Stripe MCP Server

tl;dr: Stripe’s MCP is remote only at https://mcp.stripe.com, OAuth-authorized against your Stripe account. There is no official local-stdIO @stripe/mcp-server npm package — @stripe/mcp is just the setup CLI for the remote endpoint. The Stripe team’s agent assets (plugin, skills, tools) live in github.com/stripe/ai.

Install (recommended — agent plugin)

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

stripe agent setup detects which agent runtimes you have and runs the right install command for each. It writes the MCP config and installs the skills.

Manual install

If your client doesn’t support the plugin, add the URL directly.

Claude Code

claude mcp add --transport http stripe https://mcp.stripe.com/
claude /mcp   # then complete the OAuth consent

Cursor

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

Codex CLI (~/.codex/config.toml)

[mcp_servers.stripe]
url = "https://mcp.stripe.com"

VS Code (.vscode/mcp.json)

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

For non-OAuth clients, pass a restricted API key as a bearer token:

{
  "stripe": {
    "url": "https://mcp.stripe.com",
    "headers": { "Authorization": "Bearer rk_..." }
  }
}

Tools

The remote MCP exposes both narrow stripe_api_* tools and product-specific ones. Highlights from the docs:

• stripe_api_search / stripe_api_read / stripe_api_write — generic wrappers over any Stripe GET/POST/PATCH/PUT/DELETE endpoint
• get_stripe_account_info — account details
• stripe_analytics / list_metrics / explain_metric / metric_drilldown / show_metric_app — Sigma reporting (Private preview)
• get_balance_summary — Treasury (Public preview)
• search_stripe_documentation / stripe_implementation_planner — agent helpers
• stripe_report — Reports API
• 100+ resource-specific tools for customers, payment_intents, subscriptions, invoices, products, prices, disputes, issuing/..., v2/money-management/... etc.

The full list lives at docs.stripe.com/mcp. Stripe adds tools regularly; treat the above as a snapshot, not a contract.

OAuth sessions

Each connected MCP client gets a separate session you can manage at dashboard.stripe.com/settings/user (admins manage all users’ sessions at Team and security). Revoking a session scopes to the currently viewed account/environment only.

For Connect platforms, pass a Stripe-Account: acct_… header in mcpServers.stripe.headers to act on behalf of a connected account. There is no OAuth flow for connected-account access — use a restricted key.

Gotchas

• Treat write tools like SQL injection risk. Stripe’s own docs warn: “Enable human confirmation of tools and exercise caution when using the Stripe MCP with other servers to avoid prompt injection attacks.” Pin to read-only keys when you can.
• IT may block mcp.stripe.com on managed devices. Ask to allowlist the host.
• The remote server is the only supported Stripe MCP. npx @stripe/mcp from older blog posts just runs the same setup CLI.

Related

• Notion MCP — workspace docs
• Supabase MCP — backend
• MCP Servers Explained