Schematic

io.github.SchematicHQPublished by GitHub account SchematicHQv0.4.0Updated Oct 24, 2026

Manage companies, plans, features, and billing through SchematicHQ

VerifiedSTDIODesktop onlyDeveloper ToolsBusiness & Commerce

Overview

AI-generated overview

Connects an AI assistant to SchematicHQ to look up companies, manage plans, features, entitlements, overrides and flags through natural language.

What you can do
Look up companies by ID, name, Stripe customer ID or custom key, and check their plan, trial status and Stripe link, or count companies on a plan and create or update companies by key. List, set and remove per-company feature overrides with boolean, numeric or unlimited values. List and create plans and add feature entitlements to them. List and create features, including boolean, metered and trait-based types. List flags with targeting summaries and get full targeting rules for a single flag.
When to use it
Useful when you administer a Schematic account and want to query or change billing, plan, entitlement, feature and flag configuration conversationally instead of through the dashboard. Note that the README marks this local server as deprecated in favor of a hosted Schematic MCP endpoint.
Requirements
Runs locally over stdio via the npm package, typically launched with npx, so Node.js is needed. Requires a Schematic account and a secret API key, supplied through the SCHEMATIC_API_KEY environment variable or a config file at ~/.schematic-mcp/config.json. An optional SCHEMATIC_API_URL variable points it at a non-production API.
Before you install
The secret API key grants account-level access; keep it out of shared configs and prefer the environment variable over the config file. Several tools write data: create_company upserts companies, set_company_override and remove_company_override change entitlements, and create_plan, add_entitlements_to_plan and create_feature create billing and feature configuration. The README states this local server is deprecated and no longer receives new tools or fixes.

Installation

In SourceWeft

  1. Open Schematic in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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:

    bash
    npm i @schematichq/schematic-mcp
  2. Add the MCP server to Claude:

    bash
    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):

json
{  "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
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
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:

json
{  "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

ToolDescription
get_companyLook up a company by ID, name, Stripe customer ID, or custom key. Returns details, plan, trial status, and links.
create_companyCreate (upsert) a company identified by a key (keyName/keyValue), with an optional name and traits. Updates the company if the key already exists.
get_company_planGet the plan a company is currently on.
get_company_trial_infoCheck if a company is on a trial and when it ends.
count_companies_on_planCount how many companies are on a specific plan.
link_stripe_to_schematicFind the Schematic company for a Stripe customer ID, or vice versa.

Company Overrides

ToolDescription
list_company_overridesList overrides by company or by feature.
set_company_overrideSet or update an override for a company on a specific feature. Supports boolean (on/off), numeric, and unlimited values.
remove_company_overrideRemove an override so the company falls back to plan entitlements.

Plan Management

ToolDescription
list_plansList all plans.
create_planCreate a new plan.
add_entitlements_to_planAdd feature entitlements to a plan. Auto-detects feature type and sets appropriate value types.

Feature Management

ToolDescription
list_featuresList all features.
create_featureCreate a new feature flag. Supports boolean (on/off), event-based (metered), and trait-based types. Automatically creates an associated flag.

Flag Management

ToolDescription
list_flagsList all flags with a targeting summary — for each flag: key, default value, linked feature, and whether it resolves to always-on, always-off, or targeted. Useful for auditing always-on flags (redundant to check in code) or unused flags (candidates for deletion).
get_flagGet full targeting detail for one flag by key: default value, every rule (type, value, priority, condition count), last-checked time, and the always-on / always-off / targeted determination.

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

bash
# Install dependenciesyarn install
# Buildyarn build
# Run in development mode (auto-recompile on changes)yarn dev
# Run testsyarn test

License

MIT

Source: README.md at commit 4141cb3

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.4.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts