Ok. MCP just shipped the biggest change since the day it launched, and the headline isn't a feature you get to switch on. It's the delete key.

The 2026-07-28 revision — people are calling it MCP 2.0, and it's the first release that breaks the base protocol on purpose — rips the session out. No more initialize handshake. No more notifications/initialized. No Mcp-Session-Id. No GET SSE endpoint, no resumable streams, no resources/subscribe, no roots/list at the top level, no ping, no logging/setLevel. Gone.

And here's the thing — that's the good news.

Ok, let's say you working in the company and your management or you the manager all day long talking about being AI native. First of all what does it mean to become an AI native company? Fire all developers and build AI agents to make all work? Maybe. Or something less radical, like add AI in all steps of product lifecycle? Might be.

Regardless how radical you want to be, probably you will miss the most important point, without it all your idea of becoming an AI native company will fail. Moreover you might damage your company badly.

Organizations are shipping code faster than ever. They're also forgetting faster than ever. AI agents write features in hours, but six months later, no one can explain why the system looks the way it does. The code works. The tests pass. But the story is gone.