GitHub MCP Server supports the next MCP specification
The GitHub MCP Server now supports the latest MCP protocol specification, which transitions to a stateless core architecture ahead of the official July 28, 2026 release date.
The 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.
The post GitHub MCP Server supports the next MCP specification appeared first on The GitHub Blog.
Source: original entry ↗
More from GitHub
Follow GitHub to get its new changes in your feed and email digest.
Claude Haiku 5.5 now available in GitHub Copilot
Claude Haiku 5.5, Anthropic's lightweight model, is now generally available in GitHub Copilot for fast, high-volume tasks like subagents, quick edits, and terminal operations.
Purpose-built model for leaked secret detection
GitHub introduced a new purpose-built model for detecting leaked secrets that provides context-aware detection to keep pace with modern software development practices, including AI-assisted coding.
Local sandboxing for GitHub Copilot now generally available
GitHub Copilot's local sandboxing feature is now generally available across GitHub Copilot CLI, the GitHub Copilot app, and VS Code sessions using Agent Host, providing developers with a secure environment for testing and development.