Server data from the Official MCP Registry
Manage companies, plans, features, and billing through SchematicHQ
Manage companies, plans, features, and billing through SchematicHQ
Valid MCP server (2 strong, 4 medium validity signals). 2 known CVEs in dependencies (0 critical, 2 high severity) Package registry verified. Imported from the Official MCP Registry.
3 files analyzed · 3 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Set these up before or after installing:
Environment variable: SCHEMATIC_API_KEY
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-schematichq-schematic-mcp": {
"env": {
"SCHEMATIC_API_KEY": "your-schematic-api-key-here"
},
"args": [
"-y",
"@schematichq/schematic-mcp"
],
"command": "npx"
}
}
}From the project's GitHub README.
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.
Install the package from npm:
npm i @schematichq/schematic-mcp
Add the MCP server to Claude:
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.
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"
}
}
}
}
Add to your Cursor MCP config (Settings > MCP Servers, or edit the file directly):
~/.cursor/mcp.json~/.cursor/mcp.json%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.
The server needs a Schematic secret API key (not the publishable key). It checks two sources in order:
SCHEMATIC_API_KEY~/.schematic-mcp/config.json{
"apiKey": "your-secret-api-key-here"
}
You can find your secret API key in the Schematic dashboard.
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.
| Tool | Description |
|---|---|
get_company | Look up a company by ID, name, Stripe customer ID, or custom key. Returns details, plan, trial status, and links. |
create_company | Create (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_plan | Get the plan a company is currently on. |
get_company_trial_info | Check if a company is on a trial and when it ends. |
count_companies_on_plan | Count how many companies are on a specific plan. |
link_stripe_to_schematic | Find the Schematic company for a Stripe customer ID, or vice versa. |
| Tool | Description |
|---|---|
list_company_overrides | List overrides by company or by feature. |
set_company_override | Set or update an override for a company on a specific feature. Supports boolean (on/off), numeric, and unlimited values. |
remove_company_override | Remove an override so the company falls back to plan entitlements. |
| Tool | Description |
|---|---|
list_plans | List all plans. |
create_plan | Create a new plan. |
add_entitlements_to_plan | Add feature entitlements to a plan. Auto-detects feature type and sets appropriate value types. |
| Tool | Description |
|---|---|
list_features | List all features. |
create_feature | Create a new feature flag. Supports boolean (on/off), event-based (metered), and trait-based types. Automatically creates an associated flag. |
| Tool | Description |
|---|---|
list_flags | List 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_flag | Get 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. |
Once configured, try asking your AI assistant:
# Install dependencies
yarn install
# Build
yarn build
# Run in development mode (auto-recompile on changes)
yarn dev
# Run tests
yarn test
MIT
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.