GitRuozhi/dsh-github-mcp

Name: GitRuozhi/dsh-github-mcp
Author: GitRuozhi

Plugin插件 Native原生 ⭐ 2 MIT Notifications & Remote通知与远程 Dev Workflow开发与代码工作流

DSH-GitHub桥接：通过官方GitHub MCP服务器直接访问GitHub，并修复官方桥接中文件内容丢失的问题。

Project Overview项目介绍

Edited by Zhiwei Agent (zhiwei)由知微Agent(zhiwei)编辑

This is a DeepSeek Harness (DSH) plugin that exposes the official GitHub MCP server as DSH-native tools, fixing the original bridge's file content drop issue. It lets DSH agents interact with GitHub resources directly without local Git or gh CLI. Configure GITHUB_TOKEN first; tools are global, filter manually if you need to disable them for specific presets.

这是一款DeepSeek Harness（DSH）插件，将官方GitHub MCP服务器转换为DSH原生工具，修复了DSH原有桥接丢弃文件内容的问题。无需本地Git或gh CLI，即可让DSH代理直接交互GitHub资源，需配置GITHUB_TOKEN使用，工具默认全局注册，如需禁用需自行配置过滤。

View on GitHub在 GitHub 查看

Send to your DSH发给你的 DSH 安装

请帮我安装这个 DSH 插件。安装前先完成【兼容性检查 + 安全性检查】，检查通过再动手。

插件：dsh-github-mcp（GitRuozhi/dsh-github-mcp）
仓库：https://github.com/GitRuozhi/dsh-github-mcp
本站详情页：https://www.yhbd.top/plugins/gitruozhi-dsh-github-mcp/
本站登记：类型 plugin · 归类 原生 DSH 插件 · 许可证 MIT · ⭐ 2 · 最近提交 2026-09-17 · 主语言 JavaScript

按下面顺序执行，每步先把结论告诉我，再进入下一步：

【1 兼容性检查】
① 我这边：DSH 版本、Node 版本、操作系统、当前 profile（web / desktop）。
② 读它的 README、package.json、插件 manifest，列出它要求的 DSH 版本 / Node 版本 / 操作系统 / 外部依赖 / 需要另外先装的运行时。
③ 逐条比对，结论只写「满足 / 不满足 / 未知」三种；不满足的给出可行替代方案。
④ 检查是否和我已装的插件冲突：命令名重复、skill / tool 重名、端口占用、重复注册的 MCP server。

【2 安全性检查】
① 仓库可信度：和上面「本站登记」是否一致；star / fork 数、创建时间、最近提交，是否归档或长期停更。
② 安装脚本：逐行看 package.json 的 preinstall / install / postinstall，以及 install.sh、setup.ps1 之类脚本。出现 curl|bash、下载后直接执行、混淆代码、访问与插件功能无关的域名，立刻停下来告诉我，不要继续装。
③ 依赖：列出新增依赖，标出无人维护、或与知名包拼写近似的可疑包（typosquatting）。
④ 权限与副作用：它会读写哪些目录、访问哪些域名、需要哪些 DSH 权限（filesystem / network / shell / clipboard 等），以及怎么卸载和回滚。
⑤ 如果它要求 sudo / 管理员权限，或权限明显超出功能所需，先停下来问我。

【3 安装】
上面两步没有「不满足」和「高危项」时才执行；用官方推荐方式安装，不要自行提权。

【4 汇报】
用表格输出：检查项 / 结论 / 依据 / 是否需要我决策。拿不准的一律写「未知」并说明要我怎么确认——不要猜，也不要替我决定。

Send this message to DSH in your current session: it verifies compatibility and security first (answering met / not met / unknown item by item) and only installs once everything checks out — it will stop and ask you if it finds a high-risk item. The box scrolls; the copy is the full prompt. CLI install commands may not be accurate across systems, so DSH is the safer route.把上面这条消息直接发给当前会话里的 DSH：它会先核对兼容性与安全性（逐条给「满足 / 不满足 / 未知」），确认没问题再安装，有高危项会停下来问你。框内可滚动，复制到的是完整提示词；安装命令不一定准确，发给 DSH 更稳。

Pre-install check安装前体检Compatibility · Security兼容性 · 安全性 1 warning1 项注意

Only 2 stars - very few users, little community feedback星标只有 2，几乎没人在用，遇到问题缺少社区反馈

DSH walks through these 9 checksDSH 会逐条核对这 9 项

Compatibility兼容性

DSH, Node, OS and profile requirementsDSH 版本 / Node 版本 / 操作系统 / profile 是否满足要求
External dependencies and runtimes (Electron / Python / Docker, ...)外部依赖与运行时（Electron / Python / Docker 等）是否齐备
Conflicts with installed plugins: command names, skill / tool names, ports, duplicate MCP registration与已装插件是否冲突：命令名、skill / tool 重名、端口占用、重复 MCP 注册

Security安全性

Repo matches the facts registered here; archived or abandoned?仓库是否与页面登记一致，是否归档或长期停更
Safety of preinstall / install / postinstall and install.sh / setup.ps1preinstall / install / postinstall 与 install.sh、setup.ps1 是否安全
curl|bash, download-then-execute, obfuscation, unrelated domains → stop immediatelycurl|bash、下载即执行、混淆代码、无关域名 → 立刻停止
Typosquatting or unmaintained packages among the new dependencies新增依赖里有没有 typosquatting 或无人维护的包
Requested permissions vs. what the feature actually needs申请了哪些权限、是否超出功能所需（filesystem / network / shell / clipboard）
Any sudo / admin requirement, plus uninstall and rollback是否要求 sudo / 管理员权限，以及卸载与回滚方式

Anything uncertain must be marked unknown with a note on how to confirm it. This site's signal screen is a static snapshot, not a security audit.拿不准的必须标「未知」并说明要我怎么确认。本站的信号筛查是静态快照，不能替代安全审计。

Or use CLI install (for developers)或使用命令行安装（适合开发者）

CLI Install命令行安装

dsh plugin --profile web add github:GitRuozhi/dsh-github-mcp

把 GitRuozhi/dsh-github-mcp 加入你的 DSH 配置（web profile）即可启用。

READMEREADME

4.4 KB · 缓存于 2026-09-25 22:11:50 · 4.4 KB

dsh-github-mcp

DSH-GitHub bridge: exposes the official GitHub MCP server as DSH-native tools, and fixes the issue where DSH's bridge discards file content.

After install, the agent can reach GitHub and read files directly through the mcp__github__* tool family and the github_file_read tool — no local Git or gh CLI in between.

Install

dsh plugin --profile web add github:GitRuozhi/dsh-github-mcp

Set GITHUB_TOKEN and restart dsh web. If gh is already logged in on this machine, you can just ask DSH to configure it for you.

Features


✅ Official	talks to GitHub's official `github-mcp-server`
✅ Native MCP	speaks MCP directly — no `gh` wrapper, no hand-written REST
✅ Zero local deps	uses GitHub's hosted endpoint `https://api.githubcopilot.com/mcp/`
✅ Reads file bodies	`github_file_read` fixes the official bridge's dropped-content problem

Status (2026-09-17)

Still needed. Rechecked on DeepSeek Harness 0.1.5-rc.2 (@deepseek-ai/dsh-mcp-client 0.1.5-rc.2; upstream master is 0.1.6-alpha.1):

mcp__github__get_file_contents still returns successfully downloaded text file (SHA: …) plus [embedded resource unsupported; raw resource data remains available to programmatic callers]. The file body never reaches the model.
github_file_read still returns decoded UTF-8 text for the same path.

Official minimal inherits these tools (they register globally). A custom preset such as mini-win can mask them.

Tools

Two tool families are added on install:

github_file_read — read a file's contents (decoded to UTF-8 text) or list a directory; private repos work too (needs GITHUB_TOKEN).

mcp__github__* (44 tools from GitHub's official MCP server)

Search: search_repositories, search_code, search_issues, search_pull_requests, search_commits, search_users
Repos: create_repository, fork_repository, list_repository_collaborators, list_branches / create_branch, list_tags / get_tag, list_commits / get_commit
Files: get_file_contents, create_or_update_file, delete_file, push_files
Releases: list_releases, get_latest_release, get_release_by_tag
Issues: list_issues, issue_read, issue_write, sub_issue_write, add_issue_comment, get_label, list_issue_types / list_issue_fields, get_teams / get_team_members
Pull requests: list_pull_requests, pull_request_read, create_pull_request, update_pull_request, update_pull_request_branch, merge_pull_request, pull_request_review_write, add_comment_to_pending_review, add_reply_to_pull_request_comment, request_copilot_review
Other: get_me, run_secret_scanning

Showing the opening section of the README — the full document lives in the repository以上为 README 开头摘要，完整文档在仓库内 · View the full README on GitHub →在 GitHub 查看完整 README →

渲染基于仓库 GitRuozhi/dsh-github-mcp 的 README.md。在 GitHub 查看原文 →