chushixixin/dsh-harness-mcp-server

Name: chushixixin/dsh-harness-mcp-server
Author: chushixixin

Plugin插件 Native原生 ⭐ 12 MIT Productivity & Tasks效率与任务 Clients & Launchers客户端与启动器

将DeepSeek Harness代理能力作为MCP服务器暴露（大脑=Hermes，手臂=Harness）

Project Overview项目介绍

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

This is a native DSH plugin that exposes DeepSeek Harness’s built-in agent runtime as a Model Context Protocol (MCP) server. It lets any external MCP-compatible client, like the Hermes agent, delegate coding tasks directly to Harness’s powerful agent runtime. It spins up a StreamableHTTP MCP server inside your running Harness instance, then bridges Harness’s core services for agents, presets, and tools to create a clear interface for external clients. You can install it via npm directly, or clone it from source into your Harness workspace to build from scratch.

This plugin is designed to be used as a fallback tool rather than a daily development driver. It is most useful for large refactoring jobs that need context isolation, or when you need to run multiple unrelated tasks in parallel on the same codebase. It exposes five core tools to connected MCP clients: echo for connectivity checks, harness_list_tools to get registered tool names, agent_run for synchronous task execution, and task_inbox/task_result for async tasks. Agents reuse existing sessions per working directory, cutting down context reload time dramatically.

This plugin is released under the open source MIT license, so you can use or modify it freely for personal or commercial projects. By default, the MCP server binds only to 127.0.0.1 port 8090, so it is not accessible from outside the local machine. The server offers unauthenticated remote code execution, so you must add authentication, TLS, and a reverse proxy before exposing it to any network. It requires bubblewrap installed on the host to sandbox bash write commands, otherwise write operations will be blocked.

这是一款专为DeepSeek Harness（DSH）开发的原生Cordis插件，它将DSH内置的强大代理运行时能力暴露为符合Model Context Protocol规范的MCP服务器，允许任何外部MCP客户端（比如Hermes智能体）调用DSH来执行实际编码任务。它会在DSH内部启动一个StreamableHTTP协议的MCP服务，桥接DSH核心的代理、预设和工具服务，让外部“大脑”可以把具体工作委派给DSH执行。

开发者通常将这款插件用作后备工具而非日常开发驱动，适合处理需要上下文隔离的大型重构任务，或是需要并行执行多个无关任务的场景。外部MCP客户端可以调用它提供的echo、harness_list_tools、agent_run等工具，同步或异步推送任务到DSH，获取包含会话ID、变更内容、验证结果的结构化输出，再将结果回写到客户端的持久化内存中。

它使用MIT许可证开源，可通过npm或源码两种方式安装到DSH工作区，安装后需要在Harness的配置文件中注册插件，再启动Harness加载该服务。默认情况下MCP服务仅绑定本地127.0.0.1的8090端口，由于存在未认证的远程代码执行风险，禁止直接绑定到公网或未做访问控制的局域网。需要Bubblewrap来实现Bash命令的沙箱运行，否则写操作会被拒绝。

View on GitHub在 GitHub 查看

Send to your DSH发给你的 DSH 安装

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

插件：dsh-harness-mcp-server（chushixixin/dsh-harness-mcp-server）
仓库：https://github.com/chushixixin/dsh-harness-mcp-server
本站详情页：https://www.yhbd.top/plugins/chushixixin-dsh-harness-mcp-server/
本站登记：类型 plugin · 归类 原生 DSH 插件 · 许可证 MIT · ⭐ 12 · 最近提交 2026-08-15 · 主语言 TypeScript

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

【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 note1 项提示

12 stars - an early-stage project星标 12，属于早期项目

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:chushixixin/dsh-harness-mcp-server

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

READMEREADME

4.6 KB · 缓存于 2026-08-23 03:41:19 · 4.6 KB

dsh-harness-mcp-server

Expose DeepSeek Harness agent capabilities as an MCP server, letting any MCP client (e.g. Hermes) drive Harness to execute real coding tasks.

Hermes is the brain (pro), Harness is the arms (flash) — 1+1>2.

Why this exists

Harness ships a powerful agent runtime (tools, LLM, agents, sessions), but it is a Cordis app, not something another agent can call. This plugin turns Harness inside-out: it starts a real MCP server (StreamableHTTP) inside Harness and bridges Harness's core services — ctx.agents, ctx.agentPresets, ctx.tools — so an external "brain" can delegate real work to Harness's "arms".

Hermes (MCP client, brain)
   │  agent_run / task_inbox (HTTP)
   ▼
dsh-harness-mcp-server (MCP server, :8090)
   │  ctx.agents.create → mount 'standard' preset
   ▼
Harness agent (flash) — full toolset: bash, fs, todo, web…

Tools

Tool	Direction	Purpose
`echo`	—	Verify MCP connectivity
`harness_list_tools`	—	List Harness's registered tool names
`agent_run`	Hermes → Harness	Run a task synchronously and return a structured result
`task_inbox`	Hermes → Harness	Push a structured task (task + memory context + cwd) to an async queue
`task_result`	Hermes ← Harness	Poll a queued task's structured result

Every task result is structured:

{
  "sessionId": "...",
  "assistantText": "final answer",
  "toolCalls": [{ "name": "bash", "args": "..." }],
  "toolResults": ["command output"],
  "changes": "what was changed",
  "verification": "how it was verified",
  "leftovers": "open issues"
}

This closes the loop between the client's persistent memory and Harness's coding: memory is fed into each task as context, and the result (changes / verification / leftovers) can be persisted back to the client's memory for the next run.

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

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