dsh-mcp-servers
Standalone development home for the DeepSeek Harness MCP plugins. These packages were extracted from the deepseek-harness monorepo so the MCP plugin stack can be developed, tested, and published on its own. The harness checkout keeps its own copies; this repository is the independent source of truth going forward.
Packages
| Package | Role |
|---|---|
@deepseek-ai/dsh-mcp-client |
MCP client bridge that registers external server tools on ctx.tools |
@deepseek-ai/dsh-mcp-servers |
Runtime MCP connection registry and Remote gateway behind ctx.mcp, with Web UI persistence |
@deepseek-ai/dsh-client-ui-mcp-servers |
MCP connection management page in Web Settings |
examples/mcp-memory/ holds the default-off reference overlays that connect memory servers through the generic MCP client.
Requirements
- Node
^22.19 || >=24 - pnpm 11
Develop
pnpm install
pnpm build # tsc -b + tsdown runtime bundles + ui client bundle
pnpm test # vitest unit + keyless e2e suites
pnpm clean # remove lib/ and build stateInstall and use
The packages publish to npm under the @deepseek-ai scope. Install the ones you need in a DSH profile, then reference them from a cordis.patch.yml layer exactly as the harness does — for example, connect a memory server with one of the shipped overlays:
dsh web --patch "$PWD/examples/mcp-memory/memorix.cordis.yml"No MCP server is enabled by default: every server command is trusted executable code outside the agent sandbox, so each connection is an explicit configuration. See each package README for its config schema and model-facing behavior.
License
MIT — see LICENSE.