get_billing_info
Get information about the MCP Billing Gateway service and integration options.
LABSCO SUMMARY
The installable piece is a signpost; the product is the proxy that goes in front of your server.
get_billing_info is the whole local surface — it reports what the gateway supports and where to read further. The work starts when you register a server and point callers at /proxy/{slug}/mcp, after which payment verification, usage tracking and tier enforcement sit between the caller and your upstream with no billing code of your own. The x402 rail is what makes this usable by autonomous callers: USDC on Base with no key to issue, next to the Stripe options that suit human developers. If routing your traffic through someone else's proxy is the sticking point, the gateway ships as a Docker image you can run yourself.
What it is
A hosted billing proxy that sits between callers and an MCP server you operate. Register as an operator, register your server's upstream URL under a proxy slug, attach a pricing plan, and hand callers the proxied URL; the gateway verifies payment, tracks usage and enforces tiers before forwarding each call. The installable package is the discovery side of that — one tool reporting what the service supports and where the integration docs are.
What you get
- get_billing_info returns the service capabilities and the supported payment methods — stripe_subscription, stripe_metered and x402_crypto — with the integration docs alongside
- Registering an operator through /api/v1/operator/register returns an operator id and a bg_live_ API key
- Registering a server takes a name, the upstream_url of your MCP server and a proxy_slug; callers then connect to /proxy/{slug}/mcp instead of reaching your server directly
- A pricing plan sets billing_model, price_per_call_usd_micro and free_calls_per_month — the documented starter plan is 10000 micro-USD a call with the first 100 calls each month free
- Three ways for a caller to pay: a monthly or annual Stripe subscription, Stripe credits consumed per tool call, or USDC on Base over x402, which needs no API key at the caller's end
- The operator dashboard tracks revenue, usage and active callers in real time, with /api/v1/operator/stats behind it
- The gateway speaks Streamable HTTP MCP at /mcp/, and ships as a Docker image if you would rather run the proxy yourself than use the hosted deployment
Requirements
The local package installs with pip install mcp-billing-gateway or runs as uvx mcp-billing-gateway over stdio, and takes no environment variables. The hosted gateway lives at https://mcp-billing-gateway-production.up.railway.app and also answers as a streamable-HTTP MCP server at /mcp/. Operators authenticate to the management API with Authorization: Bearer bg_live_…; callers authenticate to a proxied server with their own key. Self-hosting is a Docker build of the gateway. MIT.
Setup effort
One command — uvx mcp-billing-gateway
USE CASES
01
Charging for an MCP server you already run
Register as an operator, point the gateway at your upstream URL under a slug, and set a per-call price with a free monthly allowance. Callers switch to the proxied URL and nothing in your server changes.
02
Taking payment from agents that have no account
Accept USDC on Base over x402 alongside the Stripe rails, so an autonomous caller can pay without an API key, a card or a signup step.
03
Seeing what your tools actually earn
Revenue, usage and active callers in the operator dashboard, with the same numbers available from the stats endpoint for anything you want to automate.
1 tool
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool when we connected. get_billing_info only returns gateway capabilities and docs; billing, subscriptions and payments run through the hosted REST API, not MCP tools.
Requires
uvx on PATH
Where it runs
Of the 3 documented clients, 2 run the server on your machine and 1 connects to a hosted endpoint.
CONTEXT COST
Light Standing cost
Rated by the size of the one tool definition that rides along on every turn
INSTALLATION
Connect your client
Server setup
TERMINAL
uvx mcp-billing-gatewayMCP Clients
Claude Desktop, Cursor
JSON
{
"mcpServers": {
"mcp-billing-gateway": {
"command": "uvx",
"args": [
"mcp-billing-gateway"
]
}
}
}Any MCP client — remote proxy
For the callers of a server you have registered on the gateway, not for this package. <YOUR_PROXY_SLUG>, in the name and in /proxy/<YOUR_PROXY_SLUG>/, is the proxy_slug you registered, and <YOUR_CALLER_API_KEY> the caller's own key:
ANY MCP CLIENT — REMOTE PROXY · JSON
{
"mcpServers": {
"my-server": {
"url": "https://mcp-billing-gateway-production.up.railway.app/proxy/<YOUR_PROXY_SLUG>/mcp",
"headers": {
"Authorization": "Bearer <YOUR_CALLER_API_KEY>"
}
}
}
}
