
Stripe MCP Server (Agent Toolkit)
OfficialOfficial Stripe server for payments, customers, subscriptions, invoices, and billing via natural language.
Add to your client
Copy the config for your MCP client and paste it into its config file.
npx -y @stripe/mcp --tools=all --api-key=<your-stripe-secret-key>Paste into ~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"stripe-mcp-server-agent-toolkit": {
"command": "npx",
"args": [
"-y",
"@stripe/mcp",
"--tools=all",
"--api-key=<your-stripe-secret-key>"
]
}
}
}Before you start
- Node.js 18+ (the local server runs via npx)
- A Stripe account
- A Stripe secret key — preferably a Restricted API Key (RAK) with only the permissions the agent needs, created at https://dashboard.stripe.com/apikeys
- For the remote server (mcp.stripe.com): an MCP client that supports OAuth or bearer-token auth
About Stripe MCP Server (Agent Toolkit)
The Stripe MCP server is part of Stripe's official Agent Toolkit. It exposes Stripe's payments, billing, and commerce APIs to LLM agents so they can create customers, generate payment links, manage invoices and subscriptions, issue refunds, and read account balance through natural-language tool calls.
There are two ways to run it. A local stdio server (@stripe/mcp on npm) runs via npx and authenticates with your Stripe secret key — ideal for Claude Desktop, Cursor, VS Code, and Cline. A remote server at https://mcp.stripe.com is also available and supports OAuth for granular, revocable, per-client permissions (and is built into Cursor, VS Code, ChatGPT, and Claude Code).
Tool access is scoped by your API key. Stripe strongly recommends using a Restricted API Key (RAK) so the agent can only touch the resources you grant. The same toolkit also ships function-calling adapters for the OpenAI Agents SDK, LangChain, and CrewAI on top of Stripe's native Node and Python SDKs.
Tools & capabilities (12)
create_customerCreate a new customer record.
list_customersList existing customers.
create_payment_linkGenerate a shareable Stripe payment link.
create_productCreate a product in the catalog.
create_priceCreate a price for a product.
create_invoiceCreate an invoice; pair with create_invoice_item and finalize_invoice.
list_invoicesList invoices for review or reconciliation.
list_subscriptionsList subscriptions; update_subscription and cancel_subscription manage them.
create_refundRefund a charge or payment.
create_couponCreate a discount coupon.
retrieve_balanceRead the current Stripe account balance.
search_stripe_documentationSearch Stripe docs; plus search_stripe_resources and fetch_stripe_resources for live objects.
When to use it
- Use it when you want an agent to spin up a payment link or invoice for a customer on demand.
- Use it when building an internal support copilot that looks up customers, subscriptions, or invoices and issues refunds.
- Use it when prototyping AI-driven billing flows (create product → price → subscription) without writing API glue code.
- Use it when you want the model to answer Stripe API questions by searching Stripe's own documentation.
- Use it when you need to reconcile or report on payment intents, disputes, and balances from a chat interface.
Quick setup
- 1Create a Restricted API Key in the Stripe Dashboard with only the permissions your agent needs.
- 2Add the server to your MCP client config: command `npx`, args `["-y", "@stripe/mcp", "--tools=all"]`.
- 3Provide the key via the `STRIPE_SECRET_KEY` env var or `--api-key=` CLI flag.
- 4Optionally narrow the toolset with `--tools=` (comma-separated tool names) instead of `all`.
- 5Restart the MCP client and confirm the Stripe tools appear.
- 6Alternatively, connect the remote server at https://mcp.stripe.com using OAuth.
Security notes
Grants live access to your Stripe account; always use a restricted API key scoped to only the needed resources rather than your full secret key. For agents, prefer the remote server's OAuth flow over embedding keys.
Stripe MCP Server (Agent Toolkit) FAQ
Local server or remote (mcp.stripe.com) — which should I use?
Use the local `@stripe/mcp` server if your client only supports stdio or you want to keep keys on your machine. Use the remote server for OAuth-based, revocable, granular permissions and zero-install setup in clients like Cursor, VS Code, and Claude Code.
How do I limit what the agent can do?
Scope it with a Restricted API Key (RAK) so the server can only call the resources you grant, and/or pass `--tools=` with a specific subset of tool names instead of `--tools=all`.
Does it work with test mode?
Yes. Use a test-mode secret key (sk_test_…) and all calls hit your Stripe test data, so you can build and verify flows without moving real money.
Which clients are supported?
Any MCP client. The local server works in Claude Desktop, Cursor, VS Code, and Cline via stdio; the remote server is built into Cursor, VS Code, ChatGPT, and Claude Code.
Is it free?
The server and toolkit are open-source (MIT). You only pay standard Stripe processing fees for real transactions you create through it.
Alternatives to Stripe MCP Server (Agent Toolkit)
Coinbase's AgentKit MCP extension for onchain actions: transfers, swaps, and contract calls.
Alpaca's official trading server for stocks, ETFs, options, and crypto in plain English.
Interact with 60+ EVM chains: balances, transfers, contracts, ENS, and ABI fetching.
Compare Stripe MCP Server (Agent Toolkit) with: