GitHub MCP Server 支持下一版 MCP 规范

MCP 协议将于 2026 年 7 月 28 日转向无状态架构，GitHub MCP Server 已在官方正式发布前支持最新规范。

• 新的无状态核心意味着 MCP 部署如今更易于扩展。
• 扩展机制释放了创新空间（例如 MCP 应用和 Enterprise Managed Auth；VS Code 已支持这两项功能）。
• session 和 initialize 均被移除，因此连接服务器更快速、更简单。客户端也可以并行完成握手。
• 得益于多轮往返请求，你将看到更多远程服务器支持 elicitation 等功能。

由于所有一级 SDK 均保留了向后兼容性，并且都已发布 Beta 支持，因此你无需进行任何操作即可维持支持。GitHub MCP Server 使用官方 Go SDK。

对于 GitHub MCP Server，我们进行了三项改动：

1. 移除 Redis 会话：不再在 initialize 时写入数据库，并且每次调用也不再读取数据库；在用户没有任何损失的前提下，这使整体响应更加迅速。

2. 避免深度包检测：我们需要从 MCP 请求中读取一些值，用于日志记录和密钥扫描。在新规范中，我们可以从保证存在的 HTTP 标头中获取这些值。这意味着 SDK 处理请求之前，不再需要检查每一条请求的载荷。

3. 升级 elicitation 实现：我们的 stdio MCP Server 使用 URL elicitation，以便用户轻松登录。在新版协议中，每个步骤都是独立的 HTTP 请求。为同时兼容新旧客户端，Go SDK 提供了一个包装器，使两种机制都能正常工作。

此外，MCP 新增了官方一致性测试。严格验证可帮助 Agent 验证其工作成果。要使用此功能，请让 Copilot 指向你的代码库，并为其提供以下访问权限：

这对所有层级的官方 SDK，以及定制客户端和服务器而言都是一次重大提升，因为借助这些测试，AI 辅助开发的验证将变得容易得多。

GitHub MCP Server 已支持最新规范，早于官方正式发布。

如需了解更多信息，请参阅有关此次发布的博客文章。

The MCP protocol is going stateless on 28th July 2026, and the GitHub MCP Server supports the latest spec ahead of the official release.

• 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 initialize are 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:

1. Removed Redis sessions : Database writes on initialize are gone, and database reads are gone from every call, which makes things snappier without users losing anything.

2. 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.

3. 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 MCP Server already supports the latest spec ahead of the official release.

To learn more, see the blog post about this release.