Stacks and Flows

Implementation Guide · Source-verified

GitHub MCP Server's stateless transition: what operators should check

GitHub updated its MCP Server toward the latest specification and a stateless transport model. Operators should check client versions, authentication, session assumptions, and rollback—not infer interoperability from the MCP label.

Implementation facts

  • GitHub announced support for the latest MCP specification in July 2026.
  • GitHub maintains the server in a public repository.
  • Server support for a specification does not prove that every client supports the same transport behavior.

Pre-change check

Record the client version, transport, authentication path, and any state currently assumed between calls.

Compatibility check

Test initialization, a read-only tool call, reconnect, and an authorization failure. Passing one tool call is not a compatibility matrix.

Rollout rule

Ship to a bounded environment first, retain logs, and roll back the server-client pair together if transport assumptions diverge.

Decision detail

  1. Pin client and server versions in production integration tests.
  2. Test authentication and reconnect behavior without relying on a retained server session.
  3. Keep a rollback path until the named client-server pair passes representative tool calls.
  4. Record the transport assumptions that the rollout removes.

Evidence

These claims are source-verified. We do not label this page hands-on or benchmarked because no reproducible test artifact is attached.

Continue the decision