--- title: Stateless MCP Removes Session Affinity Requirements for... description: The latest Model Context Protocol specification removes protocol-level sessions, including the initialize/initialized handshake and the Mcp-Session-Id header,... canonical: https://daily.dev/posts/stateless-mcp-removes-session-affinity-requirements-for-aws-server-deployments-iygc8pbe0 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Stateless MCP Removes Session Affinity Requirements for AWS Server Deployments | daily.dev og:description: The latest Model Context Protocol specification removes protocol-level sessions, including the initialize/initialized handshake and the Mcp-Session-Id header,... og:url: https://daily.dev/posts/stateless-mcp-removes-session-affinity-requirements-for-aws-server-deployments-iygc8pbe0 og:image: https://api.daily.dev/og/posts/iYGc8PbE0.png og:image:alt: Stateless MCP Removes Session Affinity Requirements for AWS Server Deployments og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Stateless MCP Removes Session Affinity Requirements for AWS Server Deployments **[InfoQ](https://daily.dev/sources/infoq)** · 2 min read · 1 upvotes · 0 comments ## Summary The latest Model Context Protocol specification removes protocol-level sessions, including the initialize/initialized handshake and the Mcp-Session-Id header, so requests can be routed to any server instance behind a standard load balancer without sticky-session infrastructure or shared session stores. AWS architecture blog authors describe how this simplifies horizontal scaling and makes AWS Lambda a viable deployment target for MCP servers since persistent session connections are no longer required. New mechanisms like MRTR replace server-initiated requests, new Mcp-Method and Mcp-Name headers enable gateway routing, and W3C Trace Context supports distributed tracing. Stream resumability is removed, raising the importance of idempotent tool calls for retries. Application-level state, retries, and observability now fall to surrounding infrastructure rather than the protocol itself. Projects like Apify's MCP server are implementing stateless support alongside existing sessionful servers to support migration, and AWS recommends tracking protocol versions at the gateway during the transition. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What changed in the latest MCP specification regarding sessions? The specification removes protocol-level sessions entirely, eliminating the initialize and initialized handshake and the Mcp-Session-Id header. Requests can now be routed independently to any server instance behind a conventional load balancer, removing the need for sticky-session routing or shared session storage that earlier MCP deployments required. _Track protocol-level changes like this stateless MCP shift on daily.dev before they force an infrastructure rework._ ### Can I deploy an MCP server on AWS Lambda now that the protocol is stateless? Yes, AWS Lambda becomes a fitting deployment option because stateless MCP no longer requires persistent session connections, matching Lambda's request-response execution model. AWS architecture guidance describes this alongside replacing session-affine routing with conventional request routing and removing session storage used solely for MCP protocol state. _Compare serverless deployment tradeoffs for protocols like MCP by following architecture updates on daily.dev._ ### Do I still need to support sessionful MCP servers during migration? Yes, migration support is still necessary for legacy clients. AWS recommends tracking protocol versions at the gateway and retaining session infrastructure until legacy traffic is eliminated. Apify's MCP server project, for example, is implementing stateless support alongside its existing sessionful server, running routing and conformance tests across both protocol versions during the transition. _Plan protocol migrations with confidence by keeping up with MCP version changes on daily.dev._ ## Similar posts on daily.dev - [MCP is now stateless: what the 2026-07-28 update changes](https://daily.dev/posts/mcp-is-now-stateless-what-the-2026-07-28-update-changes-hc2vhg5ll) · Flavio Copes · 9 upvotes · 0 comments - [MCP Is Going Stateless. Here’s How This Changes Things](https://daily.dev/posts/mcp-is-going-stateless-here-s-how-this-changes-things-7fjmnzm12) · Medium · 0 upvotes · 0 comments --- Tags: [#aws](https://daily.dev/tags/aws), [#observability](https://daily.dev/tags/observability), [#mcp](https://daily.dev/tags/mcp), [#distributed-systems](https://daily.dev/tags/distributed-systems), [#aws-lambda](https://daily.dev/tags/aws-lambda) [View this post on daily.dev](https://daily.dev/posts/stateless-mcp-removes-session-affinity-requirements-for-aws-server-deployments-iygc8pbe0) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Stateless MCP Removes Session Affinity Requirements for AWS Server Deployments","url":"https://daily.dev/posts/stateless-mcp-removes-session-affinity-requirements-for-aws-server-deployments-iygc8pbe0","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/stateless-mcp-removes-session-affinity-requirements-for-aws-server-deployments-iygc8pbe0"},"datePublished":"2026-09-25T13:03:13.935Z","dateModified":"2026-09-25T13:03:36.521Z","description":"The latest Model Context Protocol specification removes protocol-level sessions, including the initialize/initialized handshake and the Mcp-Session-Id header,...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/ec1d47a143ed8e2d70c5b70ea13827a7?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/ec1d47a143ed8e2d70c5b70ea13827a7?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"InfoQ","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"InfoQ","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/afc3bced3e1e4b188dd9127017a60e0c","url":"https://daily.dev/sources/infoq"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/stateless-mcp-removes-session-affinity-requirements-for-aws-server-deployments-iygc8pbe0","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"aws,observability,mcp,distributed-systems,aws-lambda","timeRequired":"PT2M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"InfoQ","item":"https://daily.dev/sources/infoq"},{"@type":"ListItem","position":3,"name":"Stateless MCP Removes Session Affinity Requirements for AWS Server Deployments"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/stateless-mcp-removes-session-affinity-requirements-for-aws-server-deployments-iygc8pbe0#faq","mainEntity":[{"@type":"Question","name":"What changed in the latest MCP specification regarding sessions?","acceptedAnswer":{"@type":"Answer","text":"The specification removes protocol-level sessions entirely, eliminating the initialize and initialized handshake and the Mcp-Session-Id header. Requests can now be routed independently to any server instance behind a conventional load balancer, removing the need for sticky-session routing or shared session storage that earlier MCP deployments required. Track protocol-level changes like this stateless MCP shift on daily.dev before they force an infrastructure rework."}},{"@type":"Question","name":"Can I deploy an MCP server on AWS Lambda now that the protocol is stateless?","acceptedAnswer":{"@type":"Answer","text":"Yes, AWS Lambda becomes a fitting deployment option because stateless MCP no longer requires persistent session connections, matching Lambda's request-response execution model. AWS architecture guidance describes this alongside replacing session-affine routing with conventional request routing and removing session storage used solely for MCP protocol state. Compare serverless deployment tradeoffs for protocols like MCP by following architecture updates on daily.dev."}},{"@type":"Question","name":"Do I still need to support sessionful MCP servers during migration?","acceptedAnswer":{"@type":"Answer","text":"Yes, migration support is still necessary for legacy clients. AWS recommends tracking protocol versions at the gateway and retaining session infrastructure until legacy traffic is eliminated. Apify's MCP server project, for example, is implementing stateless support alongside its existing sessionful server, running routing and conformance tests across both protocol versions during the transition. Plan protocol migrations with confidence by keeping up with MCP version changes on daily.dev."}}]} ```