How to connect Stripe to Grok

Let Grok look up Stripe payments, customers and invoices. Keep it read-only, or pick the Stripe tools it may use, and see every call it made.

Updated October 10, 2026

Short answer

Grok has no Stripe connector of its own. Connect Stripe to Upsy with your Stripe login, then add Upsy to Grok as a custom connector. It takes about five minutes and needs no API key. Grok then uses Stripe's own MCP server (a connector that lets an assistant use another app), which is in public preview. For an account that holds real money, start Grok on Read-only.

The built-in way

Grok's connector docs list its built-in connectors (Google, Microsoft and Salesforce apps) and a catalog of Box, Canva, Gamma, GitHub, Linear, Meltwater, Notion, S&P Global and Vercel. Stripe isn't among them.

You could add Stripe's server address to Grok yourself as a custom connector. Then Stripe's consent page is the only filter, since Grok's docs don't describe a way to limit which tools a connector may call. Upsy adds:

Read-only: Grok can look anything up and change nothing.
Pick actions: you choose the Stripe tools one by one, and new tools stay off.
History: every Stripe call, listed under the assistant that made it.
Alerts and one-click off: stop Grok without going into Stripe.
More than one Stripe connection: up to five, each with its own level, such as a sandbox with full access and your live account read-only.
One setup that Grok Bot, Muse, ChatGPT and Claude can use too.

What you need

A Stripe account. Stripe doesn't list a plan requirement for MCP. Analytics with SQL needs Stripe Sigma, and the money-movement tools need Treasury access.
MCP access turned on for your Stripe team. An administrator can turn it on or off for live mode and sandboxes separately, at MCP and CLI access in the Dashboard.
A Grok account on grok.com. On Grok Business or Enterprise, a team admin adds connectors first.
A free Upsy account.

Set it up

Sign up at upsy.ai with Set up Upsy.
On Upsy's Apps page, find Stripe and click Connect. Sign in to Stripe.
On Stripe's consent page, choose which live accounts and sandboxes to grant, and what each may do. You can give different permissions per environment. If you're trying this out, grant a sandbox first.
On the Assistants page, click Add assistant and choose Grok under Which assistant? Upsy shows a setup prompt and its address, https://upsy.ai/connect.
In Grok, either paste the setup prompt into a chat and approve the card Grok shows, or add it by hand. On grok.com, open Connectors, click New Connector, then Custom, and paste the address. The custom connector guide has the full steps.
On the Upsy page that opens, sign in. Set Stripe to Read-only, then click Allow.
Paste the Help Grok remember message Upsy shows into Grok, so it uses Upsy for Stripe questions in later chats.

Grok already connected to Upsy? Do steps 1 to 3 only. Upsy turns a new app on for every assistant at Full access, so open Stripe's page in Upsy straight away and set Grok to Read-only.

For Grok Bot, paste the setup prompt into a Bot chat, then type @ and pick Upsy when you start a task.

Check that it works

Ask Grok: "Using Upsy, which Stripe account am I connected to, and what's my current balance?"

Grok should name your Stripe account and give the available and pending balance. If you granted only a sandbox, you'll see test data, which is expected.

What Grok can do with Stripe

Stripe's server doesn't have one tool per action any more. It has a few general tools that reach about 150 Stripe API methods:

Stripe tool	What it does	Changes anything?
`stripe_api_search`, `stripe_api_details`	Find the right Stripe API method and its fields	No
`stripe_api_read`	Look anything up: customers, payments, charges, invoices, subscriptions, refunds, disputes, payouts, balance	No
`get_stripe_account_info`	Your account's details	No
`stripe_analytics` (preview)	Metrics, subscription and billing analysis, financial reports	No
`get_balance_summary` (preview)	Balance across Stripe and Treasury accounts	No
`search_stripe_documentation`	Search Stripe's docs	No
`stripe_api_write`	Every change: create customers, invoices and payment links, refund, cancel or update subscriptions, delete coupons	Yes
`send_money`, `transfer_money`, `convert_currency`, `setup_recipient` (private preview)	Move money from a Treasury account	Yes

Upsy's levels act on these tools:

