chushixixin/dsh-harness-mcp-server
Expose DeepSeek Harness agent capabilities as an MCP server (brain=Hermes, arms=Harness)
Turns Harness inside-out by starting a real MCP server (StreamableHTTP) inside Harness. It exposes echo (connectivity check), harness_list_tools (Harness's registered tool names), agent_run (run a task synchronously and return a structured result), task_inbox (push a structured task — task + memory context + cwd — to an async queue) and task_result (poll a queued task's structured result). Every task result is structured with sessionId, assistantText, toolCalls, toolResults, changes, verification and leftovers, which closes the loop between the client's persistent memory and Harness's coding: memory is fed into each task as context, and the result can be persisted back for the next run.
Install
npm install @chushixixin/dsh-harness-mcp-serverREADME Option A ("from npm (recommended)") quoted verbatim. Registry-verified live 2026-09-13: @chushixixin/dsh-harness-mcp-server 0.1.10 with a matching repository field (github.com/chushixixin/dsh-harness-mcp-server). After installing, reference the plugin from the Harness workspace through the cordis patch (the README's Run section): export DEEPSEEK_API_KEY=... then corepack pnpm dsh web --patch ./packages/mcp/harness-mcp-server/cordis.yml. The MCP server listens on 127.0.0.1:8090 (StreamableHTTP) and MCP clients point at http://127.0.0.1:8090/mcp. Option B is a source checkout placed inside the Harness workspace at packages/mcp/harness-mcp-server/ (the pnpm workspace matches packages//, two levels deep), registered in tsconfig.host.json references and tsconfig.base.json paths, then built with corepack pnpm exec tsc -b and corepack pnpm run build:lib:host.
Compatibility
Exposes Harness agent capabilities as an MCP server so any MCP client (the README's example is Hermes) can drive Harness to execute real coding tasks — "Hermes is the brain (pro), Harness is the arms (flash)". It bridges Harness's core services (ctx.agents, ctx.agentPresets, ctx.tools) and mounts the standard preset. Source mode expects the Harness monorepo layout.
Details
- Repo: chushixixin/dsh-harness-mcp-server
- Category: Agent Capabilities
- Stars: 9
- Version: npm @chushixixin/dsh-harness-mcp-server 0.1.10 (registry-verified 2026-09-13)
- Last push: 2026-08-15
- First seen: 2026-08-13
Recent updates
The README documents the two install paths, the tool contracts and the structured result shape rather than release-by-release notes; verify the current version on the registry.
FAQ
- What does this give an MCP client?
- Per the README it lets an external MCP client (e.g. Hermes) drive Harness: agent_run runs a task synchronously, while task_inbox / task_result provide an async queue with structured results.
- What port does the MCP server use?
- It listens on 127.0.0.1:8090 (StreamableHTTP); point your client at http://127.0.0.1:8090/mcp.
- Do I have to install from npm?
- No — Option A installs from npm and references the plugin from the workspace; Option B clones the repo into packages/mcp/harness-mcp-server/ inside the Harness monorepo and builds it from source.
Alternatives
hyqhyq3/dsh-mcp-manager · PerryLink/dsh-mcp-panel · ben7am1n/dsh-mcp-proxy