How to monetize an MCP server
A publisher’s guide: charge per call for your MCP tools with Obolo as your merchant of record. You bring the tools; Obolo handles billing, taxes and payouts.
Why monetize with Obolo?
Obolo is an MCP server gateway and marketplace for the agent economy. An agent connects to one endpoint with one API key per API, and pays per tool call from a prepaid balance, with hard spend caps and audit logs. For you, the publisher, that means you don’t have to build billing, metering or collections — you focus on the tools.
Obolo acts as the merchant of record. It charges the buyer, collects and remits taxes where required — including across Latin America — and settles your share. The split is 80 / 20: the publisher keeps 80% of what’s charged for its tools. MCP gateway, glosario.
The 5 steps
- Understand why (merchant of record + 80/20)
As merchant of record, Obolo owns the billing relationship with the buyer: it issues the charge, handles taxes and jurisdictions (incl. Latin America) and pays you your 80%. You never touch cards, disputes or tax withholding. That drops the bar to monetize an MCP server down to “connect it and set a price.”
- List or claim your server (crawled vs self-published)
Two paths. If your server is already indexed in the public catalog (the “crawled” tier 1: metadata only, no ownership check), you claim it. If it’s new, you self-publish it. Either way you prove ownership with a DNS-TXT challenge: you add a TXT record on your domain to show you own it. Without proven ownership you can’t charge or settle.
- Set pricing (per-call or subscription)
Pick a model: per-call (commonly US$0.005–$0.02 per tool call, based on your tool’s real cost) or a monthly subscription. The price is deducted from the buyer’s prepaid balance on every call; when they hit their spend cap, Obolo returns a 429 and never overcharges. You can price each tool differently within the same server.
- Reach the “verified” tier (tier 2)
The verified tier proves ownership (DNS + registry) and runs your declared schema through static analysis that produces a stable canonical hash. That hash is your drift protection: if the real schema of your tools deviates from the declared, verified one, Obolo detects it and freezes payout instead of letting a rug-pull through. Verified is the trust signal that makes agents pick you.
- Get paid (Stripe Connect or USDC)
Payouts go out via Stripe Connect or USDC. Ownership verification is required to settle: until you’ve proven the server is yours, funds don’t move. Once verified and with a payout account connected, you collect your 80% on a recurring basis as agents use your tools.
Connection example (.mcp.json)
Once published, your server lives behind Obolo’s per-API endpoint. The agent connects over Streamable HTTP + JSON-RPC 2.0 with an `obl_…` key:
{
"mcpServers": {
"your-api": {
"type": "streamable-http",
"url": "https://api.obolo.dev/mcp/{serverId}",
"headers": {
"Authorization": "Bearer obl_live_xxxxxxxxxxxx"
}
}
}
}Per-tool pricing example
You can set a price per tool. Example (values are illustrative):
# per-tool pricing (illustrative) geocode.forward US$0.005 / call geocode.reverse US$0.005 / call places.search US$0.02 / call # → billed from the buyer's prepaid balance # → publisher keeps 80%
Payment rails
Buyers can fund their balance with Stripe, prepaid USDC or x402. You don’t pick the buyer’s rail: you get paid in your payout (Stripe Connect or USDC) regardless of how the agent paid. x402, security.
Get started
Keep reading
Docs · Compare · Catalog · Operator · MCP gateway