MCP Ships Its Biggest Update Ever: Stateless Core, MCP Apps, and Async Tasks
The "USB port" of the AI agent ecosystem just got its biggest overhaul since launch — the MCP 2026-07-28 specification was finalized on July 28, shifting the core architecture from stateful to stateless and introducing two major extensions: MCP Apps and Tasks.
Three Key Takeaways
Stateless core is the biggest architectural change. The new spec redesigns the protocol core as stateless: servers no longer need to maintain long-lived connection sessions. This means MCP servers can now scale horizontally, load-balance, and recover from failures just like regular HTTP APIs, dramatically reducing enterprise deployment complexity. A response caching mechanism has been added to maintain performance despite the stateless design. The spec went through a ten-week release-candidate validation window starting May 21 before replacing the 2025-11-25 version as the current standard.
MCP Apps give tools a visual interface. The new MCP Apps extension lets servers render interactive HTML UIs (sandboxed iframes) directly in the client. The rendered UI communicates with the host over the same JSON-RPC protocol used for tool calls, meaning every UI-triggered action goes through the same audit and consent path as a direct tool call. In plain terms: tools went from "can only return text" to "can pop up a dashboard."
Tasks extension solves the async pain point. The redesigned Tasks extension provides first-class support for long-running asynchronous work. The spec also introduces an Extensions Framework where extensions get reverse-DNS identifiers, independent versioning, and dedicated maintainers, allowing them to evolve independently from the main spec. Clients and servers negotiate extension support through an extensions map in their capabilities.
WangDou's Take
Switching MCP from stateful to stateless sounds like a technical footnote, but it solves a very real problem: before this, every MCP server had to maintain WebSocket connections and session state. Deploy three instances and you are worrying about session affinity; lose one instance and users drop. That does not scale in the enterprise. Go stateless and an MCP server scales like a REST API — ops complexity drops by an order of magnitude. MCP Apps are even more interesting: agents used to call a tool and get back a blob of JSON. Now they can surface a full interactive UI, which effectively upgrades MCP from an "API protocol" to a "micro-app platform." Ten weeks of release-candidate validation before finalization, breaking changes clearly documented — that is a more disciplined release cadence than most commercial software manages.