GitHub MCP Server supports the next MCP specification
Quick Answer
GitHub MCP Server has adopted the upcoming stateless MCP protocol, enhancing scalability and performance by removing sessions and enabling parallel handshakes.
Quick Take
This update supports innovative extensions and maintains backward compatibility with tier 1 SDKs, ensuring seamless integration for developers ahead of the official release in 2026.
Key Points
- protocol transitions to stateless architecture by July 28, 2026.
- Sessions and initialization removed for faster server connections.
- New extensions like MCP apps and Enterprise Managed Auth are supported.
- Backward compatibility preserved across all tier 1 SDKs.
- Official conformance tests introduced to enhance verification for developers.
📖 Reader Mode
~2 min readThe MCP protocol is going stateless on 28th July 2026, and the GitHub MCP Server supports the latest spec ahead of the official release.
What’s changing
- The new stateless core means MCP deployments are now easy to scale.
- Extensions unlock innovation (e.g., MCP apps and Enterprise Managed Auth, both of which are already supported by VS Code).
- Sessions and
initializeare both removed, so you can connect to servers faster and easier. Clients can also complete the handshake in parallel. - You’ll see more remote servers supporting features like elicitation thanks to multi round-trip requests.
Since all tier 1 SDKs have preserved backwards compatibility and they have all already shipped beta support, you don’t need to do anything to maintain support. The GitHub MCP server uses the official Go SDK.
For GitHub MCP Server, we made three changes:
- Removed Redis sessions: Database writes on
initializeare gone, and database reads are gone from every call, which makes things snappier without users losing anything. -
Avoided deep packet inspection: We need to read some values from MCP requests for logging and secret scanning. In the new spec we can do that from HTTP headers guaranteed to be present. That means no more inspecting the payload of every single request before the SDK does.
-
Upgraded our elicitation implementation: Our stdio MCP server uses URL elicitation for easy user login. In the new protocol version, each step is a separate HTTP request. To make this work with old and new clients, the Go SDK provides a wrapper that makes both mechanisms work.
In addition, MCP added official conformance tests. Strict validation helps agents to verify their work. To use this, point Copilot at your codebase and provide access to:
This is a huge boost to all tiers of the official SDK, and to bespoke clients and servers too, because AI assisted development is much easier to verify with these tests.
GitHub support
GitHub MCP Server already supports the latest spec ahead of the official release.
Additional info
To learn more, see the blog post about this release.
— Originally published at github.blog
Want this in your inbox every morning?
Daily brief at your local 8am — bilingual EN/中文, free.
More from GitHub Copilot Changelog
See more →GitHub Copilot for JetBrains adds improved OpenTelemetry configuration and model management
The latest GitHub Copilot for JetBrains update enhances workflow control with OpenTelemetry configuration, improved model management, and support for servers in Claude agent flows, facilitating better observability and cost control for enterprise users.
