GitHub MCP Server Ships Support for the Next MCP Spec Ahead of Its July 28 Ratification — Stateless Core, Redis Sessions Removed, Elicitation Over Plain HTTP

GitHub Changelog·high signal

GitHub's July 23 changelog announced that its MCP Server already supports the next MCP specification, which becomes official on July 28, 2026. The stateless core removes the Redis session dependency and the deep packet inspection of request payloads, lets clients connect without sessions or an initialize handshake, and upgrades elicitation to multi-round-trip HTTP requests wrapped by the SDKs; extensions cover MCP apps and Enterprise Managed Auth. All tier-1 SDKs keep backwards compatibility (GitHub uses the official Go SDK and required no changes), and conformance tests now exist to validate implementations — if you run an MCP server, the stateless model is the migration that actually changes your deployment topology.