By Bill Maxwell, Obot AI
The MCP spec dropping July 28 is the largest revision since MCP launched — and as a team that's been building enterprise infrastructure on top of MCP since the beginning, we've been watching this roadmap closely.
The headline change is a stateless core. The initialize/initialized handshake is gone. Protocol metadata now travels with every request instead of being negotiated once at connection time. For teams running Obot, this is a direct win: no more sticky sessions, no shared session store, no extra routing complexity at the gateway layer.
But the stateless core is just one part of a larger shift. The 2026 roadmap also formalizes an extensions system, hardens OAuth/OIDC to match how it's actually deployed in production, and establishes a proper twelve-month deprecation lifecycle. MCP is replacing early protocol-specific machinery with proven infrastructure patterns.
What's equally telling is what the roadmap leaves deliberately undefined: audit trails, SSO-integrated authorization, gateway behavior, and configuration portability are explicitly called out as enterprise-readiness concerns — and described as an open invitation for the ecosystem to fill. That's exactly the space Obot is built for, and this release makes the foundation beneath us significantly stronger.
Obot Software Architect Bill Maxwell breaks down every major change and what it means for teams running MCP in production today.
Originally published on Obot AI
Top comments (0)