Stripe MCP Server: Accept Payments via Claude

Every founder and support engineer knows the drill: a customer emails about a failed payment, so you open Stripe, filter by email, click through to the subscription, check the invoice, cross-reference the charge — and five minutes later you finally have the answer. The Stripe MCP server cuts that entire chain down to one sentence typed into Claude. It gives Claude live access to your Stripe account so you can query payment data, look up customers, and check subscription health without ever leaving your conversation.

What is Stripe?

Stripe is the payment infrastructure platform used by millions of businesses worldwide to accept online payments, manage subscriptions, issue invoices, and handle complex billing logic. It provides a developer-first API that covers everything from one-time card charges to multi-currency SaaS subscriptions and marketplace payouts. If your business takes money on the internet, there is a good chance Stripe is somewhere in the stack.

What the Stripe MCP Server Does

The Stripe MCP server acts as a bridge between Claude and the Stripe REST API. Once installed, Claude gains access to a set of tools it can invoke autonomously during your conversations. The core tools include:

• List recent charges — filter by status, date range, amount, and customer.
• Look up customer by email or ID — retrieve full customer records including payment methods and metadata.
• Check subscription status — active, past due, canceled, or trialing, with renewal date and plan details.
• Retrieve invoice details — line items, due dates, payment attempts, and outstanding balances.
• Create payment links — generate shareable Stripe payment links for a product or price.
• List products and prices — see your full product catalog and associated pricing tiers.
• Check refund status — verify whether a refund has been processed and when it will arrive.

Under the hood, Claude decides which tool to call based on your natural-language request, passes the right parameters, and formats the response in a readable way. You never write API calls yourself. For a deeper look at how Claude decides which tools to invoke, see our MCP tool schema explained guide.

Prerequisites

Before installing the Stripe MCP server, make sure you have the following:

• Stripe account — any plan works, including free test-mode accounts.
• Stripe API key — go to Dashboard → Developers → API keys. For setup, copy your secret key (starts with sk_test_ for test mode or sk_live_ for production). For read-only workflows, create a restricted key with only the scopes you need.
• Node.js 18 or higher — check with node --version in your terminal. Download from nodejs.org if needed.
• Claude Desktop — the MCP server connects via Claude Desktop's MCP integration.

How to Install the Stripe MCP Server

1. Get your Stripe API key. Log into your Stripe Dashboard, navigate to Developers → API keys, and copy your secret key. During initial setup, use a sk_test_ key so you are working against test data only.
2. Open your Claude Desktop config file. This file is called claude_desktop_config.json. On macOS it lives at ~/Library/Application Support/Claude/claude_desktop_config.json; on Windows it is at %APPDATA%\Claude\claude_desktop_config.json. See our full claude_desktop_config.json guide for details on where to find and edit this file.
3. Add the Stripe server block. Paste the following configuration into the mcpServers object. If the file is empty, use the full structure shown below.
4. Replace the placeholder key with your actual Stripe secret key.
5. Save the file and restart Claude Desktop. The Stripe server will appear in Claude's tool list within a few seconds of launch.

The Config JSON

Add this block to your claude_desktop_config.json. The npx command pulls the latest server version automatically — no manual installation required.

{
  "mcpServers": {
    "stripe": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-stripe"],
      "env": {
        "STRIPE_SECRET_KEY": "sk_live_your_key_here"
      }
    }
  }
}

If you are concerned about key security, read our MCP security and trust levels guide before going live. The short version: the key lives only in your local config file and is passed to the local server process — it does not travel to Anthropic's servers.

Real Use Cases

Once the server is connected, these are the kinds of requests Claude can handle immediately:

1. "Show me all failed payments in the last 7 days." Claude queries the charges endpoint filtered by status=failed and a Unix timestamp range, then formats the results as a table with customer email, amount, and failure reason.
2. "Look up customer john@example.com and tell me their subscription status." Claude searches for the customer by email, retrieves their active subscriptions, and reports the plan name, billing cycle, next renewal date, and whether the account is past due.
3. "How much revenue did we make this month?" Claude aggregates successful charges for the current calendar month and returns a total, along with a breakdown by currency if you process multiple currencies.
4. "Create a payment link for our $99 Pro plan." Claude finds the matching price object in your product catalog and generates a Stripe payment link you can share immediately.
5. "Which customers have overdue invoices?" Claude lists all invoices with status=open and a past due date, giving you customer names, email addresses, outstanding amounts, and the number of days overdue.

Pros

• Eliminates tab switching — payment lookups, subscription checks, and revenue queries happen right inside Claude without touching the Stripe Dashboard.
• Great for support and finance workflows — customer-facing teams can get instant answers to payment questions without needing Stripe Dashboard access.
• Significant time savings on routine lookups — tasks that took 3–5 clicks and 30 seconds of navigation now take one sentence.
• Composable with other servers — combine Stripe data with a HubSpot MCP server lookup to get full customer context in one response.

Cons / Limitations

• Always use test keys during setup — a misconfigured write operation against a live key could have real consequences. Test mode first, every time.
• Read-heavy use cases work best — the server is optimized for querying data. Complex write operations like creating subscriptions with trials, coupons, and tax IDs still benefit from the Stripe Dashboard or direct API calls.
• Not a replacement for the Stripe Dashboard — webhook configuration, fraud rules, radar settings, and developer tooling still require the web interface.