Nichts0v0/dsh-mcp-manager
30Last commit Aug 15, 2026
dsh-mcp-manager DSH plugin
This plugin adds a dedicated 'MCP Server Manager' page to the DSH Web settings. It allows you to manage MCP server connections at runtime, including add, edit, enable/disable, reconnect, and delete operations. Servers are displayed as cards with live status; tools are registered globally as mcp__<serverName>__<tool> for every session.
How to install the dsh-mcp-manager DSH plugin
dsh plugin --profile web add dsh-mcp-managerCopying does not run this command. Review the repository and version before installing the dsh-mcp-manager DSH plugin.
dsh-mcp-manager DSH plugin data source
dsh-mcp-manager DSH plugin snapshot date: Aug 16, 2026
discovered
What the dsh-mcp-manager DSH plugin can do
- Web settings UI for managing MCP servers with live status badges and card-based layout.
- Runtime connections: servers connect/disconnect on the fly; tools are registered globally for all sessions.
- Auto-reconnect with exponential backoff (3s → 60s) and manual refresh trigger.
- Enable/disable servers to immediately disconnect and unload their tools.
- Config file hot sync: watches $DSH_HOME/mcp-servers.json and applies changes within ~1s.
- HTTP API for programmatic management of servers (add, update, toggle, reconnect, delete, reload).
Where the dsh-mcp-manager DSH plugin fits
- Adding a new MCP server (e.g., a local tool server) via the settings page and connecting it immediately.
- Disabling a misbehaving server without deleting its configuration, then re-enabling it later.
- Editing an existing server's URL or command without restarting DSH.
- Reconnecting a server that went offline due to network issues.
- Managing multiple MCP servers across different profiles using the shared config file.
Who the dsh-mcp-manager DSH plugin is for
- DSH users who need to manage multiple MCP servers from a single Web interface.
- Developers extending DSH with MCP-based tools and want runtime control over server connections.
dsh-mcp-manager DSH plugin limitations
- Initial failure retries with backoff, not instantly — a failed first connect shows error and retries up to every 60s.
- Reachability probing is HTTP-level only (GET with 2.5s timeout for streamable-http); stdio servers are not probed.
- Only MCP tools are bridged; Resources/Prompts are not supported.
- Auth is token-only, loopback-by-default; must set a token before exposing the API to non-loopback addresses.
- Some MCP servers allow only one active client (e.g., Godot MCP), so a second connection is rejected until the first is released.
dsh-mcp-manager DSH plugin: from the repository README
Quoted from the Nichts0v0/dsh-mcp-manager README, the upstream source of the dsh-mcp-manager DSH plugin. Copyright remains with the original authors.
Manage **MCP servers** right from the DeepSeek Harness Web settings page — add, edit, enable/disable, reconnect and delete servers at runtime, with live status, automatic reconnect and config-file hot sync. ## Features - **Web settings UI** — a dedicated "MCP Server Manager" page: server cards with live status, an add/edit form, and two-step delete protection. - **Runtime connections** — servers connect/disconnect on the fly; tools are registered globally as `mcp__<serverName>__<tool>` for every session. - **Live status** — reachability probing so a closed server shows **offline** instead of a stale "connected"; a stuck connection times out after 30 s. - **Auto-reconnect** — a failed initial connect retries with exponential backoff (3 s → 60 s); pressing refresh retries immediately. - **Enable/disable** — switch a server off to disconnect and unload its tools; switch it on to reconnect. - **Config file hot sync** — `$DSH_HOME/mcp-servers.json` is watched; external edits take effect within ~1 s, no restart needed. - **Themes & i18n** — follows DSH light/dark mode (and `--dsw-alias-*` token overrides from appearance plugins); UI ships in **简体中文 / English**. ## Screenshot ![MCP Ma
Read the full READMERepository license: MIT
dsh-mcp-manager DSH plugin questions
How do I install dsh-mcp-manager?
Run `dsh plugin --profile web add dsh-mcp-manager` in your terminal. If you prefer building from source, clone the repo, run `npm install && npm run build`, then symlink the folder into your profile's node_modules. After installation, you must mount the plugin row in `cordis.patch.yml` and restart `dsh web`.
How do I add a new MCP server?
Open DSH Web settings, go to the 'MCP Server Manager' page, and click the 'Add' button. You can choose between 'streamable-http' (URL + optional headers) or 'stdio' (command + args). Fill in the required fields and set a connection-wait timeout. The server will be added and connected automatically.
How do I enable/disable a server without deleting its config?
On the server card, there is an enable/disable switch. Toggling it off will immediately disconnect the server and unload its tools. Toggling it on will reconnect it. The configuration remains in `mcp-servers.json` for later use.
How do I set up authentication for the MCP Manager API?
Add a `token` field at the top level of `$DSH_HOME/mcp-servers.json` (generate one with `node -e "console.log(require('crypto').randomBytes(24).toString('hex'))"`). Then all API requests must include `Authorization: Bearer <token>` header. Also enter the token in the settings page so the browser sends it automatically.
Why is my server showing 'Offline' status?
The plugin probes reachability with an HTTP GET (2.5s timeout) for streamable-http servers. If the server is not responding, it shows 'Offline'. For stdio servers, probing is not performed, so the status may remain 'Connected' even if the process died. You can manually trigger a reconnect from the settings page.