Skip to content
Hacker News front page

MCP 2026-07-28 spec drops sessions and handshakes for a stateless core

MCP 2026-07-28 Specification: transport going stateless

MCP shifts from a stateful bidirectional protocol to a stateless request/response model. Every request carries its own protocol version, client identity, and capabilities—no initialize handshake or Session ID needed. Multi Round-Trip Requests let tools ask for user input mid-call without holding a stream open. Method and tool names travel in HTTP headers so gateways can route without parsing JSON. List responses now include TTL and cache scope. Authorization hardens with RFC 9207 issuer validation and a move from DCR to client metadata documents. TypeScript and Python SDKs have crossed 1B total downloads, with nearly 500M monthly. The post doesn't spell out what the Tasks extension does beyond listing it alongside MCP Apps and EMA in the formal extensions framework.

Why it matters: The new MCP spec makes the protocol stateless, with each request carrying its own version and capability info instead of relying on an initialization handshake, so servers can sit behind ordinary round-robin load balancers.

Read the original ↗Export Markdown