Introduction

When using MCP services in DSH, configuring them per project and checking them per session can be quite scattered. dsh-mcp-manager centralizes MCP services into the “MCP Management” page of the settings popup and writes the service configuration uniformly to the host-level ~/.dsh/cordis.patch.yml file’s mcp-client line, to be loaded by the host.

Below, I will introduce its positioning, installation method, and typical usage.

What is it

dsh-mcp-manager is a DSH (DeepSeek Harness) global MCP manager, with the repository path at 1a125/dsh-mcp-manager. It solves the problems of unified adding, toggling, deleting, and viewing the status of MCP services within DSH.

This plugin declares dsh.client.platform as web and injects:

  • @deepseek-ai/dsh-client-runtime
  • @deepseek-ai/dsh-client-locale
  • @deepseek-ai/dsh-client-ui-slots

Core Features

  • Manage all MCP services uniformly in the “MCP Management” page of the settings popup.
  • Write MCP services uniformly to the host-level ~/.dsh/cordis.patch.yml (the mcp-client line), loaded by the host, callable by any project/session, and persisted after restart.
  • Support pasting standard mcpServers format JSON to add multiple services at once, without needing to fill out tedious forms.
  • Support enabling/disabling/deleting services by directly modifying the host cordis configuration (the disabled flag), achieving immediate connection/disconnection at runtime.
  • Display connected status, number of tools (detected in real-time via the host’s tool registry), and error messages.

Installation and Activation

  1. Install using the GitHub source. The following command adds the plugin to the web profile:
dsh plugin --profile web add "github:1a125/dsh-mcp-manager#main"
  1. Manual installation. Place dsh-mcp-manager into ~/.dsh/profiles/web/node_modules/, and append to ~/.dsh/profiles/web/cordis.patch.yml:
- insert:
    - id: mcp-manager
      name: 'dsh-mcp-manager'

After restarting DSH, the “MCP Management” page will appear in the settings popup.

Typical Usage

When adding services on the “MCP Management” page, paste the JSON containing mcpServers. For example, the following configuration declares a stdio service named my-server:

{
  "mcpServers": {
    "my-server": {
      "command": "node",
      "args": ["C:/path/server.js"],
      "env": { "API_KEY": "xxx" }
    }
  }
}

This plugin only supports stdio transport, and command is mandatory; it supports either a single server configuration or the mcpServers multi-service format.

Dependencies and Notes

package.json declares the following peerDependencies:

{
  "@deepseek-ai/cordis": "^4.0.1",
  "@modelcontextprotocol/sdk": "^1.0.0",
  "zod": "^3.0.0"
}

The license is MIT.

Enabling/disabling services directly modifies the host cordis configuration, and MCP services are loaded by the host. The plugin runs with the permissions of the current DSH process. Before installing, you should check the source code and license to decide whether to enable it.

  • Community directory page: https://www.skillhub.cn/plugins/1a125/dsh-mcp-manager
  • GitHub repository: https://github.com/1a125/dsh-mcp-manager