Fetching from the wire…
01
02
03
04
05
06
07
08
Top 5 · 2026-05-25 · source-backed
The protocol that powers 14,000+ servers just made a breaking architectural change. If you run an MCP server, your migration clock started four days ago.
The Model Context Protocol specification release candidate, locked May 21, removes the initialize/initialized handshake and the Mcp-Session-Id header entirely. The protocol is now stateless at the transport layer. Any request can land on any server instance without sticky routing. For anyone running MCP servers behind a load balancer with session affinity, this changes how you deploy.
The RC also introduces an Extensions framework with two official extensions: MCP Apps (servers that render HTML interfaces) and Tasks (long-running work that persists across requests). Six authorization hardening changes align MCP with OAuth 2.0 and OpenID Connect. There's a formal deprecation policy now, with 12-month minimum windows for breaking changes going forward.
Timeline: final specification publishes July 28, 2026. Tier 1 SDKs expected to ship support within a 10-week validation window.
I think going stateless is the right call. Stateful protocols are painful at scale. Sticky sessions create single points of failure. Session migration during deployments is a nightmare. But "right call" doesn't mean "easy migration." Every MCP server that relied on the session handshake or stored conversation state in server memory needs to externalize that state to a database or cache.
The Extensions framework is worth paying attention to separately. MCP Apps means servers can now render interactive UIs, not just serve data. Tasks means agents can kick off long-running work and come back for results later. These open up use cases that the original prompt-response MCP couldn't handle.
Context7, the most popular MCP server at 54,000 stars and 890,000 weekly npm downloads, will presumably adapt quickly. But the long tail of 14,000+ community servers is where the pain will be. If you're building on MCP, start reading the RC spec now. Don't wait for the final publication.
Each link below shares sources, entities, or timing with this story.
The 2026-07-28 Model Context Protocol spec published today, and it removes two things every MCP server currently depends on: the initialize/initialized handshake and the Mcp-Session-Id header. Both are gone. Not deprecated. Gone from the core. (Model Context Protocol Blog) Wha...
You have one week. If you run an MCP server in production, stop what you're doing and read the release candidate. The Model Context Protocol's 2026-07-28 spec is the largest revision since the protocol launched, and the headline is architectural: the initialize/initialized han...
The Model Context Protocol's 2026-07-28 revision is the biggest change since the protocol existed. The core is now stateless request/response instead of a bidirectional stateful session. Authorization aligns with OAuth 2.1 and OpenID Connect. MCP Apps and Tasks moved under a v...
Eighteen days. That's how long you have. The 2026-07-28 MCP specification release candidate removes the session concept from the protocol layer entirely. The initialize / initialized handshake is gone. The Mcp-Session-Id header is gone. Protocol version, client identity, and c...
The MCP team shipped the RC for the next spec, and the headline is statelessness at the protocol layer via six coordinated SEPs, plus an Extensions framework, Tasks, MCP Apps, authorization hardening, and a formal deprecation policy. Source: Model Context Protocol Blog The pra...
Ten days. That's the window. The MCP 2026-07-28 release candidate drops the initialize/initialized handshake entirely. Protocol version, client info, and capabilities now ride in _meta on every request, with a new server/discover method if you want to fetch capabilities upfron...
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.