AI Agent Hub
Back to plugins
🖥️

dsh-mcp-manager

Client Updated 2026.08.18

Run the following command in DeepSeek Harness:

dsh plugin install welsione/dsh-mcp-manager

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

Run dsh plugin install welsione/dsh-mcp-manager in DeepSeek Harness to install this plugin, source code: https://github.com/welsione/dsh-mcp-manager

About this plugin

Once a DeepSeek Harness profile hosts several MCP servers, starting and stopping individual instances, checking connectivity, and keeping configs in sync across clients usually means hand-editing YAML and restarting the service. dsh-mcp-manager pulls all of that into a single settings-page panel: it lists every mcp-client instance (name, source, transport, endpoint), supports search, filtering, and one-click toggles. Disabling an instance disposes the loader entry, severs the connection, and unregisters all mcp____* tools globally for every agent and sub-agent—no restart required.

The plugin also auto-discovers MCP configs already present on your machine—Claude Code global and project mcpServers, the Claude Desktop config file—and lets you import them with one click from the panel. Combined with a declarative mcp-servers.json mount and a live rescan hot-update, adding, removing, or changing connections takes effect immediately. The disable list persists across restarts, and the whole setup is zero-build, zero-compile.

It is designed for developers running three or more MCP servers in DSH, migrating configs from Claude Code or Claude Desktop, or anyone who needs fine-grained instance control without touching YAML. The start/stop capability works equally well in headless profiles without a Web GUI.

Use Cases

  • Toggle multiple MCP server instances from the DSH settings page without editing YAML
  • Auto-discover and import existing MCP configs from Claude Code or Claude Desktop with one click
  • Start, stop, and batch-manage MCP instances in headless mode without a Web GUI

Best For

  • Developers running three or more MCP servers in a single DSH profile
  • Users migrating MCP server configs from Claude Code or Claude Desktop
  • DSH users who want granular instance control without repeatedly hand-editing YAML