Read-only: only tools Stripe marks as read-only, which leaves out the write and money tools. Grok can answer "who paid, who didn't, what's our MRR doing" but can't change anything.
Pick actions: exactly the tools you tick. Use it to add stripe_api_write while keeping the Treasury tools off. Any tool Stripe adds later stays off until you tick it.
Full access: every tool Stripe offers, within the permissions you granted on Stripe's consent page.
No access: Grok can't reach Stripe.

Because every change runs through stripe_api_write, Upsy can't allow "create invoices" without also allowing refunds or cancellations. To narrow what that tool can do, set tighter permissions on Stripe's consent page, or grant only a sandbox. Stripe also asks for your confirmation before some changes, such as refunds and outbound payments. Grok gives you a link, you approve it in Stripe, and then you tell Grok to try again. The approval expires after 24 hours.

Prompts to try

"Did Acme Corp pay invoice INV-0042? If not, when was it due and has it been sent?"
"List this week's failed payments with the customer's email and the decline reason."
"How many active subscriptions do we have on the Pro price, and how many cancelled in September?"
"Show me the last five charges for jane@example.com and whether any were refunded or disputed."
"Summarize our open disputes: amount, reason and response deadline."
With write access in a sandbox: "Create a payment link for the Starter product at its current price and give me the URL."

Troubleshooting

Grok says it isn't allowed to make a change

That's Read-only working. Grok gets a message that you haven't allowed that Stripe tool, and History shows the attempt as blocked. If you do want the change, make it in the Stripe Dashboard, or switch Grok to Pick actions and tick stripe_api_write.

Read-only blocks a simple lookup

Read-only allows only tools Stripe itself marks as read-only. If a lookup tool is blocked, switch to Pick actions and tick the read tools from the table above, leaving the write and money tools off.

Grok sees test data, or the wrong account

Stripe connects only the accounts and environments you picked on its consent page. In Stripe, go to your user settings, open OAuth sessions and revoke the session. Then connect Stripe again in Upsy and pick the right account. A sandbox and live mode never share data.

Stripe says MCP access is disabled

An administrator has turned MCP off for that environment. They can turn it back on at Settings › MCP and CLI access, separately for live mode and sandboxes.

A refund or payout says it needs confirmation

Stripe holds some changes until a person approves them. Open the link Grok gives you, check the details, click Approve, then ask Grok to retry. More connector errors are covered in Grok connectors not working.

Security and privacy

Stripe holds your revenue and your customers' details. Three layers protect it:

Stripe's consent page decides which accounts, sandboxes and permissions any connection gets.
Upsy's level decides which Stripe tools Grok may call. Read-only stops every change. Pick actions lets you allow writes but never money movement.
Stripe's confirmation step holds refunds and outbound payments until you approve them.

Also:

Grok never holds a Stripe key. Upsy signs in with OAuth and calls Stripe for Grok.
History in Upsy lists every Stripe call Grok made, by tool and time. For the full arguments and responses, Stripe's Workbench has its own log of MCP tool calls.
Alerts: Upsy emails you if one assistant makes 100+ reads in 10 minutes, and Stripe lookups count. Changes through stripe_api_write don't count toward the delete alert, which is one more reason to keep it off unless you need it.
No approval prompt in Upsy. Upsy doesn't ask before each call, so the level you set is the control.
Turning it off: turn Grok off in Upsy with one click, set Stripe to No access, or revoke the session under OAuth sessions in Stripe.

FAQ

Can Grok access my Stripe account?

Yes, through Upsy. Grok's docs don't list a Stripe connector, so you connect Stripe to Upsy with Stripe's own sign-in and add Upsy to Grok. Grok then works through Stripe's own MCP server.

Is the Grok Stripe MCP safe for a live account?

It's as safe as the access you give it. Set Grok to Read-only in Upsy, grant only the permissions you need on Stripe's consent page, and try writes in a sandbox first.

Can Grok refund a customer or send money?

Only if you allow Stripe's write or money tools. Read-only allows neither, and Stripe still asks you to confirm refunds and outbound payments.

Do I need a Stripe API key?

No. Upsy connects with Stripe's OAuth sign-in. Stripe stops accepting old secret and restricted keys for MCP on October 31, 2026, but that doesn't affect an OAuth connection.

Can Grok use more than one Stripe account?

Yes. Upsy holds up to five Stripe connections, each with its own level. Grok picks the account in each request, or you name it in the prompt.