Stripe Billing MCP Server

Stripe Billing automation via MCP. Includes create customer, search customers, create subscription. By MEOK AI Labs. The stripe billing mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 6 defined tools rather than through you.

What it actually does

This MCP server is built with EU AI Act compliance built-in:

Its toolset

Everything the assistant can do here goes through one of these:

• Well — documented API
• Production-ready — Active maintenance
• Pro — ** $99/mo — Full MCP suite + EU AI Act tracking
• Enterprise — ** $499/mo — Custom dev + SLA + Dedicated support
• Domain — Purpose
• Tier — Price

Adding it to your client

The server ships on npm as @smithery/cli, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

When to reach for it

Among the payments and commerce options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Stripe Billing MCP's toolset — Well, Production-ready, Pro and 3 more — is a fair guide to whether it matches your workflow. It is maintained by csoai-org; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Stripe Billing MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the stripe billing mcp mcp server does with a few real requests.