Public preview

Model Context Protocol (MCP) Public preview

Let your AI agents interact with the Stripe API by using our MCP server.

The Stripe Model Context Protocol (MCP) server provides tools that AI agents can use to interact with the Stripe API and search Stripe’s knowledge base, including documentation and support articles.

Set up Stripe MCP with a plugin Recommended

Agent plugins for Stripe automatically configure the Stripe MCP server, install our skills, and make sure they’re up-to-date. You get our latest capabilities without configuration or maintenance.

To install, run:

Command Line

npm install -g @stripe/cli@latest
stripe agent setup

This command automatically detects which agents you use, and runs the applicable commands.

Manually set up Stripe MCP

If your MCP client doesn’t support agent plugins for Stripe, or you prefer to configure the Stripe MCP server and install the skills manually, follow these instructions:

Install in Cursor

Select Install in Cursor to open Cursor and add the Stripe MCP server. To configure it manually, add the following configuration to ~/the relevant part of the product.

For more information, see Cursor’s MCP documentation.

{
 "mcpServers": {
 "stripe": {
 "url": "https://mcp.stripe.com"
 }
 }
}

Manage MCP access and sessions

Stripe’s MCP server supports two authentication methods:

OAuth : Use OAuth when a client accesses Stripe on behalf of your Stripe user account.
API keys : Use API keys when an AI application needs independent, persistent access to Stripe.

When you connect an MCP client with OAuth, the client opens Stripe’s OAuth consent page. You can grant access to one or more live mode accounts or sandboxes and set different permissions for each environment. See the MCP specification for details.

If your organization manages your device or network, your IT administrator might block connections to external MCP servers. When the Stripe MCP server doesn’t connect in a managed environment, ask your IT department to allow mcp.stripe.com.

Manage MCP access for all team members

If you’re an administrator, you can enable or disable MCP access for your entire team in the Dashboard. Configure access separately for live mode and sandbox environments.

Manage your sessions

Your authorized MCP clients appear under OAuth sessions in your user settings. To revoke a session:

Find the client in the OAuth sessions list.
Click the overflow menu ( ).
Select Revoke access .

Manage sessions as an administrator

To view or revoke another user’s sessions, your role must include permissions to manage team members. The Administrator role includes these permissions.

Open Team and security in the Dashboard.
Select the team member you want to manage.
Find the OAuth sessions table.
To revoke one session, click its overflow menu and select Revoke access . To revoke every listed session, select Revoke all .

Session management applies only to the account or organization and environment—live mode or a sandbox—that you’re currently viewing. Revoking a session removes access only within that scope. The session remains active for accounts outside your current scope.

When you view an organization, the Accounts column shows the accounts associated with each session.

Authenticate Stripe MCP

Use OAuth for interactive MCP clients. OAuth lets you authorize and revoke a client without sharing an API key.

For autonomous clients that can’t use OAuth, create an agent API key with only the permissions the client needs. You can identify agent API keys in the Dashboard by the Agent badge. Pass the agent API key as the bearer token in the Authorization header of your request. Test the new configuration in a sandbox, then expire the old key.

Update API key authentication by October 31, 2026

Beginning October 31, 2026, Stripe MCP no longer accepts full-access secret keys or restricted API keys without the Agent tag. Before then, replace these keys with newly created Agent Keys or reconnect with OAuth. Requests using an unsupported key receive a 401 response with an OAuth discovery challenge.

Tools

The server exposes the following MCP tools.

Enable human confirmation of tools and exercise caution when using the Stripe MCP with other servers to avoid prompt injection attacks. If you have feedback or want to see more tools, email us at .

Resource	Tool	Description
API tools	`stripe_api_search`	Search for Stripe API methods by keyword
`stripe_api_details`	Get detailed parameter information for a specific Stripe API method.
`stripe_api_read`	Read data with any Stripe API `GET` method
`stripe_api_write`	Write data with any Stripe API `POST`, `PATCH`, `PUT` and `DELETE` method
Account	`get_stripe_account_info`	Retrieve account
Analytics	`stripe_analytics`	Preview Query metrics, analyze subscriptions and billing, and run financial reports Requires Sigma Build SQL queries based on natural language
Treasury Public preview	`get_balance_summary`	Displays an interactive balance summary across the Stripe balance and Treasury accounts
Others	`search_stripe_documentation`	Search the Stripe documentation for the given question and language
`stripe_implementation_planner`	Guides the user through Stripe products to help users accept payments, sell products online, set up billing, or build any Stripe integration
`send_stripe_feedback`	Share feedback about Stripe’s products

The Stripe MCP server exposes multiple APIs that you can call with the stripe_api_read and stripe_api_write tools. This access makes much of the API available through MCP without increasing the context window unnecessarily.

Supported API methods

Confirm actions by agents acting on your behalf

When you connect an AI agent to Stripe through the MCP server using your user credentials, you authorize the agent to access data and take actions in Stripe on your behalf.

To prevent agents from making mistakes, Stripe requires human confirmation before it takes certain stripe_api_write actions, such as refunds and outbound payments. To confirm an action, click the URL provided by your agent and review the details of the request.

Confirm a refund request

When you click Approve, Stripe provides the agent with an approval token, but you need to tell the agent to retry the operation, which doesn’t require human confirmation. If you don’t approve the action within 24 hours, it expires.

Use MCP with connected accounts

By default, Stripe MCP tools operate on the Stripe account associated with your OAuth session or API key. If you only need your agent to work with your platform account, use the standard setup above.

If you’re a Connect platform, you can also use MCP to retrieve or update resources for your connected accounts. For example, a support agent could retrieve a customer or investigate a payment for a specific connected account.

MCP doesn’t support OAuth when acting on behalf of connected accounts. Instead, authenticate with a restricted API key for your platform and grant only the connected-account permissions that your agent needs.

To make an MCP call as a connected account, pass the Stripe-Account header. This is useful when you provide an agent that allows your connected accounts to make MCP calls through your platform.

{
 "mcpServers": {
 "stripe": {
 "url": "https://mcp.stripe.com",
 "headers": {
 "Authorization": "Bearer {{AGENT_API_KEY}}",
 "Stripe-Account": "acct_xxxxxxxxx"
 }
 }
 }
}