DEV

Model Context Protocol (MCP) 2026 Spec Shifts to Stateless

By Dillip Chowdary July 29, 2026 4 min read
Model Context Protocol (MCP) 2026 Spec Shifts to Stateless

The technical committee governing the Model Context Protocol (MCP) has released the 2026-07-28 specification update. The major change shifts the standard transport model from stateful WebSockets to a stateless, query-response HTTP/3 architecture.

This transition reduces connection handshake overhead, improving performance for high-frequency agentic queries. Engineers building MCP integrations can structure their REST endpoints using [Code Formatter](/tools/code-formatter/).

Tech Pulse Daily

Get tomorrow's tech pulse first

Deeply analytical tech news delivered to your inbox every morning. Free, no spam.

Moving from Websockets to Stateless HTTP/3

The stateless design simplifies load balancing and scaling for enterprise deployments. Rather than maintaining active socket connections, servers can process context requests as independent, isolated calls.

Optimizing Latency for Agentic Workflows

The committee has published a migration guide and updated SDKs for Python and TypeScript, encouraging developers to transition their plugins to the new standard.

Key Takeaway

The Model Context Protocol (MCP) 2026-07-28 specification update shifts to a stateless transport model, reducing connection overhead.