Home · Setup · Windsurf

MCP Stripe Billing in Windsurf

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.

Two tools against the 100-tool ceiling, and the key-missing path returns a structured error rather than a stack trace, so a misconfigured install is obvious on the first try.

What you get in Windsurf

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 Windsurf

The file is mcp_config.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. Windsurf reads its own config, so here it is:

The config block:

{
  "mcpServers": {
    "stripe-billing": {
      "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"]
    }
  }
}

Save and reopen the MCP Servers list; Cascade picks it up without restarting the editor.

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.

Windsurf notes worth knowing first

Read this first: mcp_config.json applies to the legacy Cascade agent only. The Devin Local agent, the default for new tabs, takes its servers from the Devin CLI config files, so a correct entry here can still be invisible in a fresh tab. The other hard number is a cap: Cascade reaches at most 100 tools at once, and every enabled server spends from it.

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

Questions

Where does Windsurf keep its MCP config?

~/.codeium/windsurf/mcp_config.json, under mcpServers. Reach it from the MCPs icon at the top right of the Cascade panel, or Devin Settings, Cascade, MCP Servers.

I edited the file and a new tab still cannot see MCP Stripe Billing.

That file applies to the legacy Cascade agent only. The Devin Local agent, the default for new tabs, reads its servers from the Devin CLI config files instead. Check which agent the tab runs.

How many servers can I load at once?

Cascade reaches at most 100 tools at any one time, and every enabled server spends from that single budget. MCP Stripe Billing contributes 2 tools, so keep the enabled list short rather than counting servers.

Related

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