dsh-mcp-management: Independent MCP Tools per Workspace in DeepSeek Harness

What Does It Do?

MCP Management is a DSH plugin for DeepSeek Harness that scopes MCP servers to individual workspaces, so each project directory gets its own set of MCP tools. It solves the usual problem of MCP servers being configured once for the whole application, where a database tool, a GitHub tool and a JetBrains tool show up in every conversation. With this plugin, a session running in ~/work/api sees only the servers configured for that directory, while a session in ~/work/docs sees a different set or none at all. It is maintained by inkyi under the MIT license and written as plain ESM with no build step.

Core Features

• Per-workspace server lists: every workspace keeps its own server definitions, and a session receives only the servers of the workspace containing its working directory.
• Global defaults: optional defaultServers are inherited by every workspace, which is handy for tools you always want available.
• Project-local configuration: a /.dsh/mcp.json file can be committed to the repository, uses the familiar mcpServers shape, and takes precedence over the GUI-managed list.
• A real settings page: Settings → MCP Management edits workspaces and servers in place, covering stdio command/args/env/cwd and streamable-http URL/headers, plus enable and disable toggles.
• An agent tool: mcp_management lets the model inspect and manage the mapping through status, list, setServer, removeServer, setEnabled and setWorkspace.
• Live updates and secret-friendly config: servers mount on each Agent's own registration scope, so tools appear and disappear per session without a restart, and ${env:NAME} is expanded from the host environment at connect time so secrets never need to be written into configuration.

How to Use This Plugin?

After enabling it in a DSH web profile, open Settings → MCP Management to start configuring; if the navigation entry is missing, refresh the page once so the client half loads. Once you add servers for a project directory, sessions running in that directory pick up the matching tools automatically, while sessions elsewhere stay unaffected. To share configuration through version control, write the mcpServers block into /.dsh/mcp.json at the project root and commit it; for quick adjustments, edit commands, arguments or enabled state directly in the settings page and the change takes effect immediately.

How to Troubleshoot This Plugin?

If the MCP Management entry is missing from Settings, the client half has usually not loaded with the page yet, and a single page refresh restores it. If configured servers do not show up in a session, first confirm the session's working directory really falls inside the target workspace, then check whether that server is disabled and whether the precedence between the project config file and the GUI list matches what you expect.