MCP Gets Its Biggest Spec Change Since Launch, Moving to a Stateless Core
The Model Context Protocol team published the 2026-07-28 specification on July 28, 2026, the biggest revision to the protocol since launch. The central change replaces the stateful bidirectional core with a stateless request and response model, letting MCP servers run on serverless infrastructure, but bringing breaking changes for older clients.
The Biggest Spec Change Since MCP Launched
The Model Context Protocol team published the 2026-07-28 specification on July 28, 2026, described by the official MCP blog and by TechTimes as the biggest revision to the protocol since its launch in November 2024. MCP is the open standard created by Anthropic to connect AI models to tools, files and external services, now adopted as a reference standard across nearly the entire AI agent industry.
From a Stateful Protocol to a Stateless Core
The central change, according to the Claude blog and The Register, is the move from a bidirectional stateful protocol to a stateless request and response model. The revision removes the initialize handshake and the protocol level session: every request is now self contained, no longer dependent on a persistent connection between client and server.
What This Unlocks in Practice
With a stateless core, MCP servers can now run on serverless and edge infrastructure, something that was practically unfeasible under the previous model, which required persistent connections. The specification also adds multi round trip requests, header based routing, cacheable list results, hardened authorization with stricter OAuth and OIDC, and a formal framework for versioned extensions, including specific extensions for Apps and Tasks, according to 4sysops.
Breaking Changes Ahead
The official documentation itself warns that this release contains breaking changes. Servers adopting the 2026-07-28 revision may not work with older clients, and vice versa, unless both sides share the same protocol era or implement a deliberate fallback or translation mechanism between versions. Beta SDKs for Python, TypeScript, Go and C sharp have already been published for the new revision.
A Protocol Already Past 400 Million Monthly Downloads
The context helps explain the weight of the announcement: MCP has already surpassed 400 million monthly SDK downloads, up fourfold this year, cementing itself as the de facto standard for connecting AI agents to applications. Support for the new specification is being rolled out gradually across Claude's products.
Why It Matters for Brazilian Agencies and SMBs
For Brazilian agencies already building customer service and marketing automation agents on top of MCP servers, the 2026-07-28 revision is both an opportunity and a warning. The stateless architecture lowers infrastructure costs for anyone hosting AI tools on serverless environments, which favors smaller teams without a dedicated DevOps function. On the other hand, the explicit breaking change warning means MCP integrations built on the previous specification could stop working with updated clients without notice if nobody plans the migration. It is worth testing MCP servers and clients in production before AI providers, including Claude itself, make the new revision the default.