Fetching from the wire…
01
02
03
04
05
06
07
08
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.
Google released MCP / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (Google released MCP); both cover MCP, Python, Redis, SEP; overlapping topics (client, server, session).
Linked by a graph relationship (Google released MCP); both cover MCP, Redis, Session; overlapping topics (client, core, server, session).
Linked by a graph relationship (Google released MCP); both cover MCP, Redis, Session; overlapping topics (client, server, session).
Firebase built by Google / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (Firebase built by Google); both cover Google, MCP; reported by the same outlet (developers.googleblog.com).
Google released MCP / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (Google released MCP); both cover MCP, SEP, Session; overlapping topics (server, session).
Linked by a graph relationship (Google released MCP); both cover Concretely, MCP; overlapping topics (balancing, concretely, server, session).
Linked by a graph relationship (Google released MCP); both cover MCP, Redis; overlapping topics (client, handshake, server, spec).
Microsoft competes with Google / Shared entities / Same source domain / Earlier coverage / Tension
Linked by a graph relationship (Microsoft competes with Google); both cover Google, MCP; reported by the same outlet (developers.googleblog.com).