GitHub MCP Server shipped 2026-07-28 support five days before the revision was released

GitHub announced on July 23 that the GitHub MCP Server already supported the stateless 2026-07-28 revision, five days ahead of the revision's official release: "The MCP protocol is going stateless on 28th July 2026, and the GitHub MCP Server supports the latest spec ahead of the official release."

The changelog describes three server-side changes. Request values needed for logging and secret scanning now come from HTTP headers guaranteed to be present, ending deep packet inspection of every request body. The stdio server's URL-based login flow was upgraded to multi round-trip requests, with the Go SDK providing a wrapper that serves both old and new clients. And the Redis-backed session store was removed outright: database writes on initialize are gone, and database reads are gone from every call. The entry also notes the new extensions model, naming MCP apps and Enterprise Managed Auth as extensions already supported by VS Code, and states that no user action is required because all Tier 1 SDKs preserved backwards compatibility.

Release metadata corroborates the timeline. Server v1.7.0, published July 23, carries the 2026-07-28 changes via go-sdk 1.7.0-pre.3; v1.8.0 on July 30 moved to the stable go-sdk v1.7.0. From the SDK side, the Go maintainers cite the deployment as validation at scale, stating the pre-release "is already successfully used by GitHub, serving more than half a million users" (their characterization, not GitHub's own number). GitHub states no deprecation timeline for the older protocol version.

The adoption tracker records this as a verified support record for the GitHub MCP Server against MCP 2026-07-28.