The MCP Billing Gateway SDK is a hosted billing proxy that lets you monetize any MCP server with Stripe subscriptions, per-call credits, and x402 crypto payments — without writing billing code.
Service discovery: Use the get_billing_info tool to retrieve gateway capabilities, supported payment methods, features, and integration docs. This is the only tool exposed by the local SDK; full billing functionality runs on the hosted gateway.
Monetize MCP servers: Register as an operator, add your server URL and pricing plan, then point callers to a proxied URL that handles payment verification, usage tracking, and tier enforcement automatically.
Flexible billing models: Per-call billing (fiat or USDC), monthly/annual Stripe subscriptions, tiered pricing, and x402 micropayments for AI agents without API keys.
Transparent proxy: The gateway intercepts requests, verifies payment, tracks usage, and forwards to your upstream MCP server — seamlessly for AI agents and callers.
Operator dashboard: Monitor revenue, usage, and active callers, and configure servers in real time.
API endpoints: Register operators (/api/v1/operator/*), manage servers and pricing plans (/api/v1/servers/*), and proxy requests (/proxy/{slug}/*).
Deployment options: Use the hosted service or self-host via Docker.
Enables Stripe subscriptions and per-call billing for MCP servers, allowing operators to charge for API usage through monthly/annual plans or credit-based pricing.
Add Stripe subscriptions, per-call credits, and x402 crypto payments to any MCP server — without writing billing code.
MCP Billing Gateway is a hosted billing proxy that sits between AI agents and your MCP server. It handles payment verification, usage tracking, and tier enforcement automatically. You register your server, set a pricing plan, and point callers to the proxied URL. No billing code required.
Live service: https://mcp-billing-gateway-production.up.railway.app
Tutorial: Monetize any MCP server in 10 minutes — step-by-step demo with working code
pip install mcp-billing-gatewayOr with uvx:
uvx mcp-billing-gatewayAdd to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"mcp-billing-gateway": {
"command": "uvx",
"args": ["mcp-billing-gateway"]
}
}
}Add to .cursor/mcp.json in your project:
{
"mcpServers": {
"mcp-billing-gateway": {
"command": "uvx",
"args": ["mcp-billing-gateway"]
}
}
}Restart your editor after adding the configuration to activate the MCP server.
Related MCP server: Agent Bazaar
Tool | Description |
| Returns service capabilities, supported payment methods, features, and integration docs |
The local MCP server provides service discovery. The full billing functionality runs on the hosted gateway — register as an operator and proxy your MCP servers through it.
AI Agent → MCP Billing Gateway → Your MCP Server
(billing enforced here)Register as an operator and get an API key
Register your MCP server URL + pricing plan
Point callers to your proxy slug: https://mcp-billing-gateway-production.up.railway.app/proxy/{your-slug}/mcp
Callers pay via Stripe API key or x402 USDC — billing is handled transparently
Per-call billing — charge callers per tool call (fiat or crypto)
Subscriptions — monthly/annual Stripe plans with call limits
Tiered pricing — free tier + paid tiers based on usage
x402 micropayments — accept USDC on Base from AI agents with no API keys
Operator dashboard — track revenue, usage, and callers in real time
MCP transport — full Streamable HTTP MCP transport at /mcp/ endpoint
curl -X POST https://mcp-billing-gateway-production.up.railway.app/api/v1/operator/register \
-H "Content-Type: application/json" \
-d '{"email": "you@example.com", "name": "Your Name"}'Response:
{
"operator_id": "op_abc123",
"api_key": "bg_live_xxxxxxxxxxxx",
"message": "Operator registered successfully"
}curl -X POST https://mcp-billing-gateway-production.up.railway.app/api/v1/servers \
-H "Authorization: Bearer bg_live_xxxxxxxxxxxx" \
-H "Content-Type: application/json" \
-d '{
"name": "My MCP Server",
"upstream_url": "https://your-mcp-server.com/mcp",
"proxy_slug": "my-server"
}'curl -X POST https://mcp-billing-gateway-production.up.railway.app/api/v1/servers/{server_id}/plans \
-H "Authorization: Bearer bg_live_xxxxxxxxxxxx" \
-H "Content-Type: application/json" \
-d '{
"name": "Pay as you go",
"billing_model": "per_call",
"price_per_call_usd_micro": 10000,
"free_calls_per_month": 100
}'{
"mcpServers": {
"my-server": {
"url": "https://mcp-billing-gateway-production.up.railway.app/proxy/my-server/mcp",
"headers": {
"Authorization": "Bearer CALLER_API_KEY"
}
}
}
}Method | Best for | How |
Stripe subscription | Human developers | Monthly or annual plan via Stripe Checkout |
Stripe per-call | Human developers | Credits consumed per tool call |
x402 micropayments | AI agents | USDC on Base, no API keys needed |
# Using the MCP client
result = await session.call_tool("get_billing_info")
print(result)
# {
# "service": "MCP Billing Gateway",
# "version": "0.1.0",
# "payment_methods": ["stripe_subscription", "stripe_metered", "x402_crypto"],
# "features": ["Per-call usage tracking", "Tiered pricing", ...],
# "live_service": "https://mcp-billing-gateway-production.up.railway.app"
# }# 1. Register
API_KEY=$(curl -s -X POST .../api/v1/operator/register \
-H "Content-Type: application/json" \
-d '{"email": "dev@example.com", "name": "Dev"}' | jq -r .api_key)
# 2. Add your server
SERVER_ID=$(curl -s -X POST .../api/v1/servers \
-H "Authorization: Bearer $API_KEY" \
-H "Content-Type: application/json" \
-d '{"name": "my-tool", "upstream_url": "https://my-tool.com/mcp", "proxy_slug": "my-tool"}' \
| jq -r .server_id)
# 3. Set pricing: $0.01 per call, 100 free calls/month
curl -X POST .../api/v1/servers/$SERVER_ID/plans \
-H "Authorization: Bearer $API_KEY" \
-H "Content-Type: application/json" \
-d '{"name": "Starter", "billing_model": "per_call", "price_per_call_usd_micro": 10000, "free_calls_per_month": 100}'
# Callers now connect via: .../proxy/my-tool/mcpAccess your dashboard at:
https://mcp-billing-gateway-production.up.railway.app/dashboardTrack revenue, usage, active callers, and configure your servers in real time.
Endpoint | Method | Description |
| POST | Create operator account |
| GET | View profile and API keys |
| GET | Revenue and usage stats |
Endpoint | Method | Description |
| POST | Register an MCP server |
| GET | List your servers |
| POST | Create pricing plan |
Endpoint | Method | Description |
| ANY | Proxied calls with billing enforcement |
| ANY | Streamable HTTP MCP transport |
┌─────────────┐ ┌──────────────────────┐ ┌──────────────────┐
│ AI Agent / │────▶│ MCP Billing Gateway │────▶│ Your MCP Server │
│ MCP Client │◀────│ (hosted on Railway) │◀────│ (upstream) │
└─────────────┘ └──────────────────────┘ └──────────────────┘
│
├── Payment verification (Stripe / x402)
├── Usage tracking & rate limiting
├── Tier enforcement
└── Operator dashboardThe gateway is a transparent proxy. Callers interact with your MCP server normally — the gateway intercepts requests, verifies payment, tracks usage, and forwards to your upstream server.
The gateway is open for use at the hosted URL above. For self-hosted deployments, clone the server repository and deploy via Docker:
docker build -t mcp-billing-gateway .
docker run -p 3000:3000 mcp-billing-gatewayUnclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
MCP server integrating with Stripe - tools for customers, products, payments, and more.
Stripe MCP Pack — read-only access to Stripe data via API key.
A MCP server built for developers enabling Git based project management with project and personal…
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/sapph1re/mcp-billing-gateway-sdk'
If you have feedback or need assistance with the MCP directory API, please join our Discord server