Knowledge File / AI小生意项目库
GitHub MCP服务器支持下一代MCP规范
MCP协议将于2026年7月28日变为无状态,GitHub MCP Server提前支持最新规范,带来更易扩展、更快连接等改进。
SOURCE / AI小生意项目库
MIN / 9
ACCESS / 会员
POST / 2026-07-24 04:38:22
原贴
查看原文原文
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: 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. 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. 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. 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.
中文翻译
MCP协议将于2026年7月28日变为无状态,GitHub MCP Server在正式发布前支持最新规范。新的无状态核心意味着MCP部署现在易于扩展。扩展解锁创新(例如,MCP应用和企业管理认证,Visual Studio Code均已支持)。会话和初始化都被移除,因此你可以更快更轻松地连接服务器。客户端也可以并行完成握手。由于多轮请求,你将看到更多远程服务器支持像elicitation这样的功能。由于所有一级SDK都保持了向后兼容性,并且都已发布了beta支持,你无需做任何操作来保持支持。GitHub MCP服务器使用官方Go SDK。对于GitHub MCP Server,我们做了三项更改:移除了Redis会话:初始化时的数据库写入已消失,每次调用中的数据库读取也已消失,这使得响应更迅速而用户不会损失任何东西。避免了深度包检测:我们需要从MCP请求中读取一些值用于日志记录和秘密扫描。在新规范中,我们可以从保证存在的HTTP头中读取这些值。这意味着不再需要每次在SDK处理前检查每个请求的有效负载。避免了深度包检测:我们需要从MCP请求中读取一些值用于日志记录和秘密扫描。在新规范中,我们可以从保证存在的HTTP头中读取这些值。这意味着不再需要每次在SDK处理前检查每个请求的有效负载。升级了我们的elicitation实现:我们的stdio MCP服务器使用URL elicitation实现用户轻松登录。在新的协议版本中,每一步都是一个单独的HTTP请求。为了使其与新旧客户端兼容,Go SDK提供了一个包装器,使两种机制都有效。升级了我们的elicitation实现:我们的stdio MCP服务器使用URL elicitation实现用户轻松登录。在新的协议版本中,每一步都是一个单独的HTTP请求。为了使其与新旧客户端兼容,Go SDK提供了一个包装器,使两种机制都有效。
核心信息
MCP协议将于2026年7月28日变为无状态,GitHub MCP Server提前支持最新规范,带来更易扩展、更快连接等改进。
- MCP协议将于2026年7月28日变为无状态,GitHub MCP Server提前支持最新规范,带来更易扩展、更快连接等改进。
- 原贴提到:The MCP protocol is going stateless on 28th July 2026, and the GitHub MC
- 来源:github.blog
试看内容
成为会员查看完整内容
你已经看到了这篇内容的前置整理,剩余深度部分仅对会员开放。
详细解读
信息差价值
参考来源
成为会员查看完整内容