dsh-project-mcp-manager
Run the following command in DeepSeek Harness:
dsh plugin install wldxiaobai/dsh-project-mcp-manager
Paste the following prompt into your AI chat to install this plugin:
Run dsh plugin install wldxiaobai/dsh-project-mcp-manager in the DeepSeek Harness terminal to install this plugin; the project source is available at https://github.com/wldxiaobai/dsh-project-mcp-manager .
About this plugin
Managing MCP servers across multiple DSH projects means repeating the same manual steps every time: wiring connections, resolving name collisions, and hand-crafting which tools each session can see. dsh-project-mcp-manager collapses all of that into two config files in the project root (.dsh/mcp.yml or .dsh/mcp.json) that are mounted automatically the instant a session opens. Edits to those files hot-reload within a 150 ms debounce via chokidar, so there is no process restart and no manual re-trigger.
Built on the official @deepseek-ai/dsh-mcp-client, the plugin introduces a six-layer source governance model (global profile, user, project, and legacy Claude layers) with explicit shadow-priority ordering. Concurrent sessions in the same project share a single MCP connection, eliminating port and resource contention. Tool visibility is scoped per session cwd through tools.restrict, keeping servers declared in other projects invisible to the current agent. Conflicting serverNames receive a deterministic p_ prefix (truncated to 32 characters) to sidestep the per-process-root reservation conflicts that dsh-mcp-client enforces.
This plugin is aimed at developers who juggle several DSH projects and want MCP tools to stay isolated per project. It ships no UI; the entire workflow is configuration-driven, focused squarely on auto-mounting, hot-reload, and session-level tool isolation. stdio lines in config files are executable code carriers, so the plugin advises adding them only in trusted projects.
Use Cases
- Auto-mounting project-specific MCP servers whenever a DSH session opens in that directory
- Hot-reloading MCP config changes within 150 ms without restarting the dsh process
- Isolating MCP tool visibility per concurrent session so each agent only sees its own project servers
Best For
- Independent developers juggling multiple DSH projects with distinct MCP tool sets
- Engineering teams that require per-session MCP isolation to avoid cross-project resource contention
- Heavy DSH users who prefer a file-driven, zero-manual-setup workflow
Related Plugins
A network security red-team benchmark plugin for DeepSeek-V4.1/Flash featuring dual-layer kernel injection and zero-tool architecture for controlled model safety assessment.
A security red-team prompt plugin for DeepSeek-V4 that uses code-formal mapping and zero-trigger system prompts to enable unconditional output, intended for authorized testing and research only.
Adds an Auto approval mode on the official workspace-write sandbox, classifying semantic risks, asking when ambiguous, and denying destructive operations.
Undo/rollback system for DSH: config & plugin snapshots, one-click undo/redo/restore, message-level revert, secret masking, safe mode, and offline WebUI/GUI/CLI rescue tools for when DSH won't start.