GitHub MCP Server Moves to a Stateless Protocol Core
The server drops initialization sessions and Redis traffic while adding a lighter request path, revised elicitation and conformance testing.
GitHub said on July 23 that its MCP Server already supported the protocol specification scheduled for release on July 28. The update moves the server to a stateless core, removes session initialization and changes how requests, login elicitation and compatibility are handled. For teams operating remote agent-tool servers, the practical result is less server-side session machinery and a clearer test path for protocol compliance.
What changed
The new protocol core removes sessions and the `initialize` step. GitHub says its own server no longer writes session data to Redis during initialization or reads it on every subsequent call. Removing those database operations reduces the amount of state that a deployment must coordinate when traffic is spread across server instances.
GitHub also changed how it gathers values needed for logging and secret scanning. Under the new specification, those values can be read from required HTTP headers, so the server no longer needs to inspect each full request payload before handing it to the software development kit. This is an implementation change, not a promise that security controls have been removed; GitHub still describes logging and secret scanning as reasons for reading the request metadata.
Elicitation changed as well. GitHub's standard-input server uses URL elicitation for login, while the new protocol expresses each step as a separate HTTP request. The official Go software development kit provides a compatibility wrapper so the older and newer mechanisms can both work. GitHub also points developers to official conformance tests, draft documentation and tier-one SDK implementations for validating compatible clients and servers.
Why it matters
MCP is infrastructure between agents and external tools, so transport and lifecycle details affect scale, latency and reliability even when users never see them. A stateless request model can make horizontal scaling simpler because a later call does not have to return to the same session store. Removing initialization and some database traffic may also shorten the connection path, although GitHub did not publish independent latency measurements in the announcement.
Compatibility remains the important caveat. GitHub says tier-one SDKs preserved backward compatibility and had beta support, but bespoke clients and servers still need testing. The existence of conformance tests is useful because it turns protocol support from a vendor assertion into something implementers can check against their own code.
Status
Confirmed. GitHub documented the server changes in its official changelog and identified its own MCP Server as already supporting the specification. Internal confidence is high because GitHub is the primary authority for this server implementation; wider ecosystem compatibility depends on each client and server.
Sources
Update note: Last reviewed 2026-07-29. We will revise this post if GitHub changes compatibility guidance, server behavior or the referenced conformance path.
Sources
Drafted with AI assistance from source briefs; reviewed for citation completeness and label accuracy.