AivexaNewsSearch
AI news for builders and product teamsChecked every hour

Stateless MCP Removes Session Affinity Requirements for AWS Server Deployments

Collected Sep 30, 2026

AWS has outlined how the latest Model Context Protocol (MCP) specification changes remote MCP server deployments by removing protocol-level sessions, allowing requests to reach any available server instance, according to InfoQ's Leela Kumili. 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 specification removes the initialize and initialized handshake and the Mcp-Session-Id header, so requests can be routed independently to any server instance behind a conventional load balancer. It also introduces an optional server/discover operation for clients that need server capabilities before making tool calls.

AWS Architecture Blog authors Anand Komandooru, Steven DeVries, and Haleh Najafzadeh describe replacing session-affine routing with conventional request routing and removing session storage used solely for MCP protocol state. They identify AWS Lambda as a deployment option that fits the request-response model because the protocol no longer requires persistent session connections.

Michael Madsen, writing about the specification on LinkedIn, summarized the change: the protocol is stateless, but applications do not have to be.

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, 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 with side effects.

Apify's MCP server project is implementing stateless support alongside its existing sessionful server, with routing and conformance tests covering both protocol versions. 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 providing a defined migration period for deprecated capabilities.

Read at InfoQ · AI, ML & Data Engineering

Based on reporting from the original publisher. Visit the source for full context and later updates.

Publisher excerpt

AWS details how the latest Model Context Protocol specification removes protocol-level sessions, sticky-session requirements, and session storage for remote MCP servers. The change enables independent request routing and simpler horizontal scaling while shifting application state, retries, observability, and idempotency concerns to other layers. By Leela Kumili