dsh-cordis-mcp

Expose DeepSeek Harness's dynamic Cordis toolset to Claude Code via MCP (Streamable HTTP): Claude Code can load, define, run, update, stop, delete DSH dynamic plugins in real time—the exact same capabilities as using cordis_define / cordis_run / cordis_stop / cordis_undefine / cordis_inspect_* in a DSH session, through the same runtime agent.

┌─────────────┐   MCP (Streamable HTTP, loopback)   ┌───────────────────────────┐
│ Claude Code │ ────── http://127.0.0.1:8090/mcp ──▶ │ DSH host (本插件)           │
│  (claude)   │ ────── JSON-RPC 2.0 ───────────────▶ │  dynamicCordisRunner      │
└─────────────┘                                       │  cordisInspect            │
                                                      │  agents (会话解析)         │
                                                      └───────────────────────────┘

The plugin mounts on the existing web port—no new ports, no published services; the MCP endpoint enforces Bearer authentication, and the token is configured on the DSH Settings → dsh-cordis-mcp page (auto-generated on first use, customizable/regenerable).

Capabilities (10 tools)

Packages with a Client half still go through DSH's approval flow on first run: dsh_plugin_run returns awaiting-approval, and completes asynchronously after you click Allow on the Run card in the DSH Web GUI—same as in a DSH session.

Related MCP server: cc-plugin-mcp

One-click install

curl -fsSL https://raw.githubusercontent.com/GeekRicardo/dsh-cordis-mcp/main/install.sh | bash

What the script does (preview with --dry-run first):

1. Writes the dependency "dsh-cordis-mcp": "github:GeekRicardo/dsh-cordis-mcp" into ~/.dsh/profiles/web/package.json;

2. Appends dsh-cordis-mcp to dsh.profile.bundles;

3. cd ~/.dsh/profiles/web && pnpm install;

4. Verifies bundles are registered, prompts for a restart.

After restarting DSH and hard-refreshing the page, the MCP endpoint is ready alongside the web service:

pm2 restart dsh-web   # 若用 pm2 托管；否则用你的启动方式重启

Connecting Claude Code

# 端口换成你 DSH web 的实际端口（启动日志会打印完整地址）
claude mcp add dsh --transport http http://127.0.0.1:8090/mcp
claude mcp list          # 确认 connected

Authentication (mandatory, no direct connection)

The MCP endpoint enforces Bearer authentication—requests without a token always get 401 (503 if no token is configured). The token is configured on the DSH Settings → dsh-cordis-mcp page: auto-generated and persisted on first use; the page supports view/copy/customize/regenerate. Put the token into the request headers of .mcp.json:

{
  "mcpServers": {
    "dsh": {
      "type": "http",
      "url": "http://127.0.0.1:8090/mcp",
      "headers": { "Authorization": "Bearer <设置页里的 token>" }
    }
  }
}

Token resolution priority: settings page config > DSH_MCP_TOKEN environment variable > auto-generated. Token changes take effect immediately (no restart needed); after regeneration the old token is immediately invalidated, so you must update the Claude Code config accordingly.

Session semantics (important)

Dynamic plugins are scoped per session and live in process memory (cleared on DSH restart). The bridge's session resolution order:

1. sessionId in the call arguments (look it up with dsh_sessions);

2. The session specified by the DSH_MCP_DEFAULT_SESSION environment variable;

3. The current single live session;

4. Multiple live sessions but none specified → error listing the options, requiring sessionId to be passed.

Other environment variables

Security boundary

• Mandatory Bearer auth: no token → always 401 / 503, the endpoint can never be connected to directly;

• Only accepts loopback Hosts (127.* / localhost / ::1), rejects all external access;

• Rejects browser requests with sec-fetch-site: cross-site, and never returns CORS headers—web pages cannot read the response;

• The settings page route /dsh-cordis-mcp/settings only allows same-origin loopback (no MCP token needed, but it only changes the token config itself);

• This endpoint can define/run/delete plugins—equivalent to shell privileges—don't expose the port beyond the local machine.

How it works

Uninstall

# 1. 从 ~/.dsh/profiles/web/package.json 的 dsh.profile.bundles 移除 "dsh-cordis-mcp"
# 2. 移除 dependencies 里的 "dsh-cordis-mcp"
# 3. cd ~/.dsh/profiles/web && pnpm install
# 4. 重启 DSH；claude mcp remove dsh

Prerequisites

• DeepSeek Harness has an initialized web profile (~/.dsh/profiles/web exists), and the current session runs on a preset with the Cordis toolset (the host-side dynamicCordisRunner service exists, which it does by default);

• Claude Code CLI is installed locally and logged in;

• Node.js ≥ 20, pnpm available.

Troubleshooting

License

MIT