dsh-mcphub

中文 | English

Chinese

MCP management panel for DeepSeek Harness. Adds an MCP section to the settings panel:

• Connection status: a green dot means the server's tools are registered in the live session (callable by the AI); grey means configured but not registered. Shows transport (stdio / HTTP), target, tool counts and samples.

• Upgrades: detects pip-installed stdio servers (e.g. scrapling), compares against PyPI, and upgrades in one click — including Windows file-lock handling (stop holders, park the old exe, restore on failure). npx-based servers are compared against the actual npx cache with a "refresh cache" action; @latest specs are never nagged (they self-update).

• Add servers: a form that appends proper cordis.patch.yml entries (serverName / transport / URL+headers or command+args+env). Takes effect after a DSH restart.

• Connectivity probe: HTTP servers get a real MCP initialize handshake (serverInfo + latency); stdio servers get an executable check.

• Help: tool naming (mcp__<server>__<tool>), how to invoke tools via the AI, manual config example, secret-safety notes, troubleshooting.

Install

# 从 GitHub
dsh plugin --profile web add github:jinhongxun/dsh-mcphub

# 或从 npm（如已发布）
dsh plugin --profile web add dsh-mcphub

Restart DSH after installation.

Privacy

Secrets in headers / env stay in the host process for probing only — they are never sent to the browser (the panel receives key names only).

FAQ: what is a profile?

A profile is DSH's isolated config environment (like browser profiles): each one keeps its own plugins and MCP server list. Example: a machine can have web (daily web UI) and open-design profiles, each with its own MCP servers. The profile picker in the add-server form decides which environment gets the new entry — with a single profile there is nothing to choose.

Requirements

• Node.js ≥ 20

• DeepSeek Harness (ships the dsh-client-connection channel in official builds)

How is the status determined?

Green/grey dots are not maintained by the plugin itself: the plugin reads the live tool registry. If a server has mcp__<server_name>__* tools registered, it is considered connected. The advantage is zero intrusion, always consistent with actual capabilities; the edge case is "connected but exposing 0 tools" showing as a grey dot. All configuration changes (add/pause/delete/upgrade) take effect after restarting DSH.

Screenshots

To be added: screenshot of the Settings panel → MCP section.

Compatibility

Works on Windows / macOS / Linux (upgrade actions branch per platform: PowerShell ↔ pkill, where ↔ command -v, npm cache path auto-detected).

English

MCP management panel for DeepSeek Harness. Adds an MCP section to the settings panel:

• Connection status: a green dot means the server's tools are registered in the live session (callable by the AI); grey means configured but not registered. Shows transport (stdio / HTTP), target, tool counts and samples.

• Upgrades: detects pip-installed stdio servers (e.g. scrapling), compares against PyPI, and upgrades in one click — including Windows file-lock handling (stop holders, park the old exe, restore on failure). npx-based servers are compared against the actual npx cache with a "refresh cache" action; @latest specs are never nagged (they self-update).

• Add servers: a form that appends proper cordis.patch.yml entries (serverName / transport / URL+headers or command+args+env). Takes effect after a DSH restart.

• Connectivity probe: HTTP servers get a real MCP initialize handshake (serverInfo + latency); stdio servers get an executable check.

• Help: tool naming (mcp__<server>__<tool>), how to invoke tools via the AI, manual config example, secret-safety notes, troubleshooting.

Install

# from GitHub
dsh plugin --profile web add github:jinhongxun/dsh-mcphub

# or from npm (once published)
dsh plugin --profile web add dsh-mcphub

Restart DSH after installing.

Privacy

Secrets in headers / env stay in the host process for probing only — they are never sent to the browser (the panel receives key names only).

FAQ: what is a profile?

A profile is DSH's isolated config environment (like browser profiles): each one keeps its own plugins and MCP server list. Example: a machine can have web (daily web UI) and open-design profiles, each with its own MCP servers. The profile picker in the add-server form decides which environment gets the new entry — with a single profile there is nothing to choose.

Requirements

• Node.js ≥ 20

• DeepSeek Harness (ships the dsh-client-connection channel in official builds)

Compatibility

Works on Windows / macOS / Linux (upgrade actions branch per platform: PowerShell ↔ pkill, where ↔ command -v, npm cache path auto-detected).

License

MIT