Home · Setup · Claude Code

MCP Stripe Billing in Claude Code

Check your Stripe balance and build payment links from chat. stripe_balance reads your live Stripe account balance and stripe_payment_link creates a shareable payment link for a price you name; both call the Stripe REST API directly with the STRIPE_SECRET_KEY environment variable you set — no SDK, no dashboard, the answer lands in the conversation.

The key lives in the environment the server already inherits, so nothing else to configure; payment links built from the terminal land in the same chat where you are drafting the invoice.

What you get in Claude Code

You say	Tool
What is my Stripe balance right now?	`stripe_balance`
Create a payment link for 25.00 for the strategy session.	`stripe_payment_link`
Check the balance, then link 120 for the invoice.	`stripe_balance, stripe_payment_link`

The contract suite covers the key-missing path (a structured error telling you to set STRIPE_SECRET_KEY, never a stack trace) and asserts the request shapes against the documented Stripe REST API; live balance reads were verified against a real account during development.

Install it in Claude Code

The file is .mcp.json, and the key inside it is mcpServers.

Scope	Path
local (default)	`~/.claude.json, this project only`
project	`.mcp.json at the repository root`
user	`~/.claude.json, every project`

If you also run Claude Desktop, the shortest path there is one click: stripe-billing.mcpb from the latest release opens as an extension, with no JSON and no terminal. Claude Code reads its own config, so here it is:

From the terminal, against a built file:

claude mcp add --scope user stripe-billing -- node /absolute/path/to/mcp-servers/servers/stripe-billing/dist/index.js
claude mcp list    # health-check it before the first prompt

# or --scope project, committed to .mcp.json for the team

The node command above wants a built file. From a clone, once:

git clone https://github.com/theluckystrike/mcp-servers.git
cd mcp-servers && npm install
npm run build -w packages/mcp-license -w servers/stripe-billing

That writes servers/stripe-billing/dist/index.js, and its absolute path is the one argument the config needs.

The npm packages are not published yet, so the form below returns a 404 today. It is here because it is what the entry becomes the day the publish lands, with nothing else changed:

claude mcp add stripe-billing -- npx -y @theluckystrike/mcp-stripe-billing

No restart. The entry is picked up in the next session, and `/mcp` reconnects one on demand.

Nothing is published to npm yet, so the working install paths are the ones above: the .mcpb bundle from the latest release, a clone and build, or the hosted URL.

No install: the hosted endpoint

There is no hosted endpoint for this one yet. MCP Stripe Billing runs locally over stdio with the config above, which is also the only form in which it reads and writes files on your own disk. Thirty of the servers in this collection are served at https://mcp.zovo.one/mcp/<name> over MCP streamable HTTP; https://mcp.zovo.one/mcp/connect lists them and prints a ready URL for each.

Claude Code notes worth knowing first

The `--` is load-bearing: it separates Claude Code's own options, such as --transport, --env and --scope, from the command that runs the server. And the default scope is local, private to you and to the directory you ran it in, so adding it in the wrong folder leaves the tools absent with no error at all.

Free: Everything: two tools, no metering, no key. Bring your own STRIPE_SECRET_KEY. Pro is $19 once, verified offline.

Questions

Which scope should I use for MCP Stripe Billing?

Local, the default, writes ~/.claude.json and is private to you and that directory. --scope project writes .mcp.json at the repository root, shared through version control. --scope user loads it everywhere.

Why did my first prompt ignore the server?

Measured, not documented: of three fresh projects, one first prompt made zero tool calls although initialize answered in 1.05 seconds. Run claude mcp list once first: it prints Connected, and the next run used the tool.

Can I use MCP Stripe Billing without installing anything?

Not this one. The office suite starts every sibling server as its own child process, so it runs locally over stdio. Thirty of those children are hosted individually at https://mcp.zovo.one/mcp/<name> if you want a no-install route; open https://mcp.zovo.one/mcp/connect and it prints a ready URL for each.

MCP Stripe Billing in detail · The same server in Claude Desktop and Cursor · Every server in Claude Code · Guides · Claude Code docs · Buy Pro