dsh-mcp-hub

In DeepSeek Harness, MCP server configurations are scattered across cordis.patch.yml and per-bundle patch files, making manual edits tedious and error-prone. Worse, there is no immediate way to see which servers are actually connected in the current process. dsh-mcp-hub adds an "MCP" tab to the conversation view ring, consolidating every server into a single card-based panel where you can add, edit, and remove entries with a few clicks.

The panel reads the live tool registry of the running process and reverse-maps each connected MCP server by its mcp__ prefix, showing the number of exposed tools at a glance. Servers that are configured but not yet connected are clearly flagged, which makes troubleshooting unreachable endpoints or missed stdio arguments far less painful. Saving any change rewrites cordis.patch.yml immediately; newly added servers typically hot-connect without a restart. The whole plugin ships with zero runtime dependencies and no build step, reusing the host React runtime natively.

If you run DeepSeek Harness with multiple MCP services—whether over streamable-http, SSE, or stdio—and find yourself constantly digging into YAML files to tweak a URL or an environment variable, this is the plugin you need. It turns configuration management into an open-the-tab, click, and save workflow while preserving read-only visibility into bundle-level patches, giving you both flexibility and traceability without ever leaving the conversation interface.