Introduction

DSH (DeepSeek Harness) adopts a plugin-based architecture. When using DSH for agent development, managing MCP (Model Context Protocol) servers often requires manual configuration or reliance on global settings. dsh-project-mcp-manager extends the original DSH codebase to provide more complete MCP management capabilities at the project and user levels.

What Is It

This is a plugin built by extending the original DSH codebase and maintained by wldxiaobai. Its core purpose is to address the fragmentation of MCP configurations in multi-project environments. It allows developers to write MCP server configurations into project directories and automatically load them when a session starts.

Core Features

The plugin provides the following core capabilities:
* Project-Level MCP Auto-Loading: Create a configuration file in the project root directory to mount it automatically.
* Configuration File Support: Supports .dsh/mcp.yml, .dsh/mcp.（json）, and the read-only .mcp.json.
* Configuration Hot Reloading: After modifying configuration files, the DSH process automatically reloads them without requiring a restart.
* Tool Visibility Scoping: Tool visibility is isolated based on the current working directory (CWD) of the session.
* CLI Tool: Provides the dsh-mcp command-line tool for writing configurations.
* Multi-Level Configuration Sources: Supports multi-level configuration overrides.
* Official Communication: Uses the official @deepseek-ai/dsh-mcp-client for communication.

Installation and Enablement

The plugin is mounted via Bundle Patch. Make sure DSH is installed before installing it.

Prerequisites

  • Install DSH: npm install -g @deepseek-ai/dsh (or another source).

Installation Steps

Use the officially recommended command to install the latest version:

dsh plugin --profile web add dsh-project-mcp-manager@latest

Version Compatibility Notes

  • v0.7.x: Requires DSH version >= 0.2.0-rc.2.
  • v0.6.0: Use this version if you are using DSH 0.1.5.

Typical Usage

1. Create a Configuration File

Create a .dsh/mcp.yml file in the project root directory and add the MCP server configuration.

2. Use the CLI Tool

The plugin provides the dsh-mcp CLI tool to manage configurations.

Notes

  • No UI: The plugin only provides core functionality and has no graphical interface.
  • Configuration Mechanism: Official configuration is based on a profile-layer Cordis patch plus plugin_manager.
  • Transport Types: MCP transport types are determined by the official client; this plugin is not responsible for low-level transport.

Conclusion

The plugin simplifies managing MCP servers in multi-project scenarios through project-level configuration files and a hot-reloading mechanism. For more details, refer to the project documentation or source code.
GitHub Repository