The plug your AI agents connect through just went stable
The Model Context Protocol (MCP), the common standard agents use to reach tools and data, published its largest revision since launch on 28th Jul’26. The headline change makes the protocol stateless: the initialise handshake and session ID are removed, so a remote MCP server that once needed sticky sessions and a shared session store can now run behind a plain load balancer. Long-running work (Tasks) and server-rendered UIs (MCP Apps) move into a new first-class extensions framework. The release contains breaking changes: Roots, Sampling and Logging are deprecated, tools/call now requires routing headers, and anyone who built against the experimental Tasks API must migrate to the new lifecycle.
What it actually means
For a month this Digest has argued about which model you rent. This is the layer underneath that, the wiring and it just stopped being a target. Two things here. If you built MCP servers or agents against last year's spec, budget a migration pass: the session is gone, Tasks now work differently, and a few methods are now deprecated. The model is the part everyone argues about. The wiring is the part that decides whether what you shipped last quarter still runs next quarter.
The model is what everyone argues about.
12 monthsnotice before any MCP feature is removed
Source: Model Context Protocol · Tuesday, 28 July 2026