MCP Meter is a per-call metering and billing proxy for the Model Context Protocol that authenticates, routes, debits, and pays out for every MCP tool call.
What is MCP Meter?
MCP Meter is a managed proxy that sits between AI agents (Claude, Cursor, OpenAI, etc.) and MCP servers. It authenticates requests using bearer keys, forwards JSON-RPC calls, meters usage per call, and writes ledger rows. Built by the MCP Meter team, it provides a single endpoint (https://proxy.mcpmeter.com/{slug}) for all paid MCP calls.
Key Features
- Per-call metering — Every tool call is metered to the microcent, reconciled nightly, and paid out on the 1st of the month.
- 500 free calls on signup — No credit card required; enough to test integration.
- Stripe Connect payouts — Publishers receive payouts monthly via Stripe Connect Express, with $50 minimum payout and 10% platform fee for first 100 publishers.
- Open-source proxy — The proxy code is available on GitHub for transparency; no payload retention (metadata only).
- Live demo mode — A simulated stream shows real-time calls, latency, status codes; a live proxy endpoint allows testing without signup (5 calls/minute/IP).
- Works with major clients — Integrates with Claude Desktop, Cursor, OpenAI, OpenRouter, Continue, Cody via standard bearer auth.
- Spending caps and pre-paid credits — Consumers can set per-project monthly caps and buy credit in advance.
- Publishers set their own prices — Per-call pricing set by publishers; platform default is $0.0002/call for demo tools.
Who is it for?
- MCP server publishers — Create an account, list a server, set a per-call price, and get paid monthly via Stripe Connect without writing billing code.
- AI agent developers — Use one API key across multiple MCPs, pay only for calls made, and track usage per project with spending caps.
- Teams testing MCP integrations — Claim 500 free calls to wire up a client and observe calls in the live ledger before committing.
What can you do with MCP Meter?
- Indie MCP publishers: List an MCP server (e.g., weather, currency conversion, Wikipedia) and set a micro-price per tool call; receive payouts on the 1st of every month via Stripe.
- Hobbyist AI developers: Connect Claude Desktop or Cursor to multiple MCPs using a single bearer key, monitor usage in the dashboard, and avoid surprise bills with hard spending caps.
- Product teams evaluating MCPs: Use the live proxy without signing up to test latency and response quality across demo tools like echo, time, dad jokes, and UUID generation.
How does MCP Meter work?
- Sign up for a free account (no credit card required) and receive ~500 free calls.
- Mint a SHA-256 hashed API key (shown once) and configure it in your agent's MCP settings.
- Set the proxy URL (https://proxy.mcpmeter.com/{slug}) with the bearer key. Every subsequent tool call is authenticated, forwarded, metered, and recorded in the usage ledger.
Pricing
Freemium: 500 free calls on signup. After that, per-call pricing set by publishers (platform default ~$0.0002/call). Consumers can buy pre-paid credits. Publishers pay a 10% platform fee (first 100 publishers) or 20% standard fee. No subscription fees.
FAQ
Is MCP Meter free to start?
Yes. Signup gives 500 free calls with no credit card required. You can also try the live proxy without signing up (rate-limited to 5 calls/minute/IP).
How are publishers paid?
Publishers receive payouts via Stripe Connect Express on the 1st of each month, with a $50 minimum payout. The platform fee is 10% for the first 100 publishers (locked for 12 months) and 20% thereafter.
Does the proxy retain my payloads?
No. The proxy is open-source and records only metadata. Payloads are not stored.
How does billing work for consumers?
You buy pre-paid credits that never expire. Each call debits the publisher-set price. You can set per-project monthly spending caps; the proxy returns a 402 status if exceeded.
