← Back to articles

How to Connect Stripe to Gemini with MCP?

Published October 17, 2026 · Written by Aanart

SourcetoMCP is a hosted Stripe MCP server, so there is nothing to install and no code to write. This is a two-part setup: first create a restricted key in Stripe and paste it into SourcetoMCP, then add SourcetoMCP itself as a custom app inside Gemini. Once both are done, Gemini can answer questions about your revenue, subscriptions and payments from your own Stripe account. The connection is read only, so your agent cannot refund, change or cancel anything. For what the connector covers, see the Stripe MCP server page.

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 personal Google account signed in to Gemini. Custom apps in Gemini need a personal Google account (Workspace and school accounts are excluded), and Google also restricts them to accounts 18 and over, located in the US, with the language set to English and Keep Activity turned on. 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 only on the resources Gemini needs, such as Subscriptions, Invoices and Charges, and leave the rest on None. Add Financial Reports if you want SQL queries through Stripe Sigma. The Stripe setup docs cover the key in more detail.
  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.

Use an rk_test_ key to try this on test data first, then add an rk_live_ key for real payments. They appear as separate connections, and there is no consent screen because the connection uses a key you created yourself. SourcetoMCP refuses secret keys (sk_), which cannot be limited to Read.

Add SourcetoMCP as a custom app in Gemini

  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 Gemini, open Settings & help, then Connected Apps.
  3. 3Under Custom apps, choose Add a custom app and paste in your server address.
  4. 4When prompted, approve the Authorization request to access SourcetoMCP.
  5. 5Start a new chat. Gemini asks for your approval the first time it calls a SourcetoMCP tool, then reconnects on its own after that.

If Add a custom app doesn't appear, it's almost always one of the eligibility restrictions above. Double check the signed-in account is a personal one rather than Workspace or school, 18 or over, located in the US, set to English, with Keep Activity on.

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

Once it's added, SourcetoMCP is available to Gemini in any conversation, there is no separate toggle to switch on per chat. Gemini discovers the tools the server exposes and calls them the same way it uses any of its other connected apps.

With both pieces connected, Gemini can break down failed payments, find overdue invoices, total your fees and review subscriptions and promotion codes. Try something like:

  1. 1Show failed payments from the last 7 days grouped by decline reason.
  2. 2Which invoices are overdue, and for how much in total?
  3. 3How much did we pay in Stripe fees last month?
  4. 4List my active subscriptions by price.
  5. 5Which promotion codes were redeemed most this quarter?

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

How this differs from Stripe's own MCP server

Stripe's own MCP server is documented at docs.stripe.com/mcp. Use SourcetoMCP when you want Stripe on the same connection as your ad and analytics accounts, with access held to Read by a restricted key you create. The Stripe MCP server page compares the two as of a set date, and Stripe's documentation is the place to check what its server does now.

A note on safety and limits

Gemini can read your Stripe account and cannot change it. Stripe counts read requests against your account's own allowance, so each answer reports how many it used and the daily stop is 3,000 requests across Stripe operations. Names, emails and addresses are left out unless requested.

Two definitions matter when you compare numbers with Stripe's dashboard. Revenue comes from balance transactions with days in your account's time zone, and MRR is before discounts and tax, taken as a snapshot of today. Sigma SQL queries leave a query record in your account for 90 days and stop at 20 a day.

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 Gemini 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.

Add a custom app doesn't show up under Connected Apps: Google limits custom apps to personal Google accounts, age 18 and over, located in the US, language set to English, with Keep Activity turned on. Check each of those before assuming something is broken.

Gemini says it can't find the tool or has no data: check the app still shows as connected under Settings & help → Connected Apps. If it does, 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 Gemini's access entirely from the Connect an agent page. In Gemini, open Settings & help → Connected Apps and remove it. 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].