Home / Blog / Stripe MCP
How-to · 2026

Stripe MCP: Connect Claude to Stripe, and Why MRR and Churn Need a Definition First

Stripe’s MCP server lets an assistant call the Stripe API. That is a good way to look something up. It is a harder way to report MRR, which is a rule applied to subscriptions, not a field.

By · Published November 17, 2026 · 6 min read

Stripe documents an MCP server that lets an assistant such as Claude look things up in your account: customers, charges, subscriptions, invoices. It is good at that. Subscription metrics are a different job. MRR and churn are rules applied to those records, and an assistant calling the API will apply whichever rule it guesses.

Connecting it

Stripe documents a remote server at mcp.stripe.com that connects with OAuth, and a way to use a restricted API key when a client does not support OAuth. A third-party guide reports that Stripe is moving users off key-based access, so confirm the current rules in Stripe’s own documentation before you build a setup around a key. Whatever the method, keep the access read-only for reporting.

What it is good for

Lookups: what did this customer pay, which subscription is past due, which charge was refunded. One question, one record, a clear answer.

Where metrics go wrong

Take an illustrative business with 55 customers. Asked for MRR twice, an assistant that has no rule written down might spread annual plans in one answer and count the renewal month’s cash in the other. The two figures differ by thousands of dollars, and both came from the same Stripe data. The rule has to be written down once: how to calculate MRR covers annual plans, discounts and pauses, and churn rate covers why customer churn and revenue churn disagree.

Reporting every month

For a report you send each month, a connector that reads Stripe on a schedule and holds the definitions is steadier than an assistant calling the API fresh each time. Quiriz reads Stripe through a read-only connector, with Subscriptions, Invoices, Customers and an MRR dataset, and keeps the MRR and churn definitions in Company Context. See Stripe AI and Stripe reporting.

Where this stops. If a coupon is not recorded in a way that says whether it repeats, the definition has to say how to treat it. Quiriz follows the rule you set rather than guessing.

📚 Connector reference: every dataset and metric definition behind this, and how each is calculated, is in the Stripe connector. All connectors.

MRR that does not change with the question

Try the questions on sample subscription data with no signup, then connect Stripe read-only and ask for MRR by plan.

Try Quiriz free →

Frequently asked questions

Does Stripe have an MCP server?
Yes. Stripe documents a remote MCP server at mcp.stripe.com that supports OAuth, and a local option run with a key. Check Stripe’s documentation for the current authentication rules, since they have been changing.
Is it safe to use a restricted key with an assistant?
A read-only restricted key limits the damage a wrong instruction can do. Grant only the objects you need, and never use a full-access secret key.
Can Claude calculate my MRR from Stripe?
It can try, from subscription records, but the result depends on rules the API does not supply: how annual plans are spread, which discounts count and which statuses are excluded. Without those rules, two questions can give two answers.
Why does MRR differ from the Stripe dashboard?
Different rules for trials, past-due subscriptions, discounts or currency. Neither number is wrong. Write down yours and compare the same rules on both sides.
What is the difference between an MCP server and a connector?
An MCP server exposes API actions to an assistant. A connector in a reporting tool reads the data on a schedule into datasets with definitions, which suits recurring reports.