How to Monetize an MCP Server: 5 Business Models That Work in 2026

The most reliable way to monetize an MCP server is to make it part of a product people already pay for. A second option is to sell access directly, with subscriptions, API keys or pay-per-call pricing. Newer machine payment protocols, such as x402 and Stripe's Machine Payments Protocol, let AI agents pay per request without a checkout page.

The MCP specification itself does not include billing. Payment happens around the protocol: in your sign-in, your API keys, a marketplace, or a payment layer. This guide covers five models, what each needs, and the store rules that limit them. Sources were checked on 2 November 2026.

First, decide what you are selling

An MCP server is a connector. Customers rarely pay for the connector itself. They pay for the data, the service behind it, or the time it saves.

Ask three questions before choosing a model:

1. Who pays? A company buying seats, a developer buying API calls, or an agent paying per request.
2. What is metered? Seats, calls, records, compute or outcomes.
3. Where do buyers find you? Your own site, an AI app's directory, or a marketplace. Our guide on where to sell or list your MCP server covers the channels.

Model 1: Bundle it with a paid product

This is how most large vendors do it. The MCP server is free to connect, but it only works for users with an account and plan. Access follows the customer's existing permissions.

Vendors increasingly meter the AI-heavy parts. dbt Labs' MCP docs say "text_to_sql is also the only tool that consumes your dbt Copilot action allotment." Figma's MCP server guide says writing to the canvas is free during beta and will eventually become usage-based.

Best for: SaaS companies. The server increases retention and makes your product the one AI agents can use.

What you need: OAuth sign-in tied to your accounts, plan checks on each call, and clear docs on which plan unlocks which tools. See MCP authentication and OAuth.

Model 2: Subscriptions or API keys

If the MCP server is the product, for example a data feed or a specialist tool, you can sell access like any API. Customers subscribe on your website and get an API key or OAuth login. Your server checks the plan and usage on every call.

Best for: Data providers and niche tools with a clear audience.

Watch out: Store rules can block in-app selling. OpenAI's plugin submission guidelines say selling "digital products or services," including "subscriptions, digital content, tokens, or credits," is "not allowed." Plugins may not "promote upgrades," and may not link directly to a checkout page. Users can still sign in to an account they already pay for. Plan your sales path outside the AI app.

Model 3: Pay per call through a marketplace

Marketplaces handle billing so you do not have to.

Apify is a clear example. Its monetization docs list "Pay per event (PPE)" and "Pay per usage." The docs say "Apify keeps 20% of your Actor's revenue as a commission," and for pay-per-event Actors, "Apify deducts platform usage costs from your payout." Its docs also describe "Agentic payments" that let agents run Actors without an Apify account.

AWS Marketplace is the enterprise route. AWS announced an AI agents and tools category on 16 July 2025, where listings can show MCP support and customers can deploy through Amazon Bedrock AgentCore. AWS's page says partners can "offer flexible pricing" but does not list the models; check the seller guide.

Best for: Small teams that want billing, invoicing and discovery handled.

Model 4: Machine payments (agents pay per request)

This is the newest model. An agent calls a paid tool, the server answers "payment required," the agent pays, and the call goes through. No signup, no card form.

Two protocols lead:

• x402. The x402 site calls it "an open, neutral standard for internet-native payments" built on HTTP status 402. Cloudflare's Agents docs show a paidTool that charges per MCP tool call.
• Machine Payments Protocol (MPP). Stripe introduced MPP on 18 March 2026, co-authored with Tempo.

Stripe's machine payments docs say it supports both. Card payments through Shared Payment Tokens have a 0.50 USD minimum, and stablecoin payments a 0.01 USDC minimum. Payments "land directly in your Stripe balance and settle in fiat."

Best for: Low-price, high-volume tools where a subscription is overkill. Our explainer on MCP payments with x402 and Stripe covers the mechanics.

Watch out: Claude's connector review criteria list connectors that "Transfer money, cryptocurrency, or other financial assets" as an unsupported use case for the directory. A paid-per-call server can still be added as a custom connector, but plan distribution with that in mind.

Model 5: Services around the server

Some teams give the server away and sell setup, custom tools, hosting or support. Open-source projects often follow this route. It works when the server is a door to a bigger engagement. The cost side is covered in our guide to MCP server development cost.

Comparing the models

Pricing tips

• Price the outcome, not the call. A "find 50 leads" tool is easier to value than "API request."
• Keep reads cheap or free. Let agents explore before they pay.
• Cover your costs. On metered platforms, model hosting, upstream API fees and commission before you set a price.
• Show prices to the agent. Machine payment protocols return the price in the 402 response, so the client can decide.
• Add spending caps. Buyers trust tools that cannot run up a surprise bill.

Next step

Pick one model and test it with a small group before you build billing for all five. Then make the server easy to find: our guide on how to market an MCP server covers the registry, directories and search. eSEOspace's MCP marketing team helps MCP companies with positioning, docs and launch pages.

Frequently asked questions