Hermes Atlas
MCP servers & tool integrations

dsh-harness-mcp-server

chushixixin/dsh-harness-mcp-server

MCP server that lets Hermes drive DeepSeek Harness agents to run real coding tasks

In short

dsh-harness-mcp-server is an MCP server plugin for DeepSeek Harness that lets Hermes Agent, acting as the MCP client, delegate coding tasks to a Harness agent and receive structured results.

What dsh-harness-mcp-server does

DeepSeek Harness is a Cordis app that other agents cannot call directly. This plugin starts a StreamableHTTP MCP server inside Harness, listening on 127.0.0.1:8090 at /mcp, and bridges Harness's ctx.agents, ctx.agentPresets and ctx.tools services. The README frames Hermes as the brain and Harness as the arms. Hermes calls agent_run to run a task synchronously, or task_inbox to queue one and task_result to poll for it. Two further tools are echo, for a connectivity check, and harness_list_tools.

Every result is structured, with sessionId, assistantText, toolCalls, toolResults, changes, verification and leftovers, so the outcome can be written back into the client's persistent memory. Memory can also be passed in as context with each task. The README positions it as a fallback tool rather than a daily driver, useful for context isolation on very large refactors or for running unrelated work in parallel. Hermes is connected with a hermes mcp add command pointing at the local URL.

Key features

  • StreamableHTTP MCP server running inside DeepSeek Harness
  • agent_run for synchronous tasks and task_inbox plus task_result for queued ones
  • Structured results with changes, verification and leftovers fields
  • Memory passed in as context with each task
  • Optional Bearer token authentication and cwd allowlist in the cordis.yml patch

When to use it

  • Delegating a very large refactor to Harness so it does not fill the Hermes context window
  • Running unrelated coding tasks in parallel on Harness
  • Persisting what a Harness run changed and left open back into Hermes memory

Who it is for: Developers who run Hermes Agent and DeepSeek Harness and want Hermes to hand coding work to Harness.

How it fits with Hermes Agent

Hermes Agent is the intended MCP client: the README adds the server with hermes mcp add and describes Hermes as the planning side.

How to install dsh-harness-mcp-server

These commands are copied from the project's README. Check the repository for the latest steps before you run them.

npm install @chushixixin/dsh-harness-mcp-server
printf 'n\nY\n' | hermes mcp add harness_plugin --url http://127.0.0.1:8090/mcp

Requirements: A DeepSeek Harness workspace built with pnpm, a DEEPSEEK_API_KEY, and an MCP client such as Hermes

Note: By default the server exposes unauthenticated remote code execution and should stay bound to 127.0.0.1 unless authentication, TLS and a reverse proxy are added.

FAQ

What is dsh-harness-mcp-server?

dsh-harness-mcp-server is a plugin that exposes DeepSeek Harness agent capabilities as an MCP server, so an MCP client such as Hermes can run coding tasks on Harness and get structured results back.

Does dsh-harness-mcp-server work with Hermes Agent?

Yes. The README connects Hermes with hermes mcp add harness_plugin --url http://127.0.0.1:8090/mcp and describes Hermes as the brain and Harness as the arms.

Is it safe to expose dsh-harness-mcp-server to a network?

No, not by default. The README warns that the server exposes unauthenticated remote code execution and binds to 127.0.0.1 only. Add authentication, TLS and a reverse proxy before exposing it.

Similar mcp & tools for Hermes Agent

All mcp & tools

Related guides: What is Hermes Agent? · How to run Hermes Agent securely