What's this about?
The Model Context Protocol (MCP) shipped its 2026-07-28 release, its biggest yet. The core change: it moves from a *stateful*, two-way protocol (client connects, server issues a session ID, they keep a live connection) to a *stateless* request/response model. This was the community's most-requested change.
What exactly is MCP?
MCP is a standard way for AI apps to plug into tools and data — think "USB-C for AI agents." Before, connecting meant a handshake and a persistent session the server had to track. Stateless means each request stands alone, like a normal web API call: far easier to scale, load-balance, and run serverless, at the cost of the server no longer remembering you between calls.
What's the community saying?
683 + 454 likes on X
- Relief — stateful sessions were the top pain point for anyone deploying MCP servers at scale.
- Some worry about migration churn for existing stateful integrations.
- dotey's plain-language thread explaining the change was widely shared in the Chinese dev community.