--- title: Exploring the Future of MCP Transports | daily.dev description: The Model Context Protocol Transport Working Group outlines a roadmap to evolve the Streamable HTTP transport toward a stateless architecture, addressing... canonical: https://daily.dev/posts/exploring-the-future-of-mcp-transports-plpwi9inp twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Exploring the Future of MCP Transports | daily.dev og:description: The Model Context Protocol Transport Working Group outlines a roadmap to evolve the Streamable HTTP transport toward a stateless architecture, addressing... og:url: https://daily.dev/posts/exploring-the-future-of-mcp-transports-plpwi9inp og:image: https://api.daily.dev/og/posts/PlpWI9inP.png og:image:alt: Exploring the Future of MCP Transports 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. # Exploring the Future of MCP Transports **[Model Context Protocol](https://daily.dev/sources/modelcontextprotocol-blog)** · 7 min read · 0 upvotes · 0 comments ## Summary The Model Context Protocol Transport Working Group outlines a roadmap to evolve the Streamable HTTP transport toward a stateless architecture, addressing enterprise scaling issues like sticky sessions, infrastructure complexity, and ambiguous session scope. Proposed changes include replacing the initialize handshake with per-request capability exchange, moving sessions to the data model layer via a cookie-like mechanism, redesigning elicitations and sampling for stateless reconstruction, replacing generic notification streams with explicit subscriptions plus TTLs and ETags, exposing routing info via HTTP paths/headers instead of JSON-RPC parsing, and introducing Server Cards via a /.well-known/mcp.json endpoint for pre-connection discovery. STDIO and Streamable HTTP remain the only official transports, with Custom Transports still supported for specialized needs. SEPs are targeted for finalization in Q1 2026, aiming for inclusion in the next spec release tentatively planned for June 2026. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Why is the Model Context Protocol moving away from stateful Streamable HTTP sessions? Stateful connections in Streamable HTTP force sticky routing that pins traffic to specific servers, which blocks effective auto-scaling and forces developers building simple tools to manage complex backend storage. The Transport Working Group is exploring making the protocol stateless, replacing the initialize handshake with per-request capability exchange and moving sessions into the application data model layer using a cookie-like mechanism. _daily.dev helps engineers track evolving specs like MCP transports before they hit production._ ### Will MCP support official transports beyond STDIO and Streamable HTTP? No, MCP will continue to officially support only STDIO for local deployments and Streamable HTTP for remote deployments, to keep the ecosystem interoperable out of the box. Teams with specialized requirements can still build Custom Transports, and the working group plans to improve SDK integration to make those easier to implement without fragmenting the standard. _Following protocol decisions like this on daily.dev helps teams choose the right integration approach._ ### When will the proposed MCP stateless transport changes be finalized? The required Spec Enhancement Proposals are targeted for finalization in the first quarter of 2026, for inclusion in the next MCP specification release, which is tentatively slated for June of 2026. Most SDK users on both client and server sides are expected to see minimal impact, since breaking changes are being kept to an absolute minimum. _daily.dev keeps developers ahead of upcoming spec releases affecting their MCP integrations._ ## Similar posts on daily.dev - [The New MCP Roadmap](https://daily.dev/posts/the-new-mcp-roadmap-1oklafl87) · Model Context Protocol · 19 upvotes · 3 comments - [Why MCP’s Move Away from Server Sent Events Simplifies Security](https://daily.dev/posts/why-mcp-s-move-away-from-server-sent-events-simplifies-security-vskv28occ) · Auth0 · 1 upvotes · 0 comments - [Stateless MCP Removes Session Affinity Requirements for AWS Server Deployments](https://daily.dev/posts/stateless-mcp-removes-session-affinity-requirements-for-aws-server-deployments-iygc8pbe0) · InfoQ · 1 upvotes · 0 comments - [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 --- Tags: [#architecture](https://daily.dev/tags/architecture), [#ai-agents](https://daily.dev/tags/ai-agents), [#mcp](https://daily.dev/tags/mcp), [#distributed-systems](https://daily.dev/tags/distributed-systems) [View this post on daily.dev](https://daily.dev/posts/exploring-the-future-of-mcp-transports-plpwi9inp) ```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":"Exploring the Future of MCP Transports","url":"https://daily.dev/posts/exploring-the-future-of-mcp-transports-plpwi9inp","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/exploring-the-future-of-mcp-transports-plpwi9inp"},"datePublished":"2026-08-23T12:16:54.279Z","dateModified":"2026-08-23T12:18:20.039Z","description":"The Model Context Protocol Transport Working Group outlines a roadmap to evolve the Streamable HTTP transport toward a stateless architecture, addressing...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/ccad778d24e1fca3aa1c66575a7bfbf3?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/ccad778d24e1fca3aa1c66575a7bfbf3?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Model Context Protocol","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":"Model Context Protocol","logo":"https://media.daily.dev/image/upload/s--ORAgfri4--/f_auto,q_auto/v1787487408/logos/modelcontextprotocol-blog?_a=BAMAMicg0","url":"https://daily.dev/sources/modelcontextprotocol-blog"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/exploring-the-future-of-mcp-transports-plpwi9inp","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"architecture,ai-agents,mcp,distributed-systems","timeRequired":"PT7M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Model Context Protocol","item":"https://daily.dev/sources/modelcontextprotocol-blog"},{"@type":"ListItem","position":3,"name":"Exploring the Future of MCP Transports"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/exploring-the-future-of-mcp-transports-plpwi9inp#faq","mainEntity":[{"@type":"Question","name":"Why is the Model Context Protocol moving away from stateful Streamable HTTP sessions?","acceptedAnswer":{"@type":"Answer","text":"Stateful connections in Streamable HTTP force sticky routing that pins traffic to specific servers, which blocks effective auto-scaling and forces developers building simple tools to manage complex backend storage. The Transport Working Group is exploring making the protocol stateless, replacing the initialize handshake with per-request capability exchange and moving sessions into the application data model layer using a cookie-like mechanism. daily.dev helps engineers track evolving specs like MCP transports before they hit production."}},{"@type":"Question","name":"Will MCP support official transports beyond STDIO and Streamable HTTP?","acceptedAnswer":{"@type":"Answer","text":"No, MCP will continue to officially support only STDIO for local deployments and Streamable HTTP for remote deployments, to keep the ecosystem interoperable out of the box. Teams with specialized requirements can still build Custom Transports, and the working group plans to improve SDK integration to make those easier to implement without fragmenting the standard. Following protocol decisions like this on daily.dev helps teams choose the right integration approach."}},{"@type":"Question","name":"When will the proposed MCP stateless transport changes be finalized?","acceptedAnswer":{"@type":"Answer","text":"The required Spec Enhancement Proposals are targeted for finalization in the first quarter of 2026, for inclusion in the next MCP specification release, which is tentatively slated for June of 2026. Most SDK users on both client and server sides are expected to see minimal impact, since breaking changes are being kept to an absolute minimum. daily.dev keeps developers ahead of upcoming spec releases affecting their MCP integrations."}}]} ```