MCP Goes Stateless: How AI Infrastructure Is Becoming an Ad Platform

The Stateless Shift Nobody in Advertising Is Talking About

Last week, the Model Context Protocol (MCP) quietly did something radical: it killed the session. The 2026-07-28 spec removed the handshake, the session ID, the whole stateful dance that had defined how AI agents talk to tools. In its place, every request now carries its own protocol version, client identity, and capabilities—meaning any request can land on any server, anytime, with zero baggage.

For infrastructure folks, this is a win. Load balancers can finally breathe. Autoscaling doesn't mean babysitting sticky sessions. But step back for a second, and you'll see something bigger: MCP just turned AI agents into plain old API calls. And that's where the advertising story begins.

What Actually Changed Under the Hood

Before, an MCP conversation started with an initialize handshake, then tracked everything through a Mcp-Session-Id header. Every subsequent request had to find the state tied to that session. If you were running a fleet of servers, you had to keep that state somewhere, drain it during deploys, and pray your load balancer didn't send a request to the wrong instance.

Now? Gone. No session, no handshake, no sticky routing. Each request is self-contained. But here's the part that got less attention: the protocol also added two mandatory HTTP headers—Mcp-Method and Mcp-Name. A tool call now arrives as Mcp-Method: tools/call and Mcp-Name: search, followed by the JSON-RPC payload. The gateway can route, rate-limit, and meter AI traffic without even opening the request body.

Cloudflare's Matt Carey spelled out the upside: your existing WAF, rate limiter, or API gateway can now inspect these headers and act on them, using the same mechanisms they already apply to every other API. One commenter on Hacker News even noted you could copy tool parameters into headers for custom routing. That's not just a technical tweak—it's the moment AI agents became first-class citizens in the infrastructure that advertising already runs on.

Why Advertisers Should Care About Headers

Think about how ad tech works today. When you buy an impression, your DSP sends a bid request to an exchange. That request carries a bunch of headers and parameters—user ID, page URL, device type—and the exchange routes it, prices it, and decides whether to respond. The whole system is built on stateless, routable, metered API calls. It's fast, it scales, and it's boring in the best way.

MCP just made AI agents behave the same way. A tool call is now a routable, rate-limit-able, billable unit. For anyone who's been trying to figure out how to monetize AI agents, this is the missing piece. The infrastructure you already have—your gateways, your billing systems, your observability stack—can now treat AI traffic like any other API traffic. That's not a coincidence; that's the point.

The Gateway Is the New Ad Server

Until now, AI governance sat on top of the protocol. Cloudflare's agent tracing and Azure's AI Gateway layer operated as separate control planes. But with metadata pushed into the transport layer, the systems that already route and meter your API traffic can now see and act on AI requests. That's a shift in where the value sits.

One consultant's audit, posted on r/AI_Agents, found a client's MCP server logged 61 tool calls over three months—58 of them from the client's own engineers. The post's conclusion: teams confuse "agents can access this" with "agents will access this." The author, who disclosed that MCP work is a big chunk of his consulting revenue, drew a blunt conclusion: money is flowing to gateways, registries, and identity layers, not to the servers themselves.

That's the advertising angle. In the same way Google made money not from the content on the web but from the ad server that decided which ad to show, the AI gold rush might not be about the tools—it's about the gateway that decides which tool gets called, how often, and at what price. If you're in advertising, you should be paying attention to who controls that gateway.

What the Skeptics Say (and Why They're Half Right)

Not everyone is cheering. Hacker News lit up with the obvious punchline: "We invented a stateful protocol, found state hard to scale, stripped it out, and ended up with 'just send a POST request.' The REST crowd has been waiting 20 years for this." That's from user luciana1u, and it's not wrong.

Another commenter, bloppe, argued that MCP now looks like a REST API plus a spec that OpenAPI already provides, plus runtime framework authorization—only the last being genuinely new. Defenders counter that MCP's real value is that it's a convention AI providers actually support, so there's incentive to implement it. Sentry's co-founder David Cramer, who'd previously said MCP wasn't good enough, told Cloudflare the new spec finally cleans up authentication and tool handling: "Agents become useful when the underlying plumbing stops being the whole story."

What This Means for the Business of AI

Strip away the protocol talk, and you have a simple story: AI agents are becoming routable, metered, and monetizable. That's the same transformation that turned the web into an advertising medium. When you can count requests, you can price them. When you can route them, you can target them. When you can meter them, you can bill for them.

For advertisers, this opens up a few practical moves:

• Watch the gateway players. Cloudflare, Azure, and others are positioning themselves as the tollbooths for AI traffic. If you're planning ad spend around AI, those are the platforms that will control access and pricing.
• Think about tool-level targeting. With Mcp-Method and Mcp-Name exposed, you can imagine advertising that targets specific tools or actions—say, bidding higher when an agent is about to make a purchase vs. just looking up info.
• Prepare for the migration. Teams running stateful MCP servers will need to move to stateless routes. That's a technical chore, but it's also a chance to rethink how you instrument and monetize agent traffic.

The Bottom Line

The MCP spec is still evolving, and adoption numbers are staggering—Anthropic reports over 400 million monthly SDK downloads, up 3x this year. But the real question isn't whether agents will be adopted; it's who will profit from the plumbing. The stateless shift is a reminder that in tech, the boring infrastructure layers often end up being the most valuable real estate. For advertising, the message is clear: the gateway is the new ad server.

If you're building or buying AI infrastructure, don't just focus on the models or the tools. Ask who's standing at the gate, and what they're charging to let the agents through.