MCP throws the session model in the trash: now any request can land on any server, which makes connecting your tools to agents actually scale. The RC was frozen on May 21, 2026 and the final version arrives on July 28.
Remember the cable chaos before USB-C, when every gadget had its own charger and you were always missing the exact one you needed? The world of AI agents was living that exact nightmare: every tool connected its own way and nothing talked to anything. The Model Context Protocol (MCP) was born to be that universal USB-C for agents, and it has stopped being "a single-lab thing" to become a standard half the industry is adopting. It just shipped the release candidate of its next version, and pay attention, because this isn't one of those minor patches that slip by without a trace: it's the biggest redesign since it was born. If you build with agents, this is the infrastructure story of the quarter, even if it doesn't make the flashy headlines.
Goodbye sessions, hello real scaling
The headline change has a technical name but very practical consequences: a stateless core. No more "initialize" handshakes and those sticky session headers that forced every request to always land back on the same server. Now any MCP request can hit any instance with no special routing, like dealing cards without caring who picks them up. In plain English: standing up an MCP server that can take real traffic no longer requires infrastructure black magic and instead runs on plain, ordinary HTTP. If you've ever wrestled with a server that fell over as it scaled, you know exactly the headache this removes.
Extensions, MCP Apps, and grown-up auth
And it doesn't stop there, because the redesign comes loaded. There's a new extensions framework where capabilities like long-running jobs and MCP Apps (servers that serve HTML interfaces the host renders inside a sandboxed iframe) get versioned separately from the core, without breaking anything. It adds a formal deprecation policy, that boring but vital thing that keeps an update from taking your app down overnight. And several authorization improvements aligned with OAuth 2.0 and OpenID Connect, meaning real security, not toy security. The RC was frozen on May 21 and the final version lands on 2026-07-28, so this isn't science fiction: it's right around the corner.
So what does this have to do with NeuralOS?
A lot, and we're not going to pretend otherwise. We live precisely off connecting tools to agents, so an MCP that's simpler to scale and comes with native UI apps is a direct tailwind for what we're building. That said, let's be honest with you: it's not like we already have it all wired up and running beautifully, it would be a lie to tell you that. But it's exactly the direction we push toward with every sprint. Our obsession is that connecting your stack to an agent should feel like plugging in a cable, not like standing up a server at three in the morning. Seeing the industry standard move right toward that confirms we're on the right track.