Stripe MCP: The Official Server Can Move Money
Yes — Stripe has an official MCP server. Stripe hosts it directly at mcp.stripe.com, and it lets any MCP-compatible AI tool read your account data and take real actions: create refunds, issue payment links, update subscriptions, even write and read arbitrary Stripe API calls. So if you’re searching “Stripe MCP,” the connection you want exists, and it’s more powerful than most.
The thing worth knowing before you turn it on: an MCP server hands Stripe to an AI inside a conversation you start. It’s a doorway, not a worker. Nothing watches your account for you, nothing fires when a payment fails or a subscription renews, and nothing runs while the chat is closed. Here’s exactly what the Stripe MCP does, how to connect it, where it stops — and what to use when you want Stripe work that runs on its own.
See also: the full MCP server list — which apps have one, and what each can reach.
What the Stripe MCP server does
Model Context Protocol (MCP) is the open standard that lets an AI client — Claude, ChatGPT, Cursor, VS Code, and others — talk to an outside app through a shared interface. Stripe’s official server is remote (no hosting required) and ships tools grouped into a few areas:
- Account and reads —
get_stripe_account_info, plusstripe_api_readfor pulling customers, charges, invoices, subscriptions, balances, and more. - Writes —
stripe_api_writeandcreate_refundfor actions like issuing a refund, creating a customer, updating a subscription, or generating a payment link. - Docs and planning —
search_stripe_documentationandstripe_implementation_plannerto look up how an API works before calling it. - Discovery —
stripe_api_searchandstripe_api_detailsso the AI can find the right endpoint and its parameters on the fly.
With it connected, an AI client can:
- Answer billing questions — “which subscriptions renew this week?” or “what’s our balance right now?” pulled from live data.
- Take real actions — refund a charge, create a payment link, update a subscription tier, all from a chat.
- Explain your own API usage — search Stripe’s docs and get an implementation plan for a specific integration.
It’s genuinely useful for ad-hoc work: ask a question, get an answer grounded in your actual Stripe account, make a change on the spot — including changes that move money, which is not something every MCP server can say.
How to set up the Stripe MCP server
The remote server is the quick path — no code, no hosting:
- In your AI client, add a remote MCP server pointing at
https://mcp.stripe.com. Claude Code:claude mcp add --transport http stripe https://mcp.stripe.com/. Cursor and VS Code both have one-click install links from Stripe’s docs, or you can add the URL manually tomcp.json. - Authenticate. OAuth is the default and recommended path — you’ll get a consent screen and can manage the session later from your Stripe Dashboard user settings. For custom clients or autonomous agents, you can instead pass a restricted API key as a bearer token.
- Confirm the tools appear in your client, then start a chat and ask it to read a record or take an action.
Because writes are live — a refund really refunds, a subscription update really changes billing — Stripe recommends scoping access with a restricted API key rather than a full secret key, especially for anything autonomous.
Where the Stripe MCP stops
None of this is a knock on MCP — it’s just the shape of the protocol. Four limits show up the moment you want more than a conversation:
- It only works inside a chat you start. Close the window and nothing happens. The AI doesn’t watch Stripe; it waits for you to ask.
- No triggers. A payment failing, a subscription renewing, a dispute opening — none of these can start anything through MCP. There’s no “when this happens in Stripe, do that.”
- It’s one app at a time. The Stripe MCP knows Stripe. Getting a refunded customer’s record updated in your CRM, a Slack alert posted, and a spreadsheet row added means wiring up a separate MCP server for each, then hoping your client can juggle them in one turn.
- You own the plumbing and the scopes. OAuth sessions, restricted-key permissions, and the blast radius of an AI that can move money are all on you.
So the Stripe MCP is a great way to ask Stripe things and make one-off changes. It is not a way to make Stripe run — to have work happen on a schedule or in reaction to an event, across the other tools a payment or subscription touches.
Running Stripe work that doesn’t need a chat open
That “run on its own, across apps” gap is exactly where Carly fits. Carly connects to Stripe natively — no MCP server to configure, no restricted-key management — and to the ~260 other apps it supports, plus anything with a public API through your own key. The difference from MCP is the important part: Carly’s workflows are triggered and scheduled, so Stripe work happens whether or not anyone has a chat window open.
A few things that MCP can’t do but a Carly workflow can:
- When a payment fails → retry, email the customer, and notify the account owner in Slack — automatically, the moment it happens.
- Every Monday morning → summarize new subscriptions, cancellations, and failed charges from the past week and send the digest to finance.
- When a dispute opens → pull the transaction history, draft a response for approval, and log it in your CRM.
The non-AI steps — the moving, matching, and routing between apps — are free and unlimited, the Zapier-style backbone of the workflow. The AI steps (drafting, summarizing, deciding) start at $35/month. You describe the outcome in plain language and Carly wires up the Stripe connection and everything downstream.
If you just want to interrogate your account or make a one-off change from a chat, Stripe’s official MCP server is the right tool. If you want Stripe to actually do things — on a trigger, on a schedule, across every app a payment or subscription touches — that’s the job MCP wasn’t built for, and it’s the one Carly was.
FAQ
Does Stripe have an official MCP server?
Yes. Stripe hosts a remote MCP server at mcp.stripe.com, documented directly in Stripe’s own docs, with tools covering account reads, writes like refunds and payment links, subscription management, and documentation search.
Is the Stripe MCP server free? Connecting to it is free — you’re authorizing an AI client against your existing Stripe account. You still need whatever Stripe account and API access your business already has, and any restricted key you use inherits your account’s real permissions.
Can the Stripe MCP trigger automations? No. MCP is request/response inside an AI chat — it has no triggers and nothing runs when the conversation is closed. For event- or schedule-driven Stripe work across apps, you need a workflow tool like Carly rather than an MCP server.
Can I connect Stripe to AI without coding or hosting a server? Yes. You don’t have to touch MCP at all. Carly connects to Stripe for you and lets you build the automation in plain language — describe what you want to happen and it wires up Stripe and the other apps involved, with no server to configure and no code to write.
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
