Stripe MCP server

Last verified: 2026-09

Look up customers, payments, and products.

Community Developer tools Needs a secret Claude Desktop, Cursor, Windsurf, Claude Code, VS Code

What it does

Stripe's agent toolkit MCP (@stripe/mcp). Lets the model inspect customers, payments, products, and — if you pass a secret key with write — create them. Use a restricted key.

It sits in Developer tools: Split this category in two.

Good for

List products and prices in test mode.
Look up a customer or payment_intent the support thread mentioned.
Explain a webhook payload against live-shaped objects in sandbox.
Never refund or delete customers from a general-purpose chat.

Tools

customers / charges / payment_intents / products / prices / subscriptions / invoices — Read and (with a write key) mutate Stripe objects. Exact tool names follow the toolkit README.

Config (Claude Desktop / Cursor / Windsurf)

Paste the JSON below. Same mcpServers shape. Replace placeholder paths and secrets. Windows paths look like C:\\Users\\you\\project, not /path/to. Host-side steps →

Claude Desktop

OS	Config file
macOS	`~/Library/Application Support/Claude/claude_desktop_config.json`
Windows	`%APPDATA%\Claude\claude_desktop_config.json` (usually `C:\Users\<you>\AppData\Roaming\Claude\`)
Linux	`~/.config/Claude/claude_desktop_config.json`

Cursor

Scope	macOS / Linux	Windows
This project	`.cursor/mcp.json` in the repo root
This user	`~/.cursor/mcp.json`	`%USERPROFILE%\.cursor\mcp.json`

Windsurf

OS	Config file
macOS / Linux	`~/.codeium/windsurf/mcp_config.json`
Windows	`%USERPROFILE%\.codeium\windsurf\mcp_config.json`

{
  "mcpServers": {
    "stripe": {
      "command": "npx",
      "args": [
        "-y",
        "@stripe/mcp"
      ],
      "env": {
        "STRIPE_SECRET_KEY": "rk_test_..."
      }
    }
  }
}

Windsurf remote MCP: use serverUrl instead of url if the block below is HTTP.

One-liner: npx -y @stripe/mcp

Secrets it wants: STRIPE_SECRET_KEY

Source repo →

How to get started

Create a restricted key: read-only on the objects you need. Never use the old sk_live unrestricted key.
Set STRIPE_SECRET_KEY. Restart and ask it to list products.
Do refunds and customer deletes yourself.

Access risk

A live secret key is money movement. Restricted + read-only, or a sandbox key.

When to skip it

Skip it if you only need to explain a webhook payload (paste it) or if billing lives in Shopify.

Instead: Shopify, HubSpot, Salesforce.

Chat, mail & docsShopifyCatalog and orders on a Shopify store. Chat, mail & docsHubSpotContacts and deals in HubSpot. Chat, mail & docsSalesforceSOQL and sObjects.

Vs alternatives

Server	Official?	Needs a secret?	Best for
Stripe	No	Yes	Look up customers, payments, and products.
Shopify	No	Yes	Catalog and orders on a Shopify store.
HubSpot	No	Yes	Contacts and deals in HubSpot.
Salesforce	No	Yes	SOQL and sObjects.

More in Developer tools

OfficialEverythingReference server that exercises the whole MCP protocol. OfficialGitRead a local git repo: log, diff, status. OfficialGitHubRepos, issues, PRs, and file contents on GitHub. OfficialGitLabProjects, issues, and merge requests on GitLab.

All 18 in this category →

FAQ

Which key?

A restricted key, read-only, or sk_test. Never an unrestricted sk_live.

Can it move money?

If the key can refund or create charges, yes. That is the whole risk.

Stripe or Shopify?

Stripe if billing is Stripe. Shopify if the store is the system of record.

Is this Stripe's toolkit?

Yes — @stripe/mcp / agent-toolkit. Exact tool names follow their README.