MCP 2026-07-28 Specification: transport going stateless
The Model Context Protocol (MCP) has released a new specification that shifts the protocol from a stateful to a stateless request/response model. This update aims to improve reliability and scalability for developers building agentic workflows by removing the need for shared storage.
Why it matters
As AI agents become more prevalent, standardizing how they interact with data and tools is critical for the development of the AI ecosystem.
Since our last November release MCP continued to grow at an astonishing rate. Across our Tier 1 SDKs, we're seeing close to half-a-billion downloads a month, with both TypeScript and Python SDKs crossing the 1 billion total downloads threshold. In just a few months, the protocol continued to grow as the data and interactivity substrate for agentic workflows.
Today, we're officially pushing the release button on the next version of the MCP specification, 2026-07-28 , along with the SDKs that will allow you to start building clients and servers right away.
The highlight of this release is a stateless protocol core - MCP is transforming from a bidirectional stateful protocol into a request/response stateless protocol. It was one of the most highly-requested features from developers who were eager to get better reliability and scalability for their MCP servers.
There is, of course, more to what we're introducing with this version:
Get smarter about the news
Sign up free for a feed built around what you actually care about, Dive Deeper research on any story, and the full text of every article.
Create free accountAlready have an account? Sign in