Schematic MCP Server

[!WARNING] Deprecated. Schematic now hosts an MCP server at https://api.schematichq.com/mcp — see the Schematic MCP documentation to connect. This local stdio server still works but no longer receives new tools or fixes.

An MCP server that connects AI assistants to Schematic -- the platform for managing billing, plans, features, and entitlements.

Use this server to let Claude, Cursor, or any MCP-compatible client look up companies, manage plan entitlements, set overrides, create features, and more -- all through natural language.

Quick Start

Prerequisites

1. Get your Schematic secret API key: Sign up for a Schematic account and get your secret API key from the Schematic dashboard. Note: use your secret API key, not the publishable key.

Installation

Option 1: Using Claude CLI (Recommended)

1. Install the package from npm:

   Terminal

   Copy

   npm i @schematichq/schematic-mcp
   

2. Add the MCP server to Claude:

   Terminal

   Copy

   claude mcp add --transport stdio --scope project schematic --env SCHEMATIC_API_KEY=your-secret-api-key-here -- npx @schematichq/schematic-mcp
   

   Replace your-secret-api-key-here with your actual Schematic API key.

Option 2: Manual Configuration

Claude Desktop / Claude Code

Add to your Claude config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

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

Cursor

Add to your Cursor MCP config (Settings > MCP Servers, or edit the file directly):

• macOS: ~/.cursor/mcp.json
• Linux: ~/.cursor/mcp.json
• Windows: %USERPROFILE%\.cursor\mcp.json

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

After adding the config, restart Cursor for the server to be picked up.

Configuration

The server needs a Schematic secret API key (not the publishable key). It checks two sources in order:

1. Environment variable (recommended): SCHEMATIC_API_KEY
2. Config file (fallback): ~/.schematic-mcp/config.json

{
  "apiKey": "your-secret-api-key-here"
}

You can find your secret API key in the Schematic dashboard.

Custom API base URL (optional)

By default the server targets the production Schematic API. To point it at a local or non-production API, set SCHEMATIC_API_URL:

{
  "command": "npx",
  "args": ["@schematichq/schematic-mcp"],
  "env": {
    "SCHEMATIC_API_KEY": "your-secret-api-key-here",
    "SCHEMATIC_API_URL": "http://localhost:8080"
  }
}

When unset, the SDK's production default is used.

Tools

Company Lookup

Company Overrides

Plan Management

Feature Management

Flag Management

Example Prompts

Once configured, try asking your AI assistant:

• "What plan is Acme Corp on?"
• "List all my plans and their features"
• "Create a boolean feature called 'Advanced Analytics'"
• "Set an override for Acme Corp to have unlimited API calls"
• "How many companies are on the Pro plan?"
• "Find the Schematic company linked to Stripe customer cus_abc123"
• "List all flags and tell me which ones are always-on"
• "Show me the targeting rules for the billing.credits flag"

Development

# Install dependencies
yarn install

# Build
yarn build

# Run in development mode (auto-recompile on changes)
yarn dev

# Run tests
yarn test

License

MIT