AI tooling

Working with AI

Customer success, RevOps, sales, and finance teams all need the same thing from Schematic: an accurate picture of what a customer is entitled to and what they are actually using. That data lives in Schematic, but getting it out has usually meant either learning the dashboard or asking engineering.

The MCP server removes both steps. Connect an AI assistant such as Claude or ChatGPT, and you can ask for what you need in plain language. No SQL, no report to build, no ticket.

Implementing billing with Schematic? See Building with AI for connecting the MCP server to your coding assistant.

Before you start

You need a Schematic account and an AI assistant that supports custom MCP connectors. Setup takes a couple of minutes and you only do it once.

Two things to decide when you connect:

Sign in with your Schematic account rather than an API key. The connection then runs as you, respecting your team member permissions, and a change to your permissions takes effect immediately. Every client below supports this.

Connect read-only. You also pick an environment and whether the connection can write. Read-only is the right default for most of this work: everything on this page except adjusting an entitlement works read-only, and it removes any chance of a misread question changing a customer’s account.

Connect your assistant

Connectors are tied to your Claude or ChatGPT account rather than to one device, so you add the server once and it follows you across web, desktop, and mobile.

  1. Open Customize > Connectors.
  2. Click +, then Add custom connector.
  3. Enter https://api.schematichq.com/mcp as the URL and click Add.
  4. Click Connect and sign in to Schematic, then pick your environment and access level.

To use it in a conversation, click + in the chat, choose Connectors, and toggle Schematic on.

On Team and Enterprise plans an owner adds the connector first, under Organization settings > Connectors > Add, hovering Custom and choosing Web. Everyone else then finds it under Customize > Connectors and clicks Connect to sign in with their own Schematic account.

Whichever client you use, the connection runs from the vendor’s cloud rather than your own machine, so nothing needs installing locally.

Once your assistant lists Schematic as connected, ask it “How many companies are on each plan right now?” A real answer confirms both the connection and the environment you picked at sign-in. From there, the rest of this page covers the four workflows the data supports, and you can go straight to the one you came for.

Prepping a renewal

Before a renewal call you want three things: the plan the account is on, the entitlements that plan includes, and their usage on each metered feature. Each one is a separate lookup, so plenty of CSMs skip it and walk into the call guessing. Your assistant pulls all three in one question:

  • “What plan is Acme Corp on, and what entitlements does that plan include?”
  • “Show me Acme Corp’s usage against each metered feature for the last 90 days.”
  • “Which of Acme Corp’s entitlements are they close to using up?”
  • “Has Acme Corp had any overrides applied, and are any of them expiring?”

An override granted during onboarding and never revisited is a common source of renewal surprises, because the customer relies on something their plan does not include.

Spotting churn and expansion signals

The same data answers the opposite question, at portfolio scale rather than per account. Low usage against an entitlement is a churn signal. Usage pressing against a limit is an expansion signal.

  • “Which companies on the Pro plan have used less than 20% of their included usage this month?”
  • “Which companies are near the limit on any metered feature?”
  • “How many companies are on each plan right now?”
  • “Show me companies whose credit balance is running low.”

Run the first one on a schedule and it becomes a weekly churn sweep. Run the second and it becomes an upsell queue. Neither needs a dashboard or a report to be built first.

Checking what was sold against what was provisioned

Custom deals are where entitlements drift from the contract, because the plan is configured by hand after the deal closes. Nobody usually checks the two against each other until a customer complains.

  • “What entitlements does the custom plan attached to Acme Corp include?”
  • “Compare the entitlements on Acme Corp’s plan to these order form terms: [paste the terms].”
  • “List every company on a custom plan and what each one is entitled to.”

Running this over recently closed deals catches the mismatch while it is still cheap to fix. See Close custom deals for how custom plans are set up in the first place.

Adjusting an entitlement

This one needs a read and write connection, and it is worth being deliberate about who has one.

  • “Set an override on Acme Corp for the api_calls feature at 50,000 for the next 30 days.”
  • “List the overrides currently in place for Acme Corp.”
  • “Remove the override on Acme Corp for beta_features.”

Time-limited overrides are the safer instrument for anything granted as a concession, since they expire on their own instead of quietly becoming permanent. See Manage exceptions with overrides.

A write connection can never do more than you can do in the Schematic app. If your account cannot change a plan, neither can an assistant connected as you.

Where this fits

The MCP server is for ad-hoc questions and human-in-the-loop workflows. For automation that needs to run reliably without someone asking, use webhooks instead, which push events to Slack, your CRM, or any endpoint as they happen.

Next steps

Each workflow above has a fuller page behind it, covering how the data gets there and what to set up in Schematic so the answers are worth acting on.