← All news

GitHub MCP Server adopts next MCP spec: protocol goes stateless

GitHubSummarized by the ORA·tech AI assistant
GitHub MCP Server adopts next MCP spec: protocol goes stateless

GitHub says its MCP Server already supports the new MCP spec ahead of the official July 28, 2026 release, as the protocol goes stateless. Dropping sessions and the initialize step means faster connects and parallel handshakes; GitHub removed Redis sessions, avoided deep packet inspection, and upgraded elicitation.

GitHub announced its MCP Server already supports the new Model Context Protocol (MCP) spec ahead of the official July 28, 2026 release, when the protocol moves to a stateless model aimed at making MCP deployments easier to scale.

Key points

  • Stateless core: sessions and the initialize step are removed, so clients connect faster and can complete the handshake in parallel; deployments scale more easily.
  • Three GitHub-side changes: removed Redis sessions (no DB writes on initialize, no DB reads per call); avoided deep packet inspection by reading needed values from guaranteed HTTP headers instead of every request payload; upgraded URL elicitation with a Go SDK wrapper so old and new clients both work.
  • Compatibility: tier 1 SDKs preserved backward compatibility and shipped beta support, so users need to do nothing. The GitHub MCP Server uses the official Go SDK.
  • Conformance tests: MCP added official conformance tests to help verify clients/servers and make AI-assisted development easier to validate.

Details and links to the conformance suite and draft spec are in GitHub's changelog - see Read original.

#MCP#GitHub#AI agents#Go SDK#protocol
This summary was written by the ORA·tech AI assistant. Read the original for full context.

Related