Stripe MCP: payments, invoices and subscriptions for agents

When support asks why a customer was charged twice last month, someone usually logs into the Stripe Dashboard and cross-checks payments against invoices. Stripe MCP lets an agent do that legwork. It connects to https://mcp.stripe.com, authorizes with OAuth and can read and write most of the everyday API. The stripe/ai repo is maintained by Stripe and had about 1.9k stars as of 2026-10-06.

What it does

• Generic API access: stripe_api_search finds an API method by keyword, stripe_api_details returns its parameters, then stripe_api_read (GET) or stripe_api_write (POST, PATCH, DELETE and so on) makes the call. Customers, payments, invoices, subscriptions, coupons, payment links, disputes and webhooks are all on the supported list.
• A human checkpoint: for sensitive writes such as refunds and outbound payments, Stripe hands back a link. The agent can only retry after you approve the request in Stripe, and unapproved requests expire after 24 hours.
• Analytics: stripe_analytics (preview) queries metrics, analyzes subscriptions and billing and runs financial reports. Accounts with Sigma can also turn plain questions into SQL.
• Docs and planning: search_stripe_documentation searches the official docs, and stripe_implementation_planner walks you through which Stripe products fit a payments or billing build.

Who it’s for

• Small teams that take payments on Stripe and want an agent to answer “what’s our refund rate this month” or “which subscriptions renew next week”.
• Developers integrating Stripe who want a coding agent to read the docs and create products, prices and payment links in a sandbox.
• Connect platforms that want a support agent to look up a connected account’s payments through the Stripe-Account header.

Setup

You need a Stripe account and a client that supports remote MCP with OAuth. In Claude Code it’s one command, then run /mcp to authorize:

claude mcp add --transport http stripe https://mcp.stripe.com/

Clients without OAuth can send an Agent API Key created in the Dashboard as Authorization: Bearer <key>. The repo also ships a local server (npx -y @stripe/mcp), but the docs point to the hosted endpoint first.

Our take

For a payments server, two questions matter most: is it official, and are writes gated? Stripe’s answers both. It also avoids turning hundreds of endpoints into hundreds of tools; search, inspect, then call keeps the context small. Some caveats. The OAuth screen can grant live-mode access, so start with a sandbox. From October 31, 2026 the hosted server stops accepting full-access secret keys and restricted keys without the Agent tag, so older setups need an Agent Key or a fresh OAuth connection. Stripe also warns about prompt injection when you mix it with other servers, so keep tool confirmation on. The repo is MIT-licensed.