Stripe MCP Server
Official Stripe MCP server that lets AI agents use the Stripe API and search Stripe documentation.
- Skill Road
- Stripe MCP Server
Categories
Description
The Stripe MCP Server (currently in public preview per Stripe's documentation) implements the Model Context Protocol and gives AI agents access to the Stripe API: search Stripe API methods by keyword and look up their parameters, run arbitrary read (GET) and write (POST/PATCH/PUT/DELETE) API calls, retrieve account information, and search Stripe documentation and support articles. Additional tools cover analytics (querying metrics, time-series charts, Sigma queries), Treasury balances, reports, and an implementation assistant that guides you through building a Stripe integration.
Setup
Stripe recommends setting it up via an agent plug-in that configures the MCP server automatically and keeps it up to date:
npm install -g @stripe/cli@latest
stripe agent setup
Alternatively, register the server manually, e.g. in Claude Code with claude mcp add --transport http stripe https://mcp.stripe.com, or in Cursor via an mcpServers entry with "url": "https://mcp.stripe.com". The connection uses OAuth: on the first call, Stripe's consent page opens to confirm access to your own Stripe account.
Stripe explicitly recommends enabling human confirmation for tool calls and being cautious of prompt injection risks when using multiple MCP servers at once.
Why there's no self-hosting option
Unlike many other providers, Stripe does not offer a separate, open-source server component for self-hosting. The reason lies in the nature of the data being processed: per the provider, payment, customer, and revenue information should run exclusively through infrastructure controlled and vetted by Stripe itself, rather than through arbitrarily configured third-party servers. For users, this means less operational overhead but also less control over the exact server location and runtime environment compared to open-source MCP servers from other providers.
Typical use cases
The server is particularly suited for support and accounting tasks where an agent needs to look up payment status, customer data, or subscriptions without anyone manually switching between the Stripe Dashboard and a chat. It's also useful for building new Stripe integrations, where the implementation assistant walks you step by step through API methods and parameters. For automated, recurring workflows such as monthly revenue reporting, the analytics and reporting tools are a good fit, but should always run with restricted API keys instead of full account access given the write capability involved.
Authentication, Tools and Security in Detail
The server runs at https://mcp.stripe.com and supports two ways to sign in. With OAuth, a client is authorized to act on behalf of the user account, optionally for one or more live accounts or sandboxes with separate permissions. Autonomous clients can use agent API keys. From 31 October 2026, Stripe MCP no longer accepts full-access secret keys or restricted keys without the agent tag. The tools include stripe_api_search, stripe_api_details, stripe_api_read, stripe_api_write and search_stripe_documentation. Certain write actions such as refunds and outbound payments require human confirmation, which expires after 24 hours. Administrators manage MCP access for the whole team in the dashboard and can revoke OAuth sessions.
Frequently asked questions
Can I self-host the Stripe MCP Server? No, it runs exclusively as a Stripe-hosted service; there's no open-source alternative for running it yourself. Does the server work without the Stripe CLI? Yes, manual setup via the client's MCP configuration works just as well; the CLI is only the recommended, automated path. Is the server suitable for live payment data? Yes, but Stripe explicitly recommends human confirmation for write actions and separate controls for live and sandbox environments.
Requirements
A Stripe account plus an MCP client that supports remote servers over HTTP and OAuth. The recommended plug-in setup additionally requires Node.js/npm for the Stripe CLI.
Installation instructions
The Stripe MCP Server runs exclusively as a hosted remote service at mcp.stripe.com. Stripe offers an automated setup path via a plug-in as well as manual configuration for clients without plug-in support.
Step 1: Recommended: setup via agent plug-in
Install the Stripe CLI and run the setup assistant:
npm install -g @stripe/cli@latest
stripe agent setup
The command automatically detects which supported agent is installed locally, configures the MCP server accordingly, and installs the associated skills. Stripe then handles updates automatically without manual configuration changes.
Step 2: Manual setup
If your MCP client doesn't support plug-ins, you can also register the server by hand. In Claude Code:
claude mcp add --transport http stripe https://mcp.stripe.com
In Cursor via ~/.cursor/mcp.json:
{
"mcpServers": {
"stripe": { "url": "https://mcp.stripe.com" }
}
}
On the first call, the client opens Stripe's OAuth consent page. Confirm access for your own Stripe account there.
Managing access and sessions
Authorized clients appear in the Stripe Dashboard under user settings as OAuth sessions and can be individually revoked there. Administrators can additionally control MCP access centrally in the Dashboard — separately for live mode and sandbox environments.
Safeguarding tool calls
The server exposes both read and write API tools (stripe_api_read, stripe_api_write) that can change real payment and customer data. Stripe explicitly recommends enabling human confirmation for tool calls and watching for prompt injection attempts when using multiple MCP servers at once — for example via manipulated content from searched documents. For automated workflows, a restricted API key instead of full OAuth account access is recommended where possible.
Step 3: Verifying the setup
After connecting, test with a harmless, read-only task, such as "Show me my Stripe account information" or "Search Stripe documentation for webhooks." Only allow write actions once this works reliably.
Common setup issues
If the OAuth consent page doesn't open automatically, check whether the client is blocking pop-ups or whether the URL needs to be copied manually from the console output. If plug-in setup fails with a Stripe CLI error, check stripe --version first to confirm the installation completed fully.
A quick reinstall of the CLI usually resolves version-mismatch errors faster than trying to patch an existing broken installation.
Step 4: For marketplaces and connected accounts
Anyone working on behalf of connected accounts via Stripe Connect should use a restricted API key for that specific connected account rather than their own platform credentials for the agent. That keeps access scoped exactly to the account the agent should actually work on, instead of accidentally reaching the entire platform.
Following the principle of least privilege here also makes it much easier to audit later which agent actions touched which merchant account, should a review ever be needed.
Source: docs.stripe.com/mcp, checked on 2026-09-06.
claude mcp add --transport http stripe https://mcp.stripe.com
Authentication
OAuth authorization per the MCP specification, triggered on first connection. Authorized clients and their sessions can be managed and individually revoked in the Stripe Dashboard under user settings.
Required access permissions
By default the tools operate on the Stripe account tied to your own OAuth session or API key. API access via stripe_api_read/stripe_api_write covers most of the Stripe API for both reading and writing. Acting on behalf of connected accounts (Connect platforms) requires a restricted API key instead of OAuth. Administrators can control MCP access separately for live mode and sandbox environments in the Dashboard.
Transmitted or stored data
Requests and tool parameters go to the Stripe API and are returned to the MCP client and its language model to answer the request. Responses can include payment, customer, and revenue data from the connected Stripe account. The server runs exclusively as a Stripe-hosted service at mcp.stripe.com; there is no self-hostable option.
Security risks
Because the server allows both read and write API calls (stripe_api_write), a misdirected or manipulated agent could alter real business data, such as triggering payments or overwriting customer records. Stripe itself explicitly recommends enabling human confirmation for tool calls and staying alert to prompt injection when using multiple MCP servers at once, for example via manipulated content from searched documentation. For automated workflows, a restricted API key instead of full account access is recommended, especially for connected accounts.
License and costs
- License
- Not recorded yet.
- Cost
- free
The MCP server itself does not incur separate costs. A Stripe account is required; Stripe's usual transaction-based fees for payment processing and other products apply independently of the MCP server.
Alternatives
Not recorded yet.
At a glance
- Provider
- Stripe
- Status
- Official server
- Deployment
- Remote
- Current version
- Not recorded yet.
- Last reviewed
- 07.09.2026
Repository and documentation
Categories
Supported clients
Related guides
Guides and background related to this entry.
No related guides yet.