MCP Protocol Redesigned as Stateless to Unlock Enterprise Adoption

The 2026-07-28 MCP specification release candidate, authored by Anthropic engineers David Soria Parra and Den Delimarsky, redesigns the protocol's transport layer to be stateless — removing the per-session, per-server-instance dependency that had made horizontal scaling difficult [1]. Ars Technica describes it as the largest change to MCP since its introduction [1]; VentureBeat calls it the biggest update the protocol has received [4]. Concurrently, both Claude and ChatGPT now support custom MCP server connections [11][12], and a commercial MCP ecosystem is taking shape, with Manufact (YC S25) launching an MCP Cloud product [9].

MCP's stateful session model was a concrete obstacle to enterprise deployment: servers had to maintain per-client state, making standard cloud load-balancing and horizontal scaling incompatible with the protocol. A stateless core removes that constraint, bringing MCP in line with ordinary cloud infrastructure patterns. Whether the spec change is sufficient to drive actual enterprise adoption remains open — analysts identify other barriers the spec alone does not address [16].

The 2026-07-28 MCP specification release candidate introduces a stateless protocol core, the most significant technical change to the Model Context Protocol since Anthropic introduced it [1]. The spec was authored by Anthropic's David Soria Parra and Den Delimarsky, who serve as lead MCP maintainers. Under the prior design, MCP sessions were bound to individual server instances, which meant standard cloud load-balancing — routing requests across a pool of servers — was incompatible with the protocol. The new spec removes that constraint: requests no longer carry session affinity, so any server instance can handle any request [1][2][3]. Ars Technica and VentureBeat both frame this as the largest update the protocol has received [1][4]; InfoWorld focuses on the scaling implications [3].

The stateless redesign fits within a broader 2026 roadmap for MCP emphasizing enterprise readiness [5][6]. Analysis from obot.ai situates the stateless core alongside new SDK updates and enterprise-oriented extensions as part of a coordinated maturation effort [6]. TheNewStack describes the prior stateful model as the main barrier to enterprise adoption and frames the new spec as its resolution [7]. WorkOS has published enterprise team guidance on MCP [8], and a commercial layer is forming: Manufact (YC S25) launched an MCP Cloud product [9], and Gainsight has documented an MCP server integration for its customer success platform [10].

Multi-platform support has arrived in parallel. Both Claude and ChatGPT now accept custom MCP server connections [11][12][13]. Simon Willison documented the process as feasible but involving 'quite a few steps' [11], and Docker has published guidance on adding MCP servers to ChatGPT [13]. Community developers are actively experimenting with cross-platform MCP setups connecting Claude, ChatGPT, Gemini, and Perplexity [14]. Hacker News and Reddit discussions around the July 28 spec show engaged developer attention [2][15].

Not all observers read the stateless spec as a complete solution. A Medium analysis identifies six critical challenges still facing MCP in 2026, arguing the spec is a meaningful step without being a full answer to enterprise adoption barriers [16]. Developer friction in setup and the divergence between Claude and ChatGPT implementations are open practical questions. The specification is currently a release candidate, so final ratification and client-side implementation timelines are not yet confirmed.