Skip to content

chore(registry): 更新 github-mcp 至 2.0.3 - #20

Merged
yi-ge merged 2 commits into
mainfrom
updates/mcp-github-mcp-2.0.3
Nov 4, 2026
Merged

yi-ge merged 2 commits into
mainfrom
updates/mcp-github-mcp-2.0.3

Conversation

@github-actions

@github-actions github-actions Bot commented Nov 3, 2026 •

Copy link
Copy Markdown
Contributor

github-mcp: 0.32.0 → 2.0.3(listing-only 条目,人工复核后升级)

复核结果

  • 依据 GitHub 官方 Release(v0.33.0 至 v2.0.3)与 v2.0.3 README 复核;未拉取或运行容器镜像。
  • 许可证仍为 MIT。启动方式不变:docker run -i --rm -e GITHUB_PERSONAL_ACCESS_TOKEN ghcr.io/github/github-mcp-server。
  • 2.0 的破坏性变化只涉及 Go 模块路径(v2)和仅向 MCP 2026-07-28 客户端提供的结构化输出,容器用法不受影响。
  • README 中本地服务共 93 个工具;默认工具集(context / repos / issues / pull_requests / users)启用 45 个。原 toolCount: 51 无法从任何版本的 README 复现,按本地服务全部工具更新为 93,并在 usage.md 写明默认数量。

改动

  • 同步 manifest / sidecar 版本、工具数、发布时间与核对时间;镜像标签保持原有的不固定写法。
  • install.md / usage.md 原来写的是已弃用的 npx @modelcontextprotocol/server-github,与 manifest 的 Docker 方式不一致,改为 Docker 安装、验证、工具集与只读模式说明。
  • 删除候选说明文件。

验证

npm test(93 项)、目录 catalog 测试(20 项)、--require-sidecars 校验、Python 边界测试均通过。


Upgrade the listing-only github-mcp entry to 2.0.3 based on official releases and the v2.0.3 README (no container pulled or run). MIT license and the Docker launch contract are unchanged; 2.0 breaking changes affect Go library users and newer-spec structured outputs only. toolCount becomes 93 (all local tools; 45 in the default toolsets). The stale npx-based install/usage docs are rewritten to match the manifest's Docker setup. All registry checks pass.

yi-ge and others added 2 commits November 3, 2026 02:26
- 同步版本、发布时间与核对时间
- toolCount 按 2.0.3 README 中本地服务的全部工具更新为 93,说明默认工具集只启用 45 个
- install.md 与 usage.md 改为与 manifest 一致的 Docker 启动方式,替换已弃用的 npx 包说明
- 记录 2.0 的主要变化
- 移除已完成的候选说明文件
@yi-ge
yi-ge marked this pull request as ready for review November 4, 2026 03:52
@yi-ge
yi-ge merged commit 45c290e into main Nov 4, 2026
1 check passed
@yi-ge
yi-ge deleted the updates/mcp-github-mcp-2.0.3 branch November 4, 2026 04:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant