claude mcp add mcp-billing-gateway-sdk -- npx -y mcp-billing-gateway-sdk
A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.
Star count
2 ★ · sapph1re/mcp-billing-gateway-sdk · read from the repository page · (checked 2026-10-16 20:00:20)
Source
collected from the punkpeye/awesome-mcp-servers list · type: MCP server
Harvest history
first seen 2026-10-09 · last seen 2026-10-16 · seen 32× · listed by 7 sources
Score
score 703 · 2 ★ · 7 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository sapph1re/mcp-billing-gateway-sdk;first catalogued 2026-10-09;last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.
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 Installation Or with uvx: Configuration for Claude Desktop Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows): Configuration for Cursor Add to .cursor/mcp.json in your project: Restart your editor after adding the configuration to activate the MCP server. Tools | Tool | Description | |------|-------------| | get_billing_info | 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. How it works 1. Register as an operator and get an API key 2. Register your MCP server URL + pricing plan 3. Point callers to your proxy slug: https://mcp-billing-gateway-production.up.railway.app/proxy/{your-slug}/mcp 4. Callers pay via Stripe API key or x402 USDC — billing is handled transparently Features - **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 Quick Start 1. Register as operator Response: 2. Register your MCP server 3. Create a pricing plan 4. Connect callers to your proxied server Payment Methods | 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 | Examples Check gateway capabilities Register and monetize an existing MCP server Operator Dashboard Access your dashboard at: Track revenue, usage, active callers, and configure your servers in real time. API Reference Operator endpoints | Endpoint | Method | Description | |----------|--------|-------------| | /api/v1/operator/register | POST | Create operator account |