Anthropic donated the Model Context Protocol to the Linux Foundation's new Agentic AI Foundation (AAIF). OpenAI and Block co-founded it. Google, Microsoft, AWS, and Cloudflare are supporting members.
This is the single biggest structural change to MCP since launch. Here's what it means if you build MCP servers.
What Actually Happened
Three things:
MCP is no longer owned by Anthropic. It's now governed by a neutral foundation under the Linux Foundation umbrella, alongside projects from Block (goose) and OpenAI (AGENTS.md).
The founding members read like a who's-who of tech. Anthropic, Block, OpenAI as co-founders. Google, Microsoft, AWS, Bloomberg, Cloudflare as supporting members. That's not a spec maintained by one company anymore. That's an industry standard.
MCP Dev Summit is happening April 2-3 in NYC. First in-person gathering of the MCP ecosystem. Protocol evolution, tooling, and governance will all be on the table.
Why This Matters for Server Builders
1. Protocol Stability Is Now Guaranteed
When one company controls a protocol, it can change direction based on business strategy. A Linux Foundation project has formal governance, working groups, and a change process that prevents breaking changes from shipping on a whim.
If you're building a business on MCP, this removes the biggest risk: platform dependence on Anthropic's roadmap.
2. Adoption Ceiling Just Got Higher
Enterprise IT departments care about governance. "We use MCP, which is governed by the Linux Foundation" is a different conversation than "We use MCP, which Anthropic maintains." Red Hat is already building MCP into OpenShift AI with RBAC and OAuth lifecycle management.
More enterprise adoption means more users for your server. More users means more revenue potential.
3. The Monetization Layer Is the Next Frontier
The protocol itself is solved - 97M+ monthly SDK downloads, 11,000+ servers, adoption across every major AI platform. What's not solved is how builders make money.
Right now, less than 5% of MCP servers generate any revenue. The gap between "massive adoption" and "zero monetization" is where the next wave of tooling gets built.
Several approaches exist:
- Usage-based billing (Agent Bazaar, Xpack) - charge per tool call. Works for high-value, low-volume tools. Requires auth and metering infrastructure.
- Marketplace listing (MCPize, MCP Hive) - list on a discovery platform that handles payments. Good distribution, but you give up 15-30% and depend on their traffic.
- Contextual advertising (agentic-ads) - include relevant sponsored results alongside tool responses. 20 lines of code, 70/30 split. Works for high-volume tools with search/recommendation contexts.
- Freemium/subscription - build a SaaS wrapper around your MCP server with free and paid tiers.
- Enterprise licensing - sell direct to companies with SLAs and support.
The right model depends on your tool category, user volume, and how much infrastructure you want to maintain. Low-volume, high-value tools should charge directly. High-volume, utility-style tools should consider ads or marketplace placement.
4. Standards for Advertising Are Coming
The AdCP (Ad Context Protocol) consortium - Yahoo, PubMatic, Magnite, Raptive, Media.net, and 20+ others - is building open standards for advertising within MCP. Their founding member window closes March 31.
Amazon Ads has an MCP server in open beta. Dstillery shipped DS-1, an MCP-native audience builder integrated with The Trade Desk. These are billion-dollar companies building ad infrastructure for the same protocol your server runs on.
Advertising demand for MCP inventory will grow as these standards mature. If your server handles queries where users are comparing, choosing, or discovering products/services, that context is valuable to advertisers.
What to Do Now
If you're building a new MCP server:
Pick a monetization model before you launch. Adding revenue infrastructure after users expect a free tool is harder than including it from day one.
If you have an existing server with users:
Start tracking tool call volume, unique users, and query patterns. This data is the foundation for any monetization approach. You need it whether you charge directly, sell ads, or license to enterprises.
If you're considering the MCP Dev Summit (April 2-3, NYC):
Go. The governance discussions will shape what the protocol looks like in 2027. The people making decisions about MCP's future will be in the room.
The Bottom Line
MCP moving to the Linux Foundation doesn't change what the protocol does. It changes how confident you should be building on it. Platform risk is lower. Adoption ceiling is higher. The remaining gap - monetization infrastructure - is where the building is happening now.
11,000 servers. 97M monthly downloads. Less than 5% monetized. That gap is the opportunity.
Building an MCP server and thinking about monetization? The agentic-ads repo has a working ad network with a 10-minute integration path. Or check the live API to see it running.
Top comments (0)