MCP’s biggest update removes the machinery many servers were built around
The New Stack Janakiram MSV
The Model Context Protocol's next major version (arriving July 28) removes sessions and the initialization handshake, shifting from stateful to stateless architecture so remote servers can run like ordinary HTTP services without specialized machinery. The core changes include moving protocol version and client capabilities into request metadata, replacing hidden session state with explicit handles visible to models, and adding caching hints via ttlMs and cacheScope fields. Developers gain simpler deployment (round-robin load balancing without session affinity), platform teams get better routing via headers, and the ecosystem gains a formal extension governance model, though adopters must migrate existing server integrations and authentication patterns.
Why it matters
The biggest update to the Model Context Protocol (MCP) since its launch is almost here. Lead maintainers froze the release The post MCP’s biggest update removes the machinery many servers were built around appeared first on The New Stack.
