AI Agent Hub
Back to plugins
⚙️

dsh-mcp-manager

Workflow Updated 2026.08.18

Run the following command in DeepSeek Harness:

dsh plugin install 1a125/dsh-mcp-manager

Paste the following prompt into your AI chat to install this plugin:

Run dsh plugin install 1a125/dsh-mcp-manager in the DeepSeek Harness terminal to install the plugin; the full source repository is available at https://github.com/1a125/dsh-mcp-manager .

About this plugin

Running multiple MCP services under DeepSeek Harness used to mean hand-editing the host config file, filling out repetitive forms for each server, and restarting only to hope everything wired up correctly. dsh-mcp-manager pulls all of that into a single MCP Management page inside the settings dialog, turning scattered config surgery into one visual dashboard where you add, toggle, delete, and inspect every MCP service in one place.

The daily workflow follows three simple paths. To add servers, paste a standard mcpServers JSON block and multiple services register at once, skipping the tedious per-field forms. To manage them, each service carries its own toggle and delete control that writes directly to the host cordis config and takes effect at runtime without requiring a restart. To inspect them, the panel surfaces live connection status, registered tool counts pulled from the host tool registry, and any error messages, so you can diagnose problems at a glance.

If you have already wired up two or more MCP services in DSH, or you want a single source of truth where your team maintains a consistent MCP configuration across projects and sessions, this plugin collapses repetitive manual edits into one visual panel, reducing the chance of YAML typos and eliminating the restart-and-pull-prayers cycle.

Use Cases

  • Batch-import multiple MCP services into the DSH host config by pasting a single JSON block
  • Toggle an MCP service on or off at runtime without restarting DSH
  • Check live connection status, tool counts, and error messages for every MCP service from the settings panel

Best For

  • Developers running two or more MCP services under DSH
  • Engineering teams that need a single source of truth for shared MCP configuration
  • Anyone who wants to stop hand-editing cordis.patch.yml and restarting over and over