Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Stripe to Claude Code

Have Claude draft invoices, issue refunds, and update subscriptions in Stripe. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Stripe to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Stripe, you add a Stripe MCP server: a small hosted service that exposes Stripe's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Stripe account. No API keys pasted into config files.

claude mcp add --transport http stripe https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Stripe once connected?

Full read-write Stripe access lets Claude pull up a customer, draft and send an invoice, issue a refund, update or cancel a subscription, and reconcile a payment once you approve. The billing follow-ups that used to mean tab-switching into the Stripe dashboard happen where you are already working.

  • Create and send an invoice to a customer for a stated amount
  • Issue a full or partial refund on a specific charge after approval
  • Update a subscription's plan, quantity, or billing cycle
  • Cancel a subscription or schedule it to end at period end
  • Create or update a customer record with billing details
  • Look up a payment and reconcile it against an open invoice

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Stripe access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Stripe API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Stripe changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Stripe connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Stripe connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Stripe account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Stripe's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Stripe?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Stripe account it signs in with. Revoking access is one click in Stripe.

More on the Stripe connector

Stripe connector for claude.aiQuickBooks Online + Claude CodeXero + Claude CodeFreshBooks + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us