Stripe MCP Server
Connect AI agents to Stripe payments, customers, subscriptions, and invoices via the official MCP server.
Updated
What is Stripe MCP?
The Stripe MCP server is a Model Context Protocol server that gives AI agents a secure, structured way to interact with the Stripe API — searching and reading data, writing changes, and looking up Stripe documentation — without hand-coding API calls.
It is built and hosted by Stripe. The remote server lives at https://mcp.stripe.com/ and authenticates via OAuth, so an MCP client (Claude, Cursor, and others) can connect with a standard authorization flow rather than pasting a raw key. The same toolkit can also run locally with npx -y @stripe/mcp using a Stripe secret or restricted API key.
Once connected, an agent can operate across core Stripe objects — customers, charges, payment intents, refunds, invoices, subscriptions, products, and prices — and search Stripe's knowledge base. Stripe recommends restricted API keys and human confirmation of write actions to keep agent access scoped and auditable.
Tools the Stripe MCP server exposes
| Tool | What it does |
|---|---|
| stripe_api_search | Search Stripe API methods by keyword. |
| stripe_api_details | Get detailed parameter info for a specific Stripe API method. |
| stripe_api_read | Read data using any Stripe API GET method. |
| stripe_api_write | Write data using POST, PATCH, PUT, or DELETE methods. |
| get_stripe_account_info | Retrieve information about the connected Stripe account. |
| create_refund | Create a refund for a charge or payment. |
| search_stripe_resources | Search across Stripe resources. |
| fetch_stripe_resources | Fetch a specific Stripe object. |
| search_stripe_documentation | Search Stripe's documentation and support knowledge base. |
| stripe_report | Search, retrieve, and create Stripe reports. |
Connect the Stripe MCP server
Claude Code
- 1
Add the remote server
Run: claude mcp add --transport http stripe https://mcp.stripe.com
- 2
Authorize via OAuth
On first use, Claude Code opens the Stripe OAuth flow in your browser — approve the connection for your Stripe account.
- 3
Verify the connection
Run /mcp inside Claude Code to confirm the Stripe server is connected and its tools are listed.
Cursor
- 1
Open MCP settings
In Cursor, go to Settings > MCP (or edit ~/.cursor/mcp.json).
- 2
Add the Stripe server
Add an entry with the remote URL https://mcp.stripe.com so Cursor connects over HTTP.
- 3
Authenticate
Complete the OAuth prompt to authorize Cursor against your Stripe account, then enable the server and its tools in the MCP panel.
Sample use cases
A finance agent runs daily and searches for overdue invoices via search_stripe_resources
It compiles a list of unpaid invoices past their due date and triggers reminder emails to the customers.
A churn analysis agent pulls recent subscription cancellations using stripe_api_read
It groups cancellations by plan, tenure, and reason, then posts a weekly churn digest to the revenue team.
A support agent receives a refund request and needs to process it
It uses create_refund to issue the refund, then fetches the updated charge to confirm the status and notify the customer.
A revenue reporting agent generates end-of-week financial summaries
It uses stripe_report to pull payment volume, net revenue, and fee breakdowns, then formats the data into a report.
A failed-payment recovery agent monitors charges with failed status
It identifies failed payments via search_stripe_resources, checks retry eligibility, and triggers customer outreach for cards that need updating.
A pricing audit agent compares Stripe product and price objects against the website
It reads all active prices with stripe_api_read, cross-references them with the pricing page, and flags any mismatches.
A dispute management agent monitors newly opened disputes
It fetches dispute details, pulls the related charge and customer data, and prepares a draft evidence document for the team.
An integration assistant answers a developer's question about the Stripe API
It uses search_stripe_documentation to find the relevant guide, then stripe_api_details to show exact parameters — no tab switching needed.
Security & permissions
The remote server at https://mcp.stripe.com/ authenticates via OAuth, so an MCP client connects through a standard authorization flow instead of embedding a raw key. For autonomous or local use, the toolkit accepts a Stripe API key as a Bearer token; Stripe strongly recommends a *restricted API key (`rk_`)** so the agent only gets the scopes you grant. Because tools can read and write live payment data, Stripe advises enabling human confirmation on write actions and being cautious when combining the Stripe MCP with other servers to avoid prompt-injection risk.
Using Stripe MCP with Gamut
In a Gamut agent workflow, Stripe becomes a connected tool the agent can call when a workflow runs on a schedule or in response to an event — for example, pulling recent charges and refunds for a daily revenue summary, looking up a customer and their subscriptions when a support event fires, or creating a refund as part of an approval flow. Gamut manages the MCP connection and authentication, so the agent invokes Stripe actions directly within the workflow; for write operations, keep them gated behind restricted keys and human review.
Further reading: our Stripe MCP setup guide walks through server options, client configuration, and the security practices that matter.
Frequently asked questions
What is the Stripe MCP server?
It is an official Model Context Protocol server, built and hosted by Stripe, that lets AI agents interact with the Stripe API — reading and writing customers, payments, refunds, invoices, and subscriptions, and searching Stripe's docs — through standardized MCP tools instead of custom code.
Is the Stripe MCP server free?
There is no separate charge for the MCP server itself — it uses your existing Stripe account and API keys. Normal Stripe pricing (such as transaction fees) still applies to any actions that move money.
How do I connect Stripe MCP to Claude or Cursor?
Point your MCP client at the remote server https://mcp.stripe.com and complete the OAuth flow. In Claude Code, add it with claude mcp add --transport http stripe https://mcp.stripe.com; in Cursor, add the URL in the MCP settings and authorize. You can also run it locally with npx -y @stripe/mcp using a restricted API key.
Is the Stripe MCP server hosted or self-hosted?
Both. Stripe hosts a remote server at https://mcp.stripe.com with OAuth, and you can also self-host a local instance via npx -y @stripe/mcp using your Stripe secret or restricted API key.
Can an AI agent process payments and refunds through Stripe MCP?
Yes. The stripe_api_write tool can create charges, invoices, and subscriptions, and the dedicated create_refund tool processes refunds. All write operations use your Stripe API credentials, so standard Stripe permissions and rate limits apply.
What Stripe resources can agents read and write via MCP?
Agents can read and write across the full Stripe API surface — customers, charges, payment intents, invoices, subscriptions, products, prices, refunds, disputes, and more. The stripe_api_read and stripe_api_write tools map to any Stripe API endpoint.
Is it safe to give an AI agent access to Stripe?
You control access via your Stripe API key scope. Use a restricted key that only grants the permissions your agent needs (e.g., read-only for reporting, or write access limited to refunds). The remote server at mcp.stripe.com uses OAuth with the same principle.
Does Stripe MCP work in test mode?
Yes. If you connect with a test-mode API key (or authorize the OAuth flow in test mode), all operations run against your Stripe test environment. This is the recommended setup for building and validating agent workflows before going live.