How to Connect Stripe to ChatGPT 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 ChatGPT account on a Pro, Plus, Business, Enterprise or Education plan. Custom MCP connectors run through developer mode, which works on ChatGPT on the web only. 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. 2Choose Read for Customers, Charges, Subscriptions, Invoices, Balance and Payouts. They cover most revenue, MRR and payout questions. Everything else can stay on None, and Financial Reports only needs Read when you use Sigma SQL.
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.

Test keys start with rk_test_ and live keys with rk_live_, and each connects as its own connection. A full secret key (sk_) is refused on purpose, since a restricted key can be limited to Read and a secret key cannot.

Add SourcetoMCP as a connector in ChatGPT

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 ChatGPT, open Settings, then Security and login, and turn on Developer mode. Custom MCP connectors sit behind this toggle, and it only appears on ChatGPT on the web.
3. 3Open the Plugins menu and select the “+” button to create a developer-mode app.
4. 4Enter the name SourcetoMCP, paste in your server address, and pick OAuth as the authentication type.
5. 5Save. The app now sits under Drafts in your app settings, where you can switch individual tools on or off.
6. 6The first time ChatGPT calls 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.

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 ChatGPT about your Stripe account

A developer-mode app stays off until you pick it. In a chat, open the Plus menu, choose Developer mode, and select SourcetoMCP for that conversation. Naming the app in your question helps ChatGPT reach for the right tool, as in “Use the SourcetoMCP app to check my Stripe account”.

With both pieces connected, ChatGPT can check disputes, customer growth, refunds, balance and payouts, and run Sigma SQL if your account has it. Try something like:

1. 1Which disputes are due for evidence in the next seven days?
2. 2How many new customers did we add each week this quarter?
3. 3Which refunds over $200 were issued this quarter?
4. 4What is in my Stripe balance, and when does the next payout arrive?
5. 5Run a Sigma query for churn by plan by signup month.

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

How this differs from Stripe's own MCP server

Stripe publishes its own MCP server at docs.stripe.com/mcp. SourcetoMCP is a separate hosted server with a narrower job: it reads your Stripe account through a restricted key you create and cannot refund, cancel or change anything. It also sits on one connection with your Google Ads, TikTok Ads, Google Analytics and Search Console data. The Stripe MCP server page has a dated comparison. Stripe can change its server, so check its documentation for what it does today.

A note on safety and limits

The connection is read only, so ChatGPT cannot change anything in your Stripe account. Each answer reports how many Stripe requests it used, and SourcetoMCP stops at 3,000 a day across Stripe operations to protect your read allowance. Customer names, emails and addresses stay out of answers unless the request asks for them.

Sigma queries run read-only SQL, leave a query record in your account for 90 days and stop at 20 a day. Revenue figures come from balance transactions in your account's time zone, so they can differ from a Stripe report built on invoice dates.

Troubleshooting

A secret key (sk_) is refused: paste a restricted key instead. Publishable keys (pk_) and webhook secrets (whsec_) are refused as well.

An answer reports a permission problem: open the key in Stripe and set Read on the missing resource. The connection stays as it is.

The connection shows Needs attention: Stripe is reporting the key as invalid, expired or revoked, so create a new restricted key and connect it again.

Sigma asks for a subscription: running SQL needs a Sigma subscription on your Stripe account and Read on Financial Reports. A slow query comes back with a query run ID, and ChatGPT can fetch the result shortly after.

The daily request limit is hit: Stripe operations stop at 3,000 requests a day, and a narrower date range uses fewer of them. Try again tomorrow.

Developer mode is missing from Settings: it is available on Pro, Plus, Business, Enterprise and Education accounts, and only on ChatGPT on the web. The mobile apps do not show it.

The app never appears in a chat: developer-mode apps sit under Drafts and stay off until you pick them. Open the Plus menu, choose Developer mode, and tick SourcetoMCP for that conversation.

ChatGPT says it can't find the tool or has no data: open the app's details page and use Refresh to pull the current tool list from the server. If that changes nothing, check the connection still shows under Active connections in SourcetoMCP.

Revoking access

You can disconnect from either side. In SourcetoMCP, remove the account from your Connections page, or revoke ChatGPT's access entirely from the Connect an agent page. In ChatGPT, open your app settings, find SourcetoMCP under Drafts, and delete it. Turning Developer mode back off hides every custom app at once without deleting any of them. 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].