Creativity · MCP — server

MCP Stripe Server

The MCP Stripe Server wraps the Stripe REST API as Model Context Protocol tools. With a restricted API key an MCP client can look up customers, create payment links or invoices, reconcile refunds, and query subscription state — the cleanest way to let Claude or Cursor answer billing questions and draft payment flows without touching production keys.

MCP facts

Kind: server
Ecosystem: anthropic-mcp
Language: TypeScript / Node.js
Transports: stdio, http

Capabilities

Tools: stripe_create_customer, stripe_search_customers, stripe_create_invoice
Tools: stripe_create_payment_link, stripe_list_subscriptions, stripe_refund_charge
Tools: read-only views over disputes, balance transactions, payment intents
Auth: restricted API keys with Write access only on selected resources

Install

npx -y @stripe/mcp --tools=all

Configuration

{
  "mcpServers": {
    "stripe": {
      "command": "npx",
      "args": ["-y", "@stripe/mcp", "--tools=all"],
      "env": {
        "STRIPE_SECRET_KEY": "rk_test_xxx"
      }
    }
  }
}

Frequently asked questions

What kind of key should I use — live or restricted?

Always a restricted key, never a root sk_live or sk_test. Grant Read on resources the agent only inspects (Charges, BalanceTransactions) and Write only where it needs to create (Customers, PaymentLinks, Invoices).

Can the agent refund a charge?

Yes if the key has Refunds:Write, but most teams keep refunds behind a human. A safer pattern is to let the agent draft a refund proposal as a comment in your ticketing system and require an operator to execute it.

Does Stripe offer a hosted MCP endpoint?

Yes — Stripe's hosted MCP server sits at an HTTPS URL and supports OAuth so each user consents individually. Use it when you want central audit logs rather than every engineer running the stdio version.

Sources

Stripe MCP — agent tools — accessed 2026-04-20
Stripe restricted API keys — accessed 2026-04-20