Official Finance & Sales

Stripe

Stripe payments, customers, subscriptions, and invoicing.

Works with: Claude DesktopClaude CodeCursorWindsurf
Quick install
npx -y @stripe/mcp

How to install the Stripe MCP server

Add this to your Claude Desktop MCP configuration:

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

Add this to your Claude Code MCP configuration:

npx -y @stripe/mcp

Add this to your Cursor MCP configuration:

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

Add this to your Windsurf MCP configuration:

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

The Stripe MCP server is Stripe’s official integration with the agent ecosystem. It gives Claude scoped access to customers, subscriptions, invoices, charges, and revenue analytics. For solo founders running their billing on Stripe, this server collapses dashboard tab-switching into a single prompt.

Why use it

Most operational questions for a SaaS business live in Stripe: how many active subscribers, what’s churning, who hasn’t paid this month. The Stripe MCP server lets Claude answer these directly without you opening the dashboard.

For weekly metric reviews, Claude with Stripe + PostgreSQL MCP becomes a personal analyst. Pull revenue numbers, cross-reference with product usage, get a synthesised picture.

What it actually does

Read and (with explicit scopes) write Stripe objects: customers, subscriptions, invoices, payment intents, products, prices, refunds. Plus reporting endpoints for aggregate metrics.

Practical patterns:

  • “How much MRR did we add last month? Break it down by plan tier.”
  • “Find every customer whose last payment failed and surface them by tenure.”
  • “Refund customer X’s last invoice with reason ‘duplicate charge’.” (Requires explicit write scope.)

Gotchas

Live-mode write scopes are dangerous. A misinterpreted prompt with full access can refund customers en masse. Default to read-only restricted keys; create separate scoped keys for explicit automation.

API rate limits apply. Heavy “summarize everything” queries can spike. Scope to date ranges or specific customers.

For deeper revenue analytics, pair Stripe with BigQuery or Snowflake where you’d dump Stripe data into a warehouse. The MCP gives Claude live access; the warehouse gives historical depth.

MCP servers related to Stripe

All in Finance & Sales →

HubSpot

Manage HubSpot contacts, deals, and marketing campaigns.

Salesforce

Manage Salesforce records, objects, and reports.
A

Apollo.io

Apollo.io contact search, enrichment, and outbound sequences.

Stripe MCP server: FAQs

Is the Stripe MCP server official?

Yes. Stripe maintains the official @stripe/mcp package as part of their agent toolkit. Source on GitHub at stripe/agent-toolkit.

How is auth handled?

Restricted API key. Use a scoped key with read-only permissions for safety. Stripe's dashboard lets you create granular keys per integration.

Can it create charges or subscriptions?

Yes, with appropriate write scopes. Don't grant write scopes to a general-purpose Claude session. Use a separate restricted key for explicit automation workflows.

Does it support test mode?

Yes. Use a test-mode key (sk_test_…) and the server returns sandbox data. Switch to live keys only when you're sure.

What about PCI compliance?

The MCP server is a normal Stripe API consumer. It handles tokens, not raw card numbers. Standard Stripe compliance applies.

Back to all MCP servers