How to Monetize Your MCP Server in 5 Minutes
You built an MCP server. Agents are calling it. But you're not earning a cent. Here's how to fix that — in under five minutes, with twelve lines of code.
The Model Context Protocol has over 10,000 servers. Most of them are free. Not “freemium” — just free. Developers build powerful tools, host them on their own infrastructure, pay for compute, and get nothing back.
This isn't sustainable. And it's not how the rest of the software industry works. APIs have Stripe. SaaS has subscription billing. MCP servers have... nothing. Until now.
Agent Bazaar gives your MCP server a billing layer. Agents discover your tools, agree to your pricing, call your tools, and pay you — all through a standard protocol. No custom payment integration. No invoicing. No chasing down agent developers on Discord.
Here's the full setup, step by step.
Install the Bazaar SDK
One package. Works with any Node.js MCP server built on the official @modelcontextprotocol/sdk package.
npm install @noui/bazaar-sdkIf you're using Python, the SDK supports the mcp Python package too:
pip install noui-bazaarRegister on Agent Bazaar
Head to noui.bot/bazaar and create a provider account. You'll get:
- →A provider ID — your unique identifier in the marketplace
- →An API key — for authenticating billing events
- →A trust profile — starts at “unverified” (you can verify your domain and email to boost your trust score)
Verification is optional but matters. Agents using noui.bot's trust layer will prefer verified providers. More trust → more traffic → more revenue.
Wrap Your MCP Server
This is the core step. You have an existing MCP server — a set of tools that agents call. The Bazaar SDK wraps it with billing middleware that meters every invocation, validates the caller's payment token, and emits signed receipts.
import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
import { withBilling } from "@noui/bazaar-sdk";
const server = new McpServer({
name: "my-weather-tools",
version: "1.0.0",
});
// Your existing tool — nothing changes here
server.tool("get-forecast", { city: z.string() }, async ({ city }) => {
const forecast = await fetchWeather(city);
return { content: [{ type: "text", text: JSON.stringify(forecast) }] };
});
// Wrap with billing — one function call
const billedServer = withBilling(server, {
providerId: process.env.BAZAAR_PROVIDER_ID,
apiKey: process.env.BAZAAR_API_KEY,
pricing: {
"get-forecast": {
model: "per-call",
price: 0.001, // $0.001 per call (one-tenth of a cent)
currency: "USD",
},
},
});
billedServer.listen();That's it. Your server now meters every get-forecast call, validates that the calling agent has a valid payment session, and emits a signed receipt (HMAC-SHA256) for both parties.
Set Your Pricing
The SDK supports three pricing models out of the box:
Fixed price per tool invocation. Best for simple lookups and fast operations.
e.g. $0.001/call
Price based on input/output token count. Best for LLM-powered tools and content generation.
e.g. $0.01/1K tokens
Price based on execution time or resource usage. Best for heavy processing, image gen, code execution.
e.g. $0.05/sec
You can mix models across tools. Your weather lookup might be per-call at $0.001, while your satellite imagery tool charges per-compute at $0.05/second.
pricing: {
"get-forecast": { model: "per-call", price: 0.001 },
"get-satellite-img": { model: "per-compute", price: 0.05 },
"summarize-report": { model: "per-token", price: 0.008 },
}Start Earning
Once your wrapped server is live, it shows up in the Agent Bazaar marketplace. Agents browsing for weather tools will find yours, inspect your pricing and trust score, and start calling.
Revenue flows like this:
No invoices. No payment pages. No “contact sales.” The protocol handles everything.
What About Competitors?
You have options. x402 offers crypto-native payments (USDC on L2), but requires wallets on both sides. Moesif and Kong provide enterprise API billing, but require gateway infrastructure. TollBit is building a closed publisher network.
Agent Bazaar is the only solution that combines marketplace discovery + open billing spec + trust primitives in a single SDK. And the billing spec is MIT-licensed — you're not locked in.
The Math
Let's say your MCP server handles 50,000 tool calls per month from various agents. At $0.001 per call, that's $50/month — enough to cover hosting and then some for a side project.
At $0.01 per call (reasonable for tools that hit paid APIs), that's $500/month. A popular MCP server doing 500K calls/month at the same rate: $5,000/month.
The MCP ecosystem is growing exponentially. There were 500 servers a year ago. There are 10,000+ today. Agent traffic is following the same curve. The question isn't whether your tools are worth charging for — it's how long you keep giving them away.
Ready to start?
Register on Agent Bazaar, install the SDK, and start earning from your MCP server today. The whole setup takes less time than reading this article.