AI News

Daily curated updates on AI tools, models, and the companies building them.

MCP 2026-07-28: what the stateless revision breaks in your server or client, and when migrating is worth it
6 minutes ago

MCP 2026-07-28: what the stateless revision breaks in your server or client, and when migrating is worth it

The Model Context Protocol's 2026-07-28 revision turns MCP from a stateful, bidirectional protocol into a stateless request/response one. The initialize handshake and the Mcp-Session-Id header are gone; each request now carries its protocol version, client identity and client capabilities in _meta, and state that must survive across calls has to travel as an explicit, server-minted handle passed as a tool argument. Server-initiated roots/list, sampling/createMessage and elicitation/create are replaced by Multi Round-Trip Requests: the server returns a result marked input_required with the requests it needs answered, and the client retries the original call with inputResponses. Streamable HTTP now requires Mcp-Method and Mcp-Name headers, list and read results carry ttlMs and cacheScope, and authorization is hardened around RFC 9207 issuer validation and a formal shift away from Dynamic Client Registration toward Client ID Metadata Documents. Roots, Sampling, Logging and the legacy HTTP+SSE transport are deprecated inside a minimum twelve-month window. The TypeScript SDK splits into v2 packages while v1.x stays frozen at 2025-11-25, and the Python SDK is on a 2.3.0 line. The release post names Go and C# as day-one Tier 1 SDKs and Rust as beta, but this evidence carries no version numbers for them, and the claimed performance gains are vendor statements rather than independent measurements.

AI tool news in your inbox

Get the latest AI workflows to boost your productivity and business performance, delivered weekly by expert consultants.