Introduction

If you have configured a few MCP servers in DeepSeek Harness (hereinafter referred to as DSH), you are likely familiar with this process: manually editing the profile’s cordis.patch.yml, restarting DSH, and then praying it connects. There is no place to see which tools the servers have registered or if the pip-installed stdio servers have new versions; you can only sift through logs or try things out.

jinhongxun/dsh-mcphub solves this problem: it adds a new MCP section to DSH’s settings panel, moving connection status, version upgrades, adding servers, and connectivity testing onto the interface. Below is an introduction to its features, installation methods, and usage notes.

What is it

dsh-mcphub is a DSH plugin maintained by jinhongxun, licensed under MIT, with the current version being 0.3.1. It mounts the MCP section in the settings panel via DSH’s client injection mechanism (dsh.client.platform in package.json is web), completing all viewing and modifying of MCP configuration within the browser panel.

Core Features

Connection Status

The section lists all MCP servers for the current profile, with a status indicator for each server:

  • Green dot: The server’s tools have been registered in the current session and can be called by the AI;
  • Gray dot: Configured but tools are not registered.

It also displays the transport type (stdio / HTTP), target address, number of tools, and samples.

The status indicators are not maintained by the plugin itself: the plugin reads the running tool registry; a server is considered connected if it has tool registrations in the form mcp__<server_name>__*. This approach is non-intrusive, ensuring the status is always consistent with actual capabilities; the edge case is that a server that is “connected but exposes 0 tools” will appear as a gray dot.

Upgrade Management

It handles three types of servers differently:

  1. pip-installed stdio servers (e.g., scrapling): Automatically compares against the latest version on PyPI and displays an “Upgrade Available” badge if a new version exists, allowing for a one-click execution of pip install --upgrade. File locking issues on Windows have been handled: the process occupying the file is stopped first, the old exe is cached, and it is restored if the operation fails.
  2. npx-type servers: Compares against the actual version in the npx cache and provides a “Refresh Cache” operation.
  3. @latest specifications: Automatically pulls the latest version on every startup; the plugin does not repeat prompts.

Adding Servers

The form collects serverName / transport, and either URL+headers (HTTP type) or command+args+env (stdio type), appending them to the corresponding profile’s cordis.patch.yml to take effect after restarting DSH. If you prefer not to use the form, you can manually edit the configuration, as examples are provided in the panel’s usage instructions.

Connectivity Test

  • HTTP servers: Sends a real MCP initialize handshake and displays the remote serverInfo and latency;
  • stdio servers: Validates that the executable file exists.

Usage Instructions and Privacy

The panel includes built-in documentation covering tool naming rules, how to let the AI call tools, examples of manual configuration editing, security reminders for keys, and troubleshooting guides.

Regarding privacy, it is worth noting: keys in headers / env in the configuration file are only used in the Host process memory to probe the handshake and are never sent to the browser side; the panel only receives the key names.

Installation and Enablement

Environment requirements: Node.js ≥ 20, and DeepSeek Harness with the dsh-client-connection channel (included in the official release).

Installation commands:

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

# Or from npm (if published)
dsh plugin --profile web add dsh-mcphub

The npm installation method is marked as “if published” in the README. Whether it is actually listed on npm cannot be confirmed from existing materials; it is recommended to use the GitHub method first. After installation, DSH must be restarted for the changes to take effect.

Typical Usage

Letting the AI call MCP tools. The naming format for MCP tools in DSH is:

mcp__<server_name>__<tool_name>

For servers with green dots, their tools are registered in the session, so you can simply ask the AI to call them directly in the conversation.

Understanding profiles. A profile is DSH’s “independent configuration environment,” similar to browser user profiles: each profile has its own plugins and MCP list and does not affect each other. For example, a machine can have both web (daily web version) and open-design sets, each configured with its own MCPs. The profile selection in the “Add Server” form determines which environment’s cordis.patch.yml is written to—no need to worry about this if there is only one profile.

When changes take effect. All configuration changes (add, pause, delete, upgrade) require restarting DSH to take effect. Operations on the panel only change the configuration and do not hot reload.

Suitable Scenarios and Notes

Suitable scenarios:

  • Configured multiple MCP servers and want to know which ones are actually connected and have registered tools;
  • Frequently use pip / npx installed stdio servers and need to track version upgrades;
  • Don’t want to manually edit YAML and want to add servers via a form while also verifying connectivity.

A few notes:

  • Compatible with Windows / macOS / Linux. Upgrade actions are split by platform: PowerShell ↔ pkill, where ↔ command -v, and npm cache path is automatically detected.
  • The screenshot section in the README is marked “to be supplemented”; currently, it relies mainly on text descriptions.
  • Security reminder: The plugin runs with the permissions of the current DSH process. It is recommended to review the source code and license before installing third-party plugins. The source code for this plugin is open on GitHub under the MIT license (consistent between README and package.json).

Conclusion

What dsh-mcphub does is not complicated: it brings the “check status, upgrade version, add server, test connectivity” of MCP configuration in DSH into the settings panel, and it does not maintain the status itself, instead reading directly from the running tool registry. If you are using more than one or two MCP servers in DSH, installing this will save you a lot of time flipping through configuration files.

  • GitHub: https://github.com/jinhongxun/dsh-mcphub
  • Plugin Directory Page: https://www.skillhub.cn/plugins/jinhongxun/dsh-mcphub (Community-maintained independent directory, no official affiliation with DeepSeek / HF)