Fetching from the wire…
Infra2026-08-06 · source-backed
Google published the explainer August 5 for the 2026-07-28 spec, which removes the initialize/initialized handshake (SEP-2575) and the Mcp-Session-Id header (SEP-2567), making the protocol core stateless. Google led it via PR #2575 and co-founded the MCP Transports Working Group with Hugging Face because it needed MCP to scale across millions of concurrent queries. Concretely: sticky-session load balancing dies, Redis session stores die, MCP servers can scale to zero on Cloud Run. Python ships as mcp[cli]==2.0.0b1, Go as v1.7.0, TypeScript split into separate server and client betas. If you built session affinity into your MCP deployment, that's now dead weight.
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...
Ten days from spec to shipped client. That's fast even for this ecosystem. The MCP 2026-07-28 revision replaced the bidirectional stateful protocol with request/response. Every request now independently carries protocol version, client identity and capabilities. Cloudflare's t...
If you wrote an MCP server before July, it's on a protocol shape the maintainers have already removed. Not deprecated-with-a-migration-window. Removed from the spec. MCP lead maintainers David Soria Parra and Den Delimarsky published an updated roadmap on August 22, and the re...
Six clients. One manifest. Zero vendor lock. Vercel published Agent Plugins 1.0.0 on August 6, an openly licensed spec that bundles Agent Skills and MCP servers behind a single portable manifest. The shape is deliberately boring: a plugin.json requiring only schemaVersion and...
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...
upstash/context7 (60,590 stars) shipped @upstash/[redacted] on August 7 on the 2026-07-28 protocol revision. HTTP serving is now stateless for both modern and legacy clients, and Redis-backed sessions are gone, which is a real operational simplification for anyone self-hosting...
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.