How to Connect Stripe to Claude with MCP?

Before you start

You'll need a SourcetoMCP account with at least one brand created, a Stripe account where you can create restricted keys, plus a Claude account. Custom connectors work on Free, Pro, Max, Team and Enterprise, though Free accounts are limited to one at a time. Stripe Sigma is optional, and only needed if you want your agent to run SQL queries.

Connect Stripe to SourcetoMCP

1. 1In Stripe, open Developers, then API keys, and choose Create restricted key.
2. 2Set Read on the resources you want Claude to see and leave everything else on None. Customers, Charges, Subscriptions, Invoices, Balance and Payouts cover most questions. Add Read on Financial Reports as well if you have Stripe Sigma and want SQL queries.
3. 3Copy the key when Stripe shows it, because Stripe only shows it once. Leave IP address restrictions off, since requests from SourcetoMCP are blocked if the key is limited to certain addresses.
4. 4From your SourcetoMCP dashboard, go to Connectors → Add a connection and find the Stripe card.
5. 5Paste the key. SourcetoMCP verifies it against your Stripe account.
6. 6Confirm the account on the next screen. It then appears on your Connections page.

A key starting with rk_test_ connects your test data and one starting with rk_live_ connects real payments. You can connect both, and they show as separate connections. SourcetoMCP refuses a full secret key (sk_) on purpose, because a restricted key can be limited to Read and a secret key cannot. There is no consent screen to approve, because this connector uses your own key.

Add SourcetoMCP as a connector in Claude

1. 1In SourcetoMCP, open Connect an agent from the dashboard sidebar and copy your server address (it looks like https://sourcetomcp.com/api/mcp).
2. 2In Claude, open Customize, then Connectors.
3. 3Select +, then Add custom connector.
4. 4Paste in your server address. You can leave Advanced settings alone, because SourcetoMCP runs its own sign-in and Claude needs no client ID or secret.
5. 5Click Add.
6. 6The first time Claude uses it, you'll be asked to sign in to SourcetoMCP and approve access, the same OAuth approval you'd see connecting any other app. After that it reconnects on its own.

On a Team or Enterprise plan, only an Owner can add a connector, from Organization settings, then Connectors. Everyone else then opens Customize → Connectors and clicks Connect to sign in with their own SourcetoMCP account, so each person only ever reaches the sources their own account can see.

Once approved, the connection appears under Active connections on the Connect an agent page in SourcetoMCP, so you can see exactly what has access at any time.

Ask Claude about your Stripe account

Adding the connector makes it available, and you still switch it on per conversation. In a chat, select the + button, choose Connectors, and toggle SourcetoMCP on.

Claude shows a panel for each tool call, named in plain English, so you can see which data it pulled and check the numbers came from your Stripe account rather than from the model.

With both pieces connected, Claude can report on revenue, MRR, subscriptions and failed payments, and set Stripe next to your ad data. Try something like:

1. 1What was net revenue last month after refunds and Stripe fees?
2. 2What is our MRR today, and which price brings in the most?
3. 3Which subscriptions are past due?
4. 4Why are payments failing, and is the success rate falling?
5. 5Compare Stripe revenue by week with Google Ads spend for the same weeks.

Every one of these is read only. You can also ask Claude which resources your key can read, to see exactly what access it was given.

How this differs from Stripe's own MCP server

Stripe runs its own MCP server, documented at docs.stripe.com/mcp. SourcetoMCP is a separate hosted server. It reads your account through a restricted key you create, so it cannot refund, cancel or change anything, and it keeps Stripe on the same connection as your Google Ads, TikTok Ads, Google Analytics and Search Console data. The Stripe MCP server page has a dated comparison with Stripe's own server. Check Stripe's documentation for what its server does today, because it can change.

A note on safety and limits

Nothing in your Stripe account can be changed through this connection. Every request your agent makes counts towards your account's own read allowance, so SourcetoMCP counts them, reports the number with each answer, and stops at 3,000 requests a day across Stripe operations. Sigma queries run read-only SQL, leave a query record in your account for 90 days, and stop at 20 a day. Customer names, emails and addresses are left out of answers unless your agent asks for them.

Revenue is built from your balance transactions, with days taken in your account's time zone, so it can differ from a Stripe report built on invoice dates. MRR is before discounts and tax, and is a snapshot of today.

Troubleshooting

The key is refused as a full-access secret key: Stripe secret keys start with sk_. Create a restricted key with Read only and paste that one. Publishable keys (pk_) and webhook secrets (whsec_) are refused too.

An answer says the key lacks permission: the key has no Read on that resource. Edit its permissions in Stripe, then ask again. There is nothing to reconnect.

The connection shows Needs attention: Stripe says the key is invalid, expired or revoked. Create a new restricted key and reconnect.

Sigma says it needs a subscription: Sigma queries need your own Sigma subscription from Stripe and a key with Read on Financial Reports. A slow query returns a query run ID first, so ask Claude for the result a moment later.

The daily request budget has been reached: SourcetoMCP stops at 3,000 Stripe requests a day to protect your read allowance. Try again tomorrow. Narrower date ranges use fewer requests, and every answer reports how many it used.

There is no Connectors option under Customize: on Team and Enterprise plans an Owner adds connectors for the whole organisation. Ask an Owner to add it from Organization settings → Connectors, and it will then show up for you to connect.

Claude won't let you add another connector: Free accounts can keep one custom connector at a time. Remove the one you have, or move to Pro or Max.

Claude says it can't find the tool or has no data: check SourcetoMCP is toggled on for that conversation under the + menu. If it is, confirm the connection still shows under Active connections in SourcetoMCP, then remove and re-add it to trigger a fresh approval.

Revoking access

You can disconnect from either side. In SourcetoMCP, remove the account from your Connections page, or revoke Claude's access entirely from the Connect an agent page. In Claude, open Customize → Connectors and remove it. On Team and Enterprise an Owner removes it for everyone from Organization settings → Connectors. To cut off SourcetoMCP's access to your Stripe account itself, delete the restricted key in Stripe under Developers → API keys.

Still stuck?

Reach us at [email protected].