Home · Setup · Cursor

MCP Stripe Billing in Cursor

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.

Agent mode chains it well: 'check the balance, then link 120 for the invoice' is two calls the model makes itself — set the key in the environment, not the chat.

What you get in Cursor

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 Cursor

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

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. Cursor reads its own config, so here it is:

The config block:

{
  "mcpServers": {
    "stripe-billing": {
      "type": "stdio",
      "command": "node",
      "args": ["/absolute/path/to/mcp-servers/servers/stripe-billing/dist/index.js"]
    }
  }
}

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:

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

The Customize page shows the server and its tools once it has started.

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.

Cursor notes worth knowing first

The current field table marks `type` as required, with `stdio` for a locally launched server, so write it out rather than relying on command and args alone. The other documented restriction is that `envFile` is stdio-only: a remote HTTP or SSE server does not read it, and its headers belong in the config.

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

Questions

Project config or global config?

<project>/.cursor/mcp.json applies to that project and can be committed, which suits a server tied to one client. ~/.cursor/mcp.json applies everywhere. Both are managed from the Customize page.

Why does my stdio entry not start?

The current field table marks type as required, with stdio for a locally launched server, so include it. Pointing at a remote endpoint, envFile is documented as stdio-only and is not read.

Is there a one-click install link?

Servers in Cursor's marketplace get an Add to Cursor button. The deeplink reference currently documents prompt, command and rule links only, so for MCP Stripe Billing pasting the config block above is the supported route.

Related

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