Schematic

Connects AI assistants to Schematic to manage companies, plans, entitlements, and feature overrides via natural language.
  • javascript

1

GitHub Stars

javascript

Language

4 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "schematichq-schematic-mcp": {
      "command": "npx",
      "args": [
        "@schematichq/schematic-mcp"
      ],
      "env": {
        "SCHEMATIC_API_KEY": "your-api-key-here"
      }
    }
  }
}

This MCP server connects AI assistants to Schematic, enabling you to look up companies, manage plan entitlements, apply overrides, create features, and more through natural language interactions. It serves as a bridge between your MCP clients and Schematic’s billing and entitlement system, making it easy to perform management tasks within conversations.

How to use

You interact with the MCP server through an MCP client such as Claude or Cursor. After configuring the client to connect to this server, you can perform actions like retrieving company details, checking trial status, managing plan entitlements, and setting feature overrides using natural language prompts. Typical workflows include looking up a company by ID or name, querying its current plan, listing available features, and applying overrides or creating new features.

How to install

Prerequisites you need before installing include a Node.js runtime and an API key for Schematic.

# Install the MCP package
npm i @schematichq/schematic-mcp

# Option A: Claude CLI integration (stdio transport)
claude mcp add --transport stdio --scope project schematic --env SCHEMATIC_API_KEY=your-api-key-here -- npx @schematichq/schematic-mcp

# Option B: Cursor integration (stdio transport) using a local config
# This demonstrates the command and environment needed to run the MCP locally with Cursor

Additional setup notes

You can configure the MCP server in multiple ways depending on your client. The following stdio configurations show how to run the MCP server locally with an API key. If you use Claude, you can also pass the key through the command in the Claude setup example.

Available tools

get_company

Look up a company by ID, name, Stripe customer ID, or a custom key. Returns company details, current plan, trial status, and relevant links.

get_company_plan

Retrieve the plan that a specific company is currently on.

get_company_trial_info

Check whether a company is on a trial and when that trial ends.

count_companies_on_plan

Count how many companies are subscribed to a particular plan.

link_stripe_to_schematic

Find the mapping between a Stripe customer ID and its corresponding Schematic company, or vice versa.

list_company_overrides

List overrides configured for a specific company or for a specific feature.

set_company_override

Create or update an override for a company on a given feature. Supports boolean, numeric, and unlimited values.

remove_company_override

Remove an existing override so the company relies on standard plan entitlements again.

list_plans

List all available plans.

create_plan

Create a new plan.

add_entitlements_to_plan

Add feature entitlements to a plan; auto-detects feature type and assigns appropriate value types.

list_features

List all defined features.

create_feature

Create a new feature flag, supporting boolean, event-based (metered), and trait-based types; automatically creates an associated flag.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
Schematic MCP Server - schematichq/schematic-mcp | VeilStrat