Chhlafiu4312/dsh-mcp-bridge

Name: Chhlafiu4312/dsh-mcp-bridge
Author: Chhlafiu4312

Plugin插件 Native原生 ⭐ 3 MIT Notifications & Remote通知与远程

DeepSeek Harness 的零依赖 MCP 客户端桥接器：连接 stdio/HTTP MCP 服务器，并自动为其工具注册代理。

Project Overview项目介绍

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

dsh-mcp-bridge is a DSH-native plugin that connects the entire Model Context Protocol (MCP) ecosystem to DeepSeek Harness. It is built from ~400 lines of plain JavaScript with zero dependencies, no SDK or native modules required, and uses raw JSON-RPC 2.0 over stdio for communication. It lets DSH agents access thousands of MCP-hosted tools from both local stdio servers and remote HTTP/SSE servers directly as native DSH tools, no custom development required. The recommended installation method is via the DSH plugin CLI, and it can also be added dynamically for a single session or set up as a permanent agent preset.

After installation, users configure their MCP servers via the DSH_MCP_SERVERS environment variable as a JSON array, with options for server ID, executable path, arguments, environment variables, remote URLs, timeout settings and tool allow/deny filters. Once configured, the bridge automatically registers all available MCP tools to the DSH tool registry following the mcp_<server-id>_<tool-name> naming convention. Unsupported JSON schema keywords are safely degraded, with the MCP server remaining the final authority for tool input validation, keeping boundary integrity intact. When the plugin stops or updates, all child MCP processes are automatically terminated to avoid resource leaks, and this plugin is perfect for DSH users wanting to expand tool capabilities quickly.

dsh-mcp-bridge has no external dependencies, so installation is nearly instant, and the small ~400 line codebase is easy to review for security. It is released under the permissive open-source MIT license, and community contributions via issues and pull requests are welcome. If you have previously installed a pre-0.7.0 version, you should remove the old package first to avoid conflicts, as the legacy npm package was renamed to dsh-mcp-connect. Users should note that MCP servers run with local user permissions, so only connect to trusted servers, and if npx-based servers fail with permission errors, you can fix npm cache ownership or set a writable cache per server.

这是一款专为 DeepSeek Harness (DSH) 打造的原生插件，作用是将整个 Model Context Protocol (MCP) 工具生态接入 DSH。它支持同时对接本地 stdio 服务和远程 HTTP/SSE 服务，让 DSH 代理可直接调用任意 MCP 服务的数千种工具，涵盖文件操作、GitHub 协作、数据库查询等，全程零依赖，无需额外安装 SDK。用户可通过 DSH 内置插件管理器一键完成安装。

插件会自动将所有已连接 MCP 服务的工具注册到 DSH 工具注册表，遵循 mcp_<服务ID>_<工具名> 的统一命名规范，还提供 mcp_status 工具供用户查看所有已配置 MCP 服务的连接状态。当插件停止或更新时，它会自动终止所有子进程，避免资源泄漏和僵尸进程。这款插件适合想要快速拓展 DSH 代理工具集，又不想自己开发定制工具的用户使用。

这款插件由约 400 行纯 JavaScript 编写，直接使用原生 JSON-RPC 2.0 通信，没有任何第三方依赖，因此安装过程瞬间完成，代码也易于审查。它采用 MIT 开源许可证开放使用，社区欢迎用户提交问题和贡献代码。用户需要注意，MCP 服务以当前用户权限运行，仅连接可信服务，API 令牌需通过环境变量妥善保管。

View on GitHub在 GitHub 查看

Send to your DSH发给你的 DSH 安装

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

插件：dsh-mcp-bridge（Chhlafiu4312/dsh-mcp-bridge）
仓库：https://github.com/Chhlafiu4312/dsh-mcp-bridge
本站详情页：https://www.yhbd.top/plugins/chhlafiu4312-dsh-mcp-bridge/
本站登记：类型 plugin · 归类 原生 DSH 插件 · 许可证 MIT · ⭐ 3 · 最近提交 2026-08-16 · 主语言 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 3 stars - very few users, little community feedback星标只有 3，几乎没人在用，遇到问题缺少社区反馈

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:Chhlafiu4312/dsh-mcp-bridge#main"

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

READMEREADME

10.8 KB · 缓存于 2026-08-25 04:53:49 · 10.8 KB

dsh-mcp-bridge

Connect the entire MCP ecosystem to DeepSeek Harness with one file. Zero dependencies. No SDK.

Your DSH agent gets every tool from any MCP server — filesystem, GitHub, databases, search, memory, and thousands of community servers — as native tools it can call directly:

You: Create a GitHub PR for the changes in ./app
Agent: [calls mcp_github_create_pull_request] ✓ PR #42 created

architecture

✨ Why people use it


🔌 One line to 1000+ tools	The MCP ecosystem is the largest tool catalog for agents. This bridge plugs all of it into DSH.
🪶 Zero dependencies	Raw JSON-RPC 2.0 over stdio, ~400 lines of plain JavaScript. No SDK, no native modules.
🌐 stdio + HTTP/SSE	Local servers via `command`, remote servers via `url` (bridged through `mcp-remote`).
🔁 Auto-registration	Every tool becomes `mcp_<server>_<tool>` the moment the server connects.
🧹 Clean lifecycle	Child processes are terminated when the plugin stops or updates.
🛡️ Honest boundaries	Unsupported JSON-Schema keywords degrade to open inputs — the MCP server stays the authority.

🚀 Quick start

A. dsh plugin add (recommended — the repo is a dsh.bundle)

dsh plugin --profile web add "github:Chhlafiu4312/dsh-mcp-bridge#main"

Then restart dsh web and configure servers via DSH_MCP_SERVERS (see below).

B. Dynamic plugin (one session, no files)

Open a DSH session, ask your agent to run the bridge via cordis_define (paste the code from plugin.js), or define it yourself — then talk to it:

// code.host body — minimal form
return {
  inject: ['subprocess', 'tools', 'timer'],
  apply(ctx) {
    // ... paste the body of plugin.js here ...
  },
}

C. Permanent (agent preset)

# 1. create your preset directory
mkdir -p ~/.dsh/.agent-presets/mcp-agent

# 2. copy the repo files in
cp plugin.js ~/.dsh/.agent-presets/mcp-agent/
cp agent.cordis.yml.example ~/.dsh/.agent-presets/mcp-agent/agent.cordis.yml
cp preset.yml.example ~/.dsh/.agent-presets/mcp-agent/preset.yml

# 3. (optional) configure your servers
export DSH_MCP_SERVERS='[
  {"id":"filesystem","command":"npx","args":["-y","@modelcontextprotocol/server-filesystem","~/projects"]},
  {"id":"github","command":"npx","args":["-y","@modelcontextprotocol/server-github"],"env":{"GITHUB_PERSONAL_ACCESS_TOKEN":"your_github_token"}}
]'

# 4. start a session on the `mcp-agent` preset — done

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

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