Skip to main content
Guide8 min read·Updated May 31, 2026
🧩

How to Install the Stripe MCP Server in Claude Code (2026)

B

A. Frans

Published May 31, 2026

MCP ServersClaude CodeStripePaymentsTutorial

If you run a business on Stripe, you already know the dance: open the dashboard, dig through customers, cross-reference a payment, check whether a subscription renewed. The Stripe MCP server lets you skip the dashboard and just ask Claude. "Did invoice 4821 get paid?" "List my customers who signed up this week." "Create a product called Starter Plan at $19/month." Claude runs the Stripe call and answers. Here's how to set it up, and how to do it without handing over the keys to your whole account.

This takes about ten minutes. You need Claude Code installed, a Stripe account, and a little comfort with a terminal.

What the Stripe MCP server actually is

MCP. Model Context Protocol, is the open standard that lets Claude talk to outside tools. The Stripe MCP server is the connector for your Stripe account. Once it's wired up, Claude gets a set of tools it can call: look up customers, payments, invoices, subscriptions, products, and prices, and create some of those objects too. You're not pasting data back and forth; Claude queries Stripe directly and works with the live result.

The server is open-source and maintained as part of Stripe's agent tooling. The code is on GitHub so you can read exactly what it does before you trust it, which, for anything touching payments, you should.

Before you start: make a restricted key

Do not use your main secret key. This is the one step people skip and regret. Stripe lets you create restricted API keys that only allow the specific actions you grant, and you want the MCP server holding one of those, not a key that can do anything.

1. Go to the Stripe Dashboard, switch to Test mode for your first run (toggle top-right). 2. Open Developers → API keys → Restricted keys → Create restricted key. 3. Give it a name like claude-mcp, and grant only the permissions you need, for read-heavy use, set Customers, Charges, Invoices, Subscriptions, Products, and Prices to Read. Add Write only where you genuinely want Claude creating things. 4. Create the key and copy it. It starts with rk_test_ in test mode.

Starting in test mode means that if anything goes sideways while you're learning, no real money moves. Switch to a live restricted key only once you trust your setup.

Step 1: install the server

The Stripe MCP server runs through npx, so you don't have to install anything globally. Confirm you have Node.js first:

node --version   # should be v18 or newer

You can sanity-check that the package resolves:

npx -y @stripe/mcp --help

If that prints usage info, you're ready to wire it into Claude Code.

Step 2: add it to Claude Code

Claude Code reads MCP servers from its config. Add the Stripe server with your restricted key. The cleanest way is the CLI:

claude mcp add stripe \
  --env STRIPE_SECRET_KEY=rk_test_your_restricted_key_here \
  -- npx -y @stripe/mcp --tools=all

Or, if you edit the config file directly, the entry looks like this:

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

The --tools=all flag exposes the full tool set. You can narrow it, for example --tools=customers.read,charges.read — to limit what Claude can call even further. Tightening this is a good idea once you know which tools you actually use.

Step 3: restart and test

Restart Claude Code so it loads the new server. Then check it registered:

claude mcp list

You should see stripe listed. Now try it in a conversation. Start small and read-only:

> List my 5 most recent customers in Stripe.

If Claude returns your test customers, you're connected. Push a little further:

> Show me any failed payments from this week and what caused them.

Once read operations work, you can try a write in test mode — "create a test product called Starter at $19/month" — and confirm it shows up in your Stripe test dashboard.

What you can do with it

The everyday wins are small but add up. Instead of clicking through the dashboard, you ask. Some real uses:

  • Pull a quick read on revenue — "how many active subscriptions do I have and what's the monthly total."
  • Investigate a support ticket, "find the customer with email x and show their payment history."
  • Set up products and prices by describing them instead of filling out forms.
  • Reconcile, "list invoices marked unpaid older than 30 days."

It turns Stripe from a place you navigate into a thing you query. For a team without a developer on call, that's a real shortcut.

Security: take this part seriously

This connector can touch money, so the usual "eh, it's fine" attitude doesn't apply. A few rules worth keeping:

Restricted keys only, scoped tight. Grant the minimum permissions. If Claude only needs to read, don't give it write.

Test mode until you trust it. Live keys move real money. Learn the workflow in test mode first.

Never commit the key. Keep it in the MCP env config, not in a file you'll push to GitHub. If a key leaks, roll it in the Stripe dashboard immediately.

Read the server source. It's open on GitHub. For anything financial, spend five minutes confirming what the connector does before you run it.

Watch what you confirm. Claude proposes actions; you approve them. For write operations especially, read what it's about to do before you say yes.

If you want a code-level integration instead of the MCP connector, see our guide on integrating Stripe via Claude skills. And for other connectors, our walkthroughs for the GitHub MCP and the Notion MCP follow the same pattern.

Troubleshooting common errors

A few things go wrong on first setup. Most are quick fixes.

stripe doesn't show up in claude mcp list. Usually the config didn't load, make sure you fully restarted Claude Code, and check the JSON for a trailing comma or missing bracket. A malformed config means the whole server list silently fails to load.

"Invalid API key" or authentication errors. Confirm the key is pasted in full with no stray spaces, and that test-mode keys (rk_test_) match a test-mode request. Mixing a test key with a live-mode expectation throws auth errors that look confusing until you spot the mode mismatch.

"Permission denied" on a specific action. Your restricted key doesn't grant that permission. Go back to the Stripe dashboard, edit the restricted key, and add the needed scope, or decide Claude shouldn't have it and leave it off. This error is the system working as intended.

npx hangs or fails to fetch the package. Check your Node version is 18 or newer and that you have network access. Running npx -y @stripe/mcp --help on its own isolates whether the problem is the package or the Claude config.

Claude says it can't find a customer that exists. Check which mode you're in. Test-mode keys only see test-mode data, and vice versa. The customer you're looking at in the live dashboard won't appear through a test key.

When in doubt, narrow the surface: start with --tools=customers.read only, confirm one read works, then widen from there. Adding scope gradually makes it obvious which step broke.

What it can't (and shouldn't) do

A connector isn't a replacement for judgment. The Stripe MCP server is great at retrieving and creating objects, but it's not your accountant and it's not a controls system. Don't lean on it for anything that needs an audit trail or a second human approval, issuing refunds, changing payout settings, deleting records. Those belong in the dashboard where there's logging and confirmation built in, not in a chat where a misread instruction could move real money.

The smart pattern is read-heavy. Let Claude answer questions and surface what's happening in your account at speed, and keep the consequential writes, refunds, plan changes, anything touching live funds, as deliberate actions you take yourself. Used that way, it's a fast window into your Stripe data without becoming a risk. If you outgrow it and want deeper, code-level automation, that's the moment to look at the Stripe agent toolkit instead of the MCP connector.

FAQ

Is the Stripe MCP server free? Yes, the server itself is free and open-source. You pay normal Stripe transaction fees on real charges, but connecting Claude to your account costs nothing.

Is it safe to connect Claude to my Stripe account? Use a restricted API key, in test mode first. The server can do whatever the key allows, so scope the key tightly and never paste a full live secret key into an unsecured config.

What can the Stripe MCP server do? It lets Claude query and manage Stripe objects through tools, list customers, look up payments, create products and prices, check subscriptions, in natural language inside Claude Code.

Do I need to be a developer to use it? Some comfort with a terminal and editing a JSON config helps. The install is a few commands and a config edit. If you can follow steps and copy a key, you can set it up.

Share this article

⚙Related Tools

📬

Get More AI Tool Guides

New comparisons and guides every week. Join thousands of professionals staying ahead of the AI curve.