How to Connect Stripe to Grok 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 Grok account. Custom connectors on grok.com need a SuperGrok plan, either standalone or through X Premium+. On a Grok Business or Enterprise seat, a team admin provisions the connector instead, see the note in the next section. 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. 2On the new key, change the permissions you want Grok to use to Read (Customers, Charges, Subscriptions, Invoices, Balance and Payouts are the usual set) and keep every other permission on None. Add Read on Financial Reports only if you have Stripe Sigma and want 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.

You can connect a test key (rk_test_) and a live key (rk_live_) side by side, and each shows as its own connection. Pasting a full secret key (sk_) gets refused, because only a restricted key can be held to Read access. Nothing needs approving, since the key is yours.

Add SourcetoMCP as a custom connector in Grok

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. 2Go to grok.com/connectors and select New Connector.
3. 3Choose Custom.
4. 4Paste in your server address and complete the authentication step so Grok can reach it. SourcetoMCP runs its own OAuth, so there is no client ID or secret to enter.
5. 5Approve access when Grok asks for it, the same as you would for any other connector.

On a Business or Enterprise plan, a team admin adds the connector first, from console.x.ai's Grok Business → Connectors, choosing Add Connector, then Other, and pasting the same server address. Once it's provisioned, each team member opens grok.com/connectors themselves and signs in with their own SourcetoMCP account, so a 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 Grok about your Stripe account

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

With both pieces connected, Grok can build weekly revenue tables, count trials and cancellations, compare payment success rates and check payouts. Try something like:

1. 1Give me a weekly revenue table for the last eight weeks.
2. 2How many subscriptions are trialing, and how many are set to cancel?
3. 3What is our payment success rate this month compared with last month?
4. 4Which payouts failed or are running late?
5. 5Compare net revenue this month with the same month last year.

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

How this differs from Stripe's own MCP server

Two Stripe options exist: Stripe's own MCP server (docs.stripe.com/mcp) and SourcetoMCP. SourcetoMCP reads your account with a restricted key you create, so it cannot refund, cancel or change anything, and it shares one connection with your Google Ads, TikTok Ads, Google Analytics and Search Console accounts. Compare them on the Stripe MCP server page, and recheck Stripe's documentation because its server can change.

A note on safety and limits

Everything Grok does here is a read. The daily stop is 3,000 Stripe requests, counted per answer and reported with it, because Stripe counts reads against your own allowance. Sigma queries stop at 20 a day and leave a query record in your account for 90 days. Customer names, emails and addresses only appear when the request asks for them.

Revenue is built from balance transactions in your account's time zone, which can differ from a Stripe report built on invoice dates. MRR excludes discounts and tax and shows today only.

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

New Connector → Custom isn't available on grok.com: custom connectors need a SuperGrok plan on an individual account. On a Business or Enterprise seat, a team admin has to provision the connector first from console.x.ai before it shows up for anyone else.

Grok says it can't find the tool or has no data: check the connector still shows in grok.com/connectors. 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 Grok's access entirely from the Connect an agent page. In Grok, open grok.com/connectors and remove it. On Business and Enterprise, a team admin removes it for everyone from console.x.ai. 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].