Protocol updates are the least glamorous thing in this industry and among the most consequential. MCP is how an AI tool reaches your repositories, your database, your issue tracker. On 28 July the specification behind it changes shape, and GitHub shipped support for the new version five days early.
What actually changes
The headline is that MCP becomes stateless. In GitHub’s words, "the new stateless core means MCP deployments are now easy to scale". Three changes carry most of that:
- Sessions and the initialize procedure are gone, so connections establish faster
- Clients and servers complete the handshake in parallel rather than in sequence
- Requests can span multiple round trips, which is what makes richer elicitation possible
Elicitation is the part users will notice
Most of the above is invisible. Elicitation is not. It is the mechanism by which a server can stop mid-task and ask the client for something — a missing parameter, a confirmation, a choice between options — instead of failing or guessing.
Anyone who has watched an agent barrel ahead on an ambiguous instruction and produce confidently wrong output understands why this matters. Multi-round-trip requests are the plumbing that lets a tool say "which of these three databases did you mean?" halfway through, and that is a meaningful reduction in a specific failure mode.
What GitHub had to change to support it
The engineering notes are unusually candid about the cost of statefulness. To move the GitHub MCP Server across, the team removed Redis sessions so that initialisation no longer performs a database operation, stopped doing deep packet inspection in favour of reading the values it needs from HTTP headers, and upgraded the stdio server so it speaks both the old and new client protocols through the Go SDK wrapper.
That last point is the reassuring one. All tier 1 SDKs preserved backwards compatibility, so existing implementations require no changes. MCP has also introduced official conformance tests, which gives anyone building a server a way to check their work rather than discovering incompatibility in production.
Why this belongs in a tools newsletter at all
Because connectors are quietly becoming the thing you are actually buying. Claude, Copilot and Cursor all reach outside themselves through MCP; n8n occupies adjacent territory by wiring systems together directly. When the protocol underneath gets faster to connect and better at asking clarifying questions, every tool sitting on top inherits that without shipping anything.
The practical advice for this week is narrow. If you maintain an MCP server, run the new conformance tests before 28 July. If you only consume MCP through a product, there is nothing to do — backwards compatibility means the change should reach you as things simply working slightly better, which is the correct way for a protocol update to arrive.