Stateless MCP Removes Session Affinity Requirements for AWS Server Deployments

AWS detailed how the latest Model Context Protocol specification removes protocol-level sessions, eliminating the initialize/initialized handshake and the Mcp-Session-Id header so requests can route to any server instance behind a conventional load balancer. AWS Architecture Blog authors Anand Komandooru, Steven DeVries, and Haleh Najafzadeh said the change removes session-affine routing and MCP-only session storage, and named AWS Lambda as a fit for the request-response model; the spec also adds an optional server/discover operation, Mcp-Method and Mcp-Name headers for gateway routing and throttling, W3C Trace Context tracing, and ttlMs and cacheScope caching controls. AWS recommends tracking protocol versions at the gateway and retaining session infrastructure until legacy traffic is eliminated, since stream resumability was removed and clients may need to retry interrupted operations, raising the importance of idempotency for tool calls with side effects.

AWS has outlined how the latest Model Context Protocol MCP specification https://aws.amazon.com/blogs/architecture/mcp-went-stateless-is-your-aws-mcp-server-deployment-well-architected/ changes remote MCP server deployments by removing protocol-level sessions and allowing requests to reach any available server instance. The change eliminates the protocol requirement for sticky sessions and shared session stores, simplifying horizontal scaling while shifting state management and other responsibilities to surrounding infrastructure. The updated MCP specification https://blog.modelcontextprotocol.io/posts/2026-07-28/ removes the initialize and initialized handshake https://modelcontextprotocol.io/specification/2025-11-25/basic/lifecycle and the Mcp-Session-Id header. Requests can therefore be routed independently to any server instance behind a conventional load balancer. The specification also introduces an optional server/discover operation for clients that need server capabilities before making tool calls. AWS diagram showing how MCP changes map to the Well-Architected Agentic AI Lens. Source: AWS Architecture Blog https://aws.amazon.com/blogs/architecture/mcp-went-stateless-is-your-aws-mcp-server-deployment-well-architected/ . For AWS deployments, this can eliminate infrastructure used specifically to maintain MCP protocol sessions. AWS Architecture Blog authors Anand Komandooru https://www.linkedin.com/in/akomandooru/ , Steven DeVries https://www.linkedin.com/in/stevenpdevries/ , and Haleh Najafzadeh https://www.linkedin.com/in/haleh-najafzadeh/ describe replacing session-affine routing with conventional request routing and removing session storage used solely for MCP protocol state. They also identify AWS Lambda as a deployment option that fits the request-response model because the protocol no longer requires persistent session connections. The distinction between protocol and application state has also emerged in community discussion. Michael Madsen https://www.linkedin.com/in/mgm87/ , writing about the specification on LinkedIn https://www.linkedin.com/posts/mgm87 the-release-candidate-for-mcp-2026-07-28-activity-7480623534516355073-uuyH?utm source=share&utm medium=member desktop&rcm=ACoAAArnikgBqzTxA9Y838-O55QUcB2McACIq94 , summarized the change as: The protocol is stateless. Your application doesn't have to be. MRTR https://modelcontextprotocol.io/specification/draft/basic/patterns/mrtr replaces server-initiated requests that previously required held-open streams, allowing multi-step interactions through input required responses and subsequent requests. New Mcp-Method and Mcp-Name headers enable gateway routing and throttling, while W3C Trace Context supports distributed tracing. ttlMs and cacheScope provide caching controls. AWS maps these changes to its Well-Architected guidance for agentic AI https://docs.aws.amazon.com/wellarchitected/latest/agentic-ai-lens/agentic-ai-lens.html , covering monitoring, tracing, security, and tool integration. Stream resumability has also been removed, so clients may need to retry interrupted operations, increasing the importance of idempotency for tool calls that produce side effects. Early implementation work shows that existing infrastructure still requires a transition path. Apify's MCP server project https://github.com/apify/apify-mcp-server/issues/1140 is implementing stateless support alongside its existing sessionful server, with routing and conformance tests covering both protocol versions. Migration therefore remains relevant for deployments supporting earlier MCP clients. AWS recommends tracking protocol versions at the gateway and retaining session infrastructure until legacy traffic has been eliminated. The MCP project has also established a feature lifecycle policy https://blog.modelcontextprotocol.io/posts/2026-07-28/ providing a defined migration period for deprecated capabilities.