# Stripe

> Manage payments, customers, and subscriptions through Stripe.

[Canonical HTML page](https://top-mcps.com/mcp/stripe) · [server.json](https://top-mcps.com/mcp/stripe.json) · [methodology](https://top-mcps.com/about/methodology)

## Install

### Claude Desktop — `claude_desktop_config.json`

Paste under mcpServers. Fully quit and reopen Claude after editing.

```json
{
  "mcpServers": {
    "stripe": {
      "command": "npx",
      "args": [
        "-y",
        "@stripe/mcp"
      ],
      "env": {
        "STRIPE_SECRET_KEY": "${STRIPE_SECRET_KEY}"
      }
    }
  }
}
```

### Claude Code — `CLI or .mcp.json`

Run from your repo. Commit .mcp.json to share with your team.

```shell
# export STRIPE_SECRET_KEY=sk_test_your_key
claude mcp add stripe -- npx -y @stripe/mcp
```

### Cursor — `.cursor/mcp.json`

Global path: ~/.cursor/mcp.json. Reload window after editing.

```json
{
  "mcpServers": {
    "stripe": {
      "command": "npx",
      "args": [
        "-y",
        "@stripe/mcp"
      ],
      "env": {
        "STRIPE_SECRET_KEY": "${STRIPE_SECRET_KEY}"
      }
    }
  }
}
```

### VS Code — `.vscode/mcp.json`

VS Code uses the "servers" key (not "mcpServers").

```jsonc
{
  "servers": {
    "stripe": {
      "command": "npx",
      "args": [
        "-y",
        "@stripe/mcp"
      ],
      "env": {
        "STRIPE_SECRET_KEY": "${STRIPE_SECRET_KEY}"
      }
    }
  }
}
```

### Windsurf — `~/.codeium/windsurf/mcp_config.json`

Open via Cascade → hammer icon → Configure.

```json
{
  "mcpServers": {
    "stripe": {
      "command": "npx",
      "args": [
        "-y",
        "@stripe/mcp"
      ],
      "env": {
        "STRIPE_SECRET_KEY": "${STRIPE_SECRET_KEY}"
      }
    }
  }
}
```

### Cline — `cline_mcp_settings.json`

Open via the Cline sidebar → MCP Servers → Edit.

```json
{
  "mcpServers": {
    "stripe": {
      "command": "npx",
      "args": [
        "-y",
        "@stripe/mcp"
      ],
      "env": {
        "STRIPE_SECRET_KEY": "${STRIPE_SECRET_KEY}"
      }
    }
  }
}
```

### Continue — `~/.continue/config.json`

Continue uses modelContextProtocolServers with a transport block.

```json
{
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "stdio",
          "command": "npx",
          "args": [
            "-y",
            "@stripe/mcp"
          ],
          "env": {
            "STRIPE_SECRET_KEY": "${STRIPE_SECRET_KEY}"
          }
        }
      }
    ]
  }
}
```

### Codex CLI — `~/.codex/config.toml`

Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.

```shell
# ~/.codex/config.toml
[mcp_servers.stripe]
command = "npx"
args = [
  "-y",
  "@stripe/mcp",
]
env = { STRIPE_SECRET_KEY = "${STRIPE_SECRET_KEY}" }
```

### Zed — `~/.config/zed/settings.json`

Zed calls them "context_servers". Settings live-reload on save.

```jsonc
{
  "context_servers": {
    "stripe": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "@stripe/mcp"
        ]
      },
      "env": {
        "STRIPE_SECRET_KEY": "${STRIPE_SECRET_KEY}"
      }
    }
  }
}
```

### ChatGPT — `ChatGPT → Settings → Connectors → Developer mode`

Enable Developer mode (paid plans) and enter these values in the UI.

```json
{
  "name": "Stripe",
  "transport": "stdio",
  "command": "npx",
  "args": [
    "-y",
    "@stripe/mcp"
  ],
  "env": {
    "STRIPE_SECRET_KEY": "${STRIPE_SECRET_KEY}"
  }
}
```

## At a glance

- **Maintainer:** Stripe
- **Transport:** stdio, Streamable HTTP
- **Auth model:** API key
- **Required secrets:** STRIPE_SECRET_KEY
- **Supported clients:** Claude, Cursor, Any MCP-compatible client, Stripe accounts
- **License:** MIT
- **Language:** TypeScript
- **Latest version:** latest
- **Last verified:** 2026-04-19
- **GitHub stars:** 1,490 (fetched 2026-04-19T20:32:55.230Z)
- **Score:** 87/100 (rubric 2026-04 — see https://top-mcps.com/about/methodology)
- **Source:** https://github.com/stripe/agent-toolkit

## Security & scope

- **Access scope:** network
- **Sandbox:** Authenticates with a Stripe secret key (sk_live_... or sk_test_...). API access scope matches the key permissions.
- **Gotchas:**
  - The MCP does not distinguish between live-mode and test-mode keys — mistakes on a live key affect real charges. Always develop with sk_test_ first.
  - Restricted API keys (Stripe lets you scope keys by resource) are strongly recommended over root secret keys for agent use.

## Quick answer

**What it does.** Exposes the Stripe REST API as MCP tools: customer CRUD, subscription management, invoice creation, payment inspection, refund processing, and payout reconciliation.

**Best for:**
- Support agent lookups
- Billing state inspection
- Automated refunds with approval
- Subscription drift audits
- Invoice generation from chat

**Not for:**
- Unattended payout initiation
- Fraud-review workflows requiring compliance trail

## Recipes

### Verify test-mode setup with a safe read

```
Using my test-mode Stripe key, list my 10 most recent customers with fields: id, email, created. Confirm the key is test-mode before returning results.
```

_Tested with: Claude Desktop, Cursor_

## Description

The official Stripe MCP connects AI models and agents to your Stripe account. Create customers, issue invoices, inspect subscriptions, refund charges, and reconcile payouts — all from a natural language prompt or autonomous loop.

## Why it matters

Stripe runs billing for a huge share of modern SaaS. Giving agents programmatic access unlocks support automation, revenue analysis, and billing fixes without humans in the loop.

## Key features

- Full Stripe REST API coverage
- Scoped restricted API keys
- Test-mode support for safe iteration
- Official maintenance from Stripe
- OAuth Connect support for platforms

## FAQ

### How do I scope the Stripe MCP safely?

Use a Stripe restricted API key rather than a secret key. Restricted keys let you grant read/write per resource — e.g. read-only on customers, no access to balance transactions. The MCP respects whatever scopes the key carries.

### Does it support Stripe Connect?

Yes. For platforms using Connect, the MCP supports account impersonation headers so an agent can operate on behalf of a connected account without swapping credentials mid-flow.

### Can I use it in test mode before production?

Yes — use a test-mode restricted key (starts with `rk_test_`) and the MCP operates entirely against Stripe's test environment. Ideal for building agent workflows without real money moving.

### Is there a risk of the agent processing unintended refunds?

Only if you give it write access and run it unattended. The safe pattern is per-call approval for refunds, scoped keys that cannot touch payouts, and running destructive operations in test mode first.

## Changelog

- **2026-04-19** — Refreshed install snippets and fact sheet; verified for 2026.
- **2025-03-10** — Initial directory listing.