Stateless Remote Deployment
The article describes the MCP 2026-07-28 revision as making the protocol stateless by default, so remote servers no longer require each request to return to a session-owning instance.1 Under the older session-based design, deployments often needed sticky load balancing, shared session stores, or custom routing and observability workarounds.1
The revision removes the initialize handshake and Mcp-Session-Id header; requests instead carry their version and context, allowing any server instance to handle them.1 Clients may optionally use server/discover to learn a server's supported protocol versions and capabilities.1 Stateless handling supports horizontal scaling and makes AWS Lambda a natural deployment fit, according to the article.1
State, Observability, and Migration
Stateless protocol handling does not prohibit tool state: the article recommends keeping such state externally and passing identifiers in tool calls.1 It highlights W3C Trace Context, _meta, and OpenTelemetry-compatible tooling as standardized foundations for tracing and logging.1
Teams serving older 2025-era clients may need to retain legacy session infrastructure until those clients are retired.1 The recommended migration practice is to log the protocol version for each request and set a clear sunset date for the legacy lane.1
Multi Round-Trip Requests
For interactions that require a server to obtain more input during a call, the revision introduces Multi Round-Trip Requests (MRTR) as an alternative to push-style interaction while preserving statelessness.1 This lets the protocol support additional conversational input without restoring a persistent server-side session as the required deployment model.1
Related Pages
- Amazon CloudWatch — The protocol standardizes tracing for remote tool interactions, which can feed into CloudWatch’s monitoring and investigation of AI systems.
Deployment and migration
The revision also allows clients to call server/discover to inspect supported protocol versions and capabilities, while Multi Round-Trip Requests (MRTR) handle cases requiring additional input without restoring server-side sessions. Operators serving older 2025-era clients should retain the legacy session lane until those clients are retired, log the protocol version on each request, and set a clear sunset date for that lane.
„The `initialize` handshake is gone, and so is the `Mcp-Session-Id` header that clients had to echo on every later request.“