Stripe MCP server

Connect Stripe

npm install -g @stripe/cli@latest

stripe agent setup

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

codex mcp add stripe --url https://mcp.stripe.com

{"servers": {"stripe": {"type": "http", "url": "https://mcp.stripe.com"}}}

Use OAuth when your client supports it. For an autonomous agent, create an agent API key with only the permissions it needs and pass it as a bearer token in the Authorization header, read from an environment variable rather than pasted into a command. Claude Desktop and ChatGPT install Stripe from their connector and plugin directories.

What the Stripe MCP server does

The Stripe MCP server is Stripe's own hosted server for connecting AI agents to a Stripe account. Instead of one tool per endpoint, it gives the agent four API tools: search for an API method, read its parameters, then call it with stripe_api_read for GET requests or stripe_api_write for POST, PATCH, PUT and DELETE. That covers customers, payments, refunds, invoices, subscriptions, products, prices, coupons, payment links, disputes, tax and more.

The Stripe server also searches Stripe's docs and support articles, plans an integration step by step, and in preview queries metrics and runs financial reports. Stripe asks a human to confirm certain writes, such as refunds and outbound payments, through a link the agent shows you; unconfirmed requests expire after 24 hours. Connect platforms can act for a connected account with a restricted key and the Stripe-Account header.

Stripe hosts the server at mcp.stripe.com with OAuth, where you pick live or sandbox accounts and permissions per environment, or with an agent API key. Admins can turn MCP access on or off for the whole team. The stripe/ai repo, formerly agent-toolkit, holds Stripe's AI SDKs, plugins and skills, and had 1,851 GitHub stars on 2026-10-01.

Tools it gives your agent

• stripe_api_search
• stripe_api_details
• stripe_api_read
• stripe_api_write
• get_stripe_account_info
• stripe_analytics
• get_balance_summary
• search_stripe_documentation
• stripe_implementation_planner
• send_stripe_feedback

When to use Stripe

• You want the agent to look up a customer's payments and subscription status.
• You want test products, prices and payment links created in a sandbox.
• You are building a Stripe integration and want the agent to read the current docs.
• You want a refund issued with a human approval step.

When to pick something else

• Live mode without limits: stripe_api_write can create charges, cancel subscriptions and issue refunds, so start in a sandbox and grant live access per permission.
• Old API keys after 2026-10-31: from that date Stripe MCP rejects full secret keys and restricted keys without the Agent tag, so switch to an agent key or OAuth.

What Stripe needs

• A Stripe account, signed in through OAuth or with an agent API key
• Stripe Sigma, only for natural language SQL queries in stripe_analytics

What the Stripe MCP server costs

No separate charge for the server; payments, invoices and refunds the agent creates are billed at your normal Stripe fees, and analytics queries need Stripe Sigma.

Current prices: docs.stripe.com ↗. We do not list prices: vendors change them often, so check the publisher's own page.