Stripe MCP Server for Claude and ChatGPT
Ask about revenue, MRR, refunds, disputes and failed payments from Claude, ChatGPT or any MCP-compatible agent. Your agent can read your Stripe account and cannot change it.
SourcetoMCP is a hosted Stripe MCP server, so there is nothing to install or run on your computer. You connect with a restricted key that only has the Read access you give it, and Stripe sits on the same connection as your Google Ads, TikTok Ads, Google Analytics and Search Console accounts, so one question can compare what you spent on ads with what came in.
Agent asks
What was net revenue last month, and how much went to Stripe fees?
Agent asks
Why are payments failing this month?
Why connect Stripe to your agent
The Stripe dashboard shows the reports someone set up in advance. An agent answers the question you actually have, such as why revenue dipped last week, by reading the payments, refunds and subscriptions behind it.
- Finance questions answered in one request. Revenue after fees and refunds, MRR by price, new customers by week and the reasons payments fail, each built from your own records.
- Read only, enforced twice. The connector only sends reads, and your restricted key limits what Stripe will return. An agent cannot refund a payment or cancel a subscription through it.
- Stripe next to your ad spend. Google Ads, TikTok Ads, Google Analytics and Search Console sit on the same connection, so your agent can answer how much revenue each ad dollar brought in.
- Customer details stay out by default. Names, emails, phone numbers and addresses are left out of results unless your agent asks for them.
How it works
Create a restricted key in Stripe. Under Developers, then API keys, create a restricted key and set Read on the resources you want your agent to see. Add Read on Financial Reports if you want SQL queries.
Paste it into SourcetoMCP. Paste the key, which starts with rk_live_ or rk_test_. It is checked against your account, then stored encrypted. Deleting the key in Stripe revokes access.
Ask in plain language. Your agent picks the right operation and shows you the answer. Every answer says how many Stripe requests it used.
Recurring revenue by price
monthly recurring revenue, yearly plans at one twelfth
| price | subscriptions | MRR |
|---|---|---|
| Starter, monthly | 62 | $2,170 |
| Growth, monthly | 21 | $2,079 |
| Pro, yearly | 6 | $600 |
| Total | 89 | $4,849 |
Ask about your revenue and your ads in one question.
‖ manual mode on
Understand your Stripe account from the AI tool you already use
Revenue, fees and net
Gross sales, refunds, disputes, Stripe fees and net, by day, week or month and by currency. It is built from your balance transactions, so it matches what reached your Stripe balance, and payouts are shown apart from revenue.
Recurring revenue
Monthly recurring revenue, annual run rate and subscription counts right now, with the MRR for each price. Yearly plans count at one twelfth, and tiered or metered prices are counted separately instead of guessed.
Failed payments and why
How many payments succeeded or failed in a period, the success rate, and the top reasons for failure such as card_declined or expired_card, so you can see whether a decline problem is growing.
Refunds and disputes
List refunds and disputes with their amounts, reasons and status, filter by charge or payment, and see each dispute's evidence deadline before it passes.
Customers, subscriptions and invoices
Look up customers, subscriptions, invoices, prices, coupons and checkout sessions with filters, or search with Stripe's own query language. New customers are counted by day, week or month.
Your own SQL with Sigma
If your Stripe account has a Sigma subscription, your agent can run a SQL query over your data, such as churn by plan by signup month. Stripe lists no per-query fee, and the answer comes back as a table.
Read only, by design
You connect with a restricted key and choose what it can read. Nothing in the connector creates, changes, refunds or cancels anything in Stripe, even if the key you paste would allow it.
Anything else Stripe lets you read
Ninety of Stripe's read methods are reachable, including tax registrations, billing portal settings and Issuing cards, with unknown parameters refused and any request for a card number or secret blocked.
How this compares with Stripe's own MCP server
Stripe runs an official MCP server and lists connectors for Claude and ChatGPT. It reads and writes, and it is built to help you build with Stripe as well as run an account. The Stripe column below comes from its documentation.
| Stripe's MCP server | SourcetoMCP | |
|---|---|---|
| Writes | Can create and update customers, invoices, subscriptions, coupons and more, and create refunds, with a confirmation step for some. | Read only. Nothing creates, changes, refunds or cancels. |
| Access | Sign in with OAuth, or use an agent API key. | A restricted key you create, limited to Read on the resources you choose. Test and live keys both work. |
| Reports | Generic read tools, plus an analytics tool that is in preview. | Ready-made revenue, MRR, customer growth and payment outcome reports, with dates in your account's time zone. |
| Other data | Stripe data. | Same connection as Google Ads, TikTok Ads, Google Analytics and Search Console. |
| Building an integration | Includes documentation search and an implementation planner. | Not covered. This is for reading and analysing an account you already run. |
Source for the Stripe column: Stripe documentation, Model Context Protocol, read on 17 October 2026. Stripe can change its server at any time.
What you can ask your Stripe account
Examples of requests the operations support. Your agent chooses the operation, so you never name one.
Revenue and refunds
- What was net revenue last month after refunds and Stripe fees?
- Which refunds over $200 were issued this quarter?
- Which disputes are due for evidence in the next seven days?
Subscriptions and customers
- What is our MRR today, and which price brings in the most?
- How many new customers did we add each week this quarter?
- Which subscriptions are past due?
Payments and SQL
- Why are payments failing, and is the success rate falling?
- Compare Stripe revenue with Google Ads spend by week.
- Run a Sigma query for churn by plan by signup month.
Stripe MCP FAQ
Common questions from people connecting Stripe to an agent.
It can read it. That is 33 operations, all reads: your balance, customers, charges, payment intents, refunds, disputes, payouts, balance transactions, invoices, subscriptions, products, prices, coupons, checkout sessions and more, plus four reports (revenue summary, subscription metrics, customer growth and payment outcomes) and Sigma SQL queries if your account has Sigma. It cannot create, change, refund or cancel anything.
Claude, ChatGPT, Claude Code, Cursor, Gemini, Grok, or any MCP-compatible client. Connect once from your dashboard's "Connect an agent" page and every tool you have paired can use your Stripe data.
Yes. Stripe runs an official one at mcp.stripe.com, and lists connectors for Claude and ChatGPT. It can also write: its own page lists tools for creating refunds, invoices, subscriptions and payment links, with a confirmation step for some. SourcetoMCP is a separate, hosted server built for reading and analysing an account, and it never writes. The comparison above lists the details and links to Stripe's page.
A restricted API key, which starts with rk_live_ or rk_test_. In Stripe, open Developers, then API keys, create a restricted key and set Read on the resources you want your agent to see. Add Read on Financial Reports if you want SQL queries. A full secret key (sk_) is refused on purpose, because it cannot be limited to reads. The key is stored encrypted, and deleting it in Stripe revokes access straight away.
Yes. Test keys and live keys both work. A test mode key reads your sandbox data and a live key reads your live data, and each counts as its own connection.
No. The connector only sends reads. The one request that is not a plain read starts a Sigma query, which leaves a record of the query in your Stripe account for 90 days and changes nothing else. Because the key you paste can be limited to Read, Stripe enforces the same rule on its side too.
Customer names, emails, phone numbers and addresses are left out of results unless your agent asks for them. Reports such as revenue, MRR and payment outcomes contain no customer details at all. In Sigma results, columns that look personal, such as email and name, are left out by default.
They come from your balance transactions, so they follow money that reached your Stripe balance, with dates taken in your account's time zone. They can differ from a dashboard report built on a different basis, such as invoice dates or accrual. MRR is before discounts and tax and is a snapshot of today, because Stripe keeps no history of it. Each answer states what it covers and warns when a long period was cut short.
Stripe does not charge for API reads, but each request counts towards your account's read allowance, an average of 500 read requests per transaction over 30 days and never less than 10,000 a month. SourcetoMCP counts the requests every answer makes and stops at a daily limit, so an agent cannot use up the allowance. Sigma needs its own subscription from Stripe, and Stripe lists no per-query fee.
A dashboard shows what someone built in advance. Here your agent answers whatever you ask, in plain language, and can put Stripe next to your Google Ads, TikTok Ads, Google Analytics and Search Console data in the same request.
