MCP serverValidated

Stripe MCP — billing questions answered from the source

Stripe's official server: query customers, subscriptions, and payments, and search Stripe's docs from the session — so billing integration work runs against real API state in test mode.

com.stripe/mcpOfficial docs →

A vetted listing, not an install — add the config to your MCP client yourself. CoSquared never writes MCP config.

Why this one

Billing bugs are expensive and Stripe's own server with a restricted test-mode key is the lowest-risk way to give an agent real API context.

How to use it

  1. 1Use a restricted key, test mode first — never a live secret key
  2. 2Treat any mutating call as something to review before it runs

Client config

Placeholders only — bring your own values

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

Security notes

Connected with a live key this reads real customer and payment data straight into model context, and can call mutating endpoints. Use a restricted API key scoped to what the task needs, prefer test mode, and never paste a live secret key into any config file.