tonytanglab/deepseek-harness-relay-mcp

Delegate long-running work to DeepSeek Harness from any MCP agent—and monitor it to completion.

Harness Relay MCP is the MCP control plane for DeepSeek Harness: it attaches to an existing official Harness Host and exposes that Host's native session/event/plugin/workspace/permission lifecycle to external MCP-capable agents (Codex, Claude Code, OpenCode, Cursor and other standards-compliant clients). It is not a model wrapper — tasks run inside the real Harness with its registered workspaces, tools, plugins, provider catalog and native permission presets (read-only, workspace-write, danger-full-access). The full asynchronous lifecycle is covered: start, status, wait, steer, reply, cancel, reopen, with durable run identities, idempotency, reconciliation and restart recovery. Provider/model/reasoning-effort/agent-preset selection happens before the first task prompt; ordered text plus bounded-base64 inline images are supported; each run returns a stable Harness Web session link with explicit visible-page verification in the bundled Skill. The package ships a Codex plugin (external caller layer) and a standalone dsh-relay mode kept for older Harness versions.

Agent Capabilities ★ 1 updated 2026-09-14 ⚠️ needs adapt
View on GitHub ↗

Install

dsh plugin --profile web add harness-relay-mcp

npm harness-relay-mcp 0.2.6 verified 2026-09-02 (repository field → github.com/tonytanglab/deepseek-harness-relay-mcp; README EN primary with zh edition link). Recommended install is as a Harness bundle: dsh plugin --profile web add harness-relay-mcp, then dsh --profile web --dump-config to inspect the composed layer and dsh --profile web to start. An offline/pinned install downloads the release tarball and points the same command at the local .tgz. If dsh web is already running, restart the Host after install/upgrade. Uninstall: dsh plugin --profile web remove harness-relay-mcp (does not cancel submitted work).

Compatibility

Node.js ^22.19 or >=24; internal mode requires DeepSeek Harness >=0.1.2-alpha.2 <0.2.0 (web profile, 127.0.0.1 bind; Relay 0.2.6 and earlier target the removed rc.7 ApiProxy surface); target workspace must be registered by Harness or inside an allowed root.

Details

Recent updates

Native Harness sessions/events over MCP; complete async lifecycle; read-only/workspace-write/danger-full-access permissions; durable identities + restart recovery; Web session links; Codex plugin; standalone relay mode for older Harness.

FAQ

Is this a DeepSeek model wrapper?
No — it is the MCP control plane for DeepSeek Harness: an MCP client controls a running Harness Host, which executes the work with its native plugins, permissions and sessions.
Which Harness versions does the internal bundle need?
Harness >=0.1.2-alpha.2 <0.2.0 with the web profile on a 127.0.0.1 bind; Relay 0.2.6 and earlier target the removed rc.7 ApiProxy surface and do not load in this line.
Which MCP clients can connect?
Standards-compliant MCP clients such as Codex, Claude Code, OpenCode and Cursor connect through the authenticated proxy or the stateless stdio proxy.

Alternatives

Noelune/dsh-agent-relay · LeslieWylie/dsh-task-relay · ben7am1n/dsh-mcp-proxy

More plugins in Agent Capabilities

Browse more in Agent Capabilities

Guides for Agent Capabilities plugins