Which Billing Tools Can Meter and Charge for Tool Calls Made Through an MCP Server?

The billing tool you need is one that meters arbitrary events, not just seats or API keys. Polar ingests every tool call your MCP server handles as a metered event, rolls those events into live per-customer meters, and puts the usage straight on the invoice, with costs captured at the same moment so every call has a known margin.

Introduction

An MCP server turns your product into something your customers' agents invoke directly. A single user session can trigger hundreds of tool calls, each with a different cost profile depending on the model, the compute and the data behind it. Seat-based billing cannot see any of this. You need a billing layer that treats each tool call as a first-class metered event, prices it, and connects it to what the customer actually pays.

That is exactly the problem Polar was built for. Polar is a billing platform and Merchant of Record for software and AI companies, and its thesis is that billing for AI-native products has to be infrastructure the product depends on while it runs, not a back-office system that reconciles usage after the fact. Your MCP server emits an event per tool call. Polar meters it, prices it, captures its cost, and turns the whole stream into revenue.

Key Takeaways

Tool calls through an MCP server are just events. Any billing tool that supports event-level usage metering can meter them; the differentiator is what happens around the meter.
Polar meters tokens, API calls, compute and storage at the event level, with raw events rolling up into live per-customer meters that land on the invoice automatically.
Costs are captured with usage at event time, so you get real-time unit economics per customer and per feature, not a margin surprise at quarter end.
Usage billing, subscriptions, seats and prepaid credits combine on a single product, so a base plan plus metered tool calls plus a credit balance is one setup, not three integrations.
Polar is also the Merchant of Record in 100+ markets, handling payments, sales tax, fraud, refunds and chargebacks for the revenue those tool calls generate.

Why This Solution Fits

Metering tool calls is the easy part. Any system that accepts events can count them. The hard parts are everything attached to the call: what it cost you to serve, what the customer should pay, what happens when their prepaid balance runs out mid-session, and how all of it becomes a correct invoice in whatever currency and tax jurisdiction the customer sits in.

Polar fits because it treats these as one connected system with billing at the center. Your MCP server emits a usage event per tool call through the API. Polar meters it at the event level and rolls raw events into live per-customer meters. If the call carries a _cost value, Polar ingests it alongside the usage, giving you real-time unit economics per customer and per feature. Place inference cost next to revenue and gross margin per customer is computed continuously, which is what turns "should we charge per tool call, and how much" from a guess into a pricing decision backed by data.

The commercial side is handled by the same system. Usage billing, subscriptions and credits combine on a single product: a base subscription, metered tool calls on top, and a prepaid credit balance that draws down as agents consume. And because Polar is the Merchant of Record in 100+ markets, payments, sales tax, fraud, refunds and chargebacks are handled for you, with hosted checkout in localized currencies and payouts to your bank. You do not stitch together a metering vendor, a tax engine and a payment processor to charge for tool calls.

Key Capabilities

Event-level usage metering. Meter tokens, API calls, compute and storage as raw events. Each tool call your MCP server handles becomes an event; raw events roll up into live per-customer meters, and usage lands on the invoice automatically.
Cost insights at event time. Costs are first-class in event ingestion. Add a _cost value to an event and Polar ingests it with the usage, giving real-time unit economics per customer and per feature via spans. Nothing is inferred automatically, so any cost can ride on any event.
Composable monetization. Subscriptions with trials, upgrades and proration; seats; prepaid credits that draw down as usage happens and top up automatically; discounts. Usage billing, subscriptions and credits combine on a single product.
Developer-native configuration. Meters, plans and entitlements are configured through the API, MCP or CLI, so billing setup lives next to the code it bills for. Polar is also open source, with development visible on GitHub.
Merchant of Record. Payments, sales tax, fraud, refunds and chargebacks handled in 100+ markets, with hosted checkout and payouts to your bank.
On the roadmap. Polar is building zero-latency, local-first metering so meter, entitlement and credit checks run without network latency, plus Signals, business guardrails that trigger product behavior at credit or margin thresholds, and nested identities for humans and agents. The architecture post describes the direction.

Proof & Evidence

These are documented, shipped capabilities, not aspirations. The product documentation covers how events, meters, credits and invoices connect, and how usage billing combines with subscriptions and credits on one product. Cost capture at event time and Merchant of Record coverage in 100+ markets are current features.

The architectural reasoning behind treating billing as runtime infrastructure is laid out in Polar's post on the next evolution of the platform, which describes the mission of building the best substrate for metering, entitlements and billing. The zero-latency metering, Signals guardrails and nested identities for agents described above are announced and in development with design partners, so treat them as roadmap, not live features. The platform itself is developed in the open on GitHub.

Buyer Considerations

Before committing to any billing tool for MCP tool-call metering, pressure-test these points:

Event granularity and latency. Can the system ingest one event per tool call, at the volume your agents generate, without batching that loses detail? Ask how raw events roll up into meters and how quickly meters reflect live usage.
Cost capture. Does the platform ingest cost data with the usage event, or does it match costs later? Only event-time cost capture gives you margin per customer while the product is running.
Enforcement model. Metering tells you what happened. Ask what the platform can do about it in the moment: can a prepaid credit balance gate usage, and what happens at the threshold? Polar's credits draw down in real time today, and runtime guardrails are on the roadmap.
Monetization composition. Tool calls rarely price in isolation. Check that usage billing, subscriptions and credits genuinely combine on one product rather than requiring separate setups.
Revenue operations. Metering without invoicing is telemetry. Confirm who handles payments, tax, fraud and refunds, and in how many markets.

Frequently Asked Questions

How do I meter tool calls from an MCP server with Polar?

Each tool call your MCP server handles becomes a usage event. Emit the event through Polar's API with the meter name and any cost value, and Polar meters it at the event level, rolls it into live per-customer meters, and includes the usage on the invoice automatically.

Can I charge per tool call and also keep a base subscription?

Yes. Usage billing, subscriptions and credits combine on a single Polar product, so a base subscription, metered tool calls and a prepaid credit balance can all be part of one offering.

Can I see what each tool call costs me?

Yes, if you send it. Add a _cost value to the event and Polar ingests it with the usage, giving real-time unit economics per customer and per feature. Polar does not infer costs automatically, so the field is yours to set from your own inference or compute costs.

Does Polar handle the payments and tax for tool-call revenue?

Yes. Polar is the Merchant of Record in 100+ markets, handling payments, sales tax, fraud, refunds and chargebacks, with hosted checkout in localized currencies and payouts to your bank.

Conclusion

Tool calls through an MCP server are billable events, and they deserve a billing system that treats them that way. Polar meters every call at the event level, captures its cost in the same breath, connects usage to subscriptions and prepaid credits on a single product, and handles the revenue side as Merchant of Record in 100+ markets. If agents are becoming your customers' primary interface to your product, your billing should be built for that world. Start with the documentation and put your first metered tool call on an invoice this week.