dsh-mcp-tools: Toggle MCP Tools on Demand in DeepSeek Harness

What Does It Do?

MCP Tools Manager is a DSH plugin for DeepSeek Harness that gathers scattered MCP servers and tools into a single settings panel. It solves the problem of every registered MCP tool flooding the model context, wasting tokens and risking accidental calls, by letting you switch servers and individual tools on demand. Its core capabilities include server add/disable/delete, Postman-style request headers, connectivity testing with an event log, and per-tool chip toggles.

Core Features

• Server management: supports both streamable-http (URL plus headers) and stdio (command, arguments, environment variables, working directory) transports, and can import multiple servers at once by pasting mcpServers JSON.
• Row-based request headers: keys are entered as key-value rows instead of a JSON text box, values are masked by default and can be revealed per row, and duplicate names are flagged inline.
• Real per-tool control: each tool is a chip that disappears from the model tool list when clicked, with search, select-all, invert and disable-all, plus full descriptions on hover.
• Connectivity test and event log: opens a temporary connection through initialize → tools/list → close, reporting latency, protocol version and tool count without disturbing running servers.
• Server toggle and config copy: turning a server off disconnects it and unregisters all its tools without deleting the config, and its mcpServers snippet can be copied in one click.
• Native DSH look and feel: reuses the harness design tokens and 32px inputs, adapts to light/dark and Chinese/English, and the client needs no build step.

How to Use This Plugin?

After enabling it in DSH, open the MCP section in settings and add a server: enter the URL for a remote server and paste the key into the header row (x-mcp-key by default). Click test connection, and once you see something like "connected · 95 tools · 478 ms", save it and turn the server switch on; tools then register with an mcp____ prefix for the model to call in a session. Disable unused tools from the expanded list, since fewer enabled tools mean a smaller tool schema on every request. State lives in a local state file, and deleting that file resets everything to empty until it is rebuilt on the next start.

How to Troubleshoot This Plugin?

If the MCP section is missing from settings, the bundle is most likely not enabled: confirm it on the plugin page and refresh, restarting the DSH service if needed. If tools do not appear in a session, check that the server switch is on and the matching tool chips are enabled, because disabled tools are never registered. When a connection test fails, verify the URL, that the server uses streamable-http rather than plain SSE, and that header names match what the server expects; network or proxy issues also surface here.