Does the Stripe MCP server work with Claude?

Yes. It works with any MCP client, including Claude Cowork, Claude Code, and Claude Desktop. Stripe hosts a remote server at https://mcp.stripe.com that connects over OAuth, and you can also run a local server with npx.

Is there an official Stripe MCP server?

Yes. Stripe maintains an official MCP server as part of its Agent Toolkit. It runs locally via the @stripe/mcp npm package and is hosted remotely at mcp.stripe.com, so you do not need a community alternative.

Is the Stripe MCP server free?

The server itself is free and open source. You pay only normal Stripe processing fees on real transactions — the MCP layer adds no charge. Test it against a sandbox account first.

Can the Stripe MCP server move money or issue refunds?

It can create refunds, payment links, and invoices out of the box, and the toolkit can be extended with Treasury and Issuing tools for moving money and managing cards. Scope it with a restricted API key so it can only do what you intend.

Stripe MCP Server: What It Does & How to Use It with Claude

The Stripe MCP server lets an AI assistant read and act on your Stripe account: creating customers, invoices, and payment links, listing payments and subscriptions, issuing refunds, and searching Stripe’s own docs. It is an official server maintained by Stripe, so any MCP client (Claude Cowork, Claude Code, Claude Desktop) can connect to it over OAuth or a local key.

What can the Stripe MCP server do?

Capability	What it enables
Customers	Create customers (`create_customer`) and list existing ones (`list_customers`).
Products & prices	Create and list products and prices (`create_product`, `create_price`, `list_products`, `list_prices`).
Invoices	Create invoices and invoice items, finalize them, and list invoices (`create_invoice`, `create_invoice_item`, `finalize_invoice`, `list_invoices`).
Payment links	Generate a shareable hosted checkout link (`create_payment_link`).
Payments & refunds	List PaymentIntents and create refunds (`list_payment_intents`, `create_refund`).
Subscriptions	List, update, and cancel subscriptions (`list_subscriptions`, `update_subscription`, `cancel_subscription`).
Coupons & disputes	Create and list coupons; list and update disputes (`create_coupon`, `list_coupons`, `list_disputes`, `update_dispute`).
Balance & account	Retrieve account info and balance (`get_stripe_account_info`, `retrieve_balance`).
Search & fetch	Look up Stripe objects and search Stripe’s documentation and support knowledge base (`search_stripe_resources`, `fetch_stripe_resources`, `search_stripe_documentation`).

The toolkit can also be extended with Treasury and Issuing tools to move money, pay bills, and manage cards. Those are off by default and gated by your key’s permissions.

Is there an official or community server?

There is no need for a community fork here. Stripe ships and maintains the server itself.

Official Stripe MCP server (@stripe/mcp) is the right default. It is part of Stripe’s Agent Toolkit, available as a remote OAuth server at https://mcp.stripe.com or a local server via npx. It covers payments, billing, and the documentation search tools above.
Wrappers and directory listings. Third parties (Composio, Docker MCP Catalog, and others) repackage the official server for their platforms. They are convenience layers rather than separate implementations, and still hit Stripe’s APIs under your key.

How do you connect it to Claude (Cowork / Code / Desktop)?

Pick a transport. Use the remote server (https://mcp.stripe.com) for OAuth-based access, or run locally with npx -y @stripe/mcp@latest --api-key=<YOUR_RESTRICTED_KEY>.
Create a restricted API key. In the Stripe Dashboard, generate a restricted API key (RAK) that grants only the resources you want the agent to touch. Start with read scopes.
Enable MCP access. In Settings → MCP, turn on MCP for your sandbox first. Administrators enable sandbox and live environments separately.
Add it to your client. In Claude Code: claude mcp add --transport http stripe https://mcp.stripe.com/, then run /mcp to authenticate over OAuth. In Claude Cowork or Desktop, add the same remote URL (or the local npx command with your key in --api-key or a STRIPE_SECRET_KEY env var) as a custom MCP server.
Start read-only. Verify with list_customers or retrieve_balance against your sandbox before granting any write or refund scopes.

How we use it: Good for pulling live billing context into a conversation: “which subscriptions churned this week,” “draft an invoice for this customer,” “generate a payment link for $400.” Bad for being a system of record or doing bulk financial reconciliation; that belongs in your accounting stack, not an agent loop. The realistic gotcha: tools like create_refund and cancel_subscription act on live money the moment they run, so always test against a Stripe sandbox key and keep human confirmation on before pointing it at your production account.

A second note: tool availability mirrors your restricted key’s permissions, so if a tool “isn’t showing up,” it is usually a missing scope, not a bug.

Security & permissions

Use a restricted API key scoped to only the resources the agent needs, keep keys in environment variables or a secrets vault (never in code), start in a sandbox, and leave human confirmation of tools enabled. Because MCP servers can be targeted by prompt injection, be cautious about running Stripe alongside untrusted servers, and revoke OAuth sessions from your Dashboard the moment they are no longer needed.

Wiring Stripe into your stack

The Stripe MCP server is the fast path to giving an assistant safe, scoped access to billing, but the value is in how you wire it into a real workflow: which scopes, which confirmations, which handoffs to QuickBooks or Salesforce. If you want help setting that up cleanly, Book a discovery call.

Sources: Stripe MCP docs · Stripe Agent Toolkit (GitHub) · PulseMCP listing