Introduction¶
DeepSeek Harness (DSH) natively supports capabilities such as file read/write and bash execution, so MCP plugins for the local file system have limited value. The core value of MCP lies in connecting external services such as GitHub, Slack, Postgres, or various SaaS products. However, maintaining a static server list cannot keep up with the pace of ecosystem development, and manually writing the cordis.patch.yml configuration is cumbersome.
dsh-mcp-manager is a DSH plugin designed to solve these problems. It provides a unified page for managing all MCP servers, supports searching from live registries and npm, offers card-based one-click installation, and allows custom STDIO and streaming HTTP integration.
Core Features¶
Live Directory Browsing¶
The plugin does not include a static list; instead, it queries upstream data sources directly:
* Official MCP Registry: Provides search and pagination, and displays the source and transport method (HTTP or npm) for each entry.
* npm registry: Supplements packages that have not yet been included in the official registry, and displays monthly download counts and quality scores.
* Offline fallback: When both sources are unreachable, it falls back to built-in zero-config seeds and explicitly marks the service as unavailable.
Direct Query by Package Name¶
Some packages are not included in the official registry or do not contain the search keywords in their descriptions, making them unsearchable. The plugin supports entering @scope/name directly to query npm and auto-infer the launch command from the package’s bin field.
Server Management¶
- Card list: Displays connection status and transport method, and supports toggling, editing, and deleting servers.
- In-place editing: After modifying parameters or environment variables, saving takes effect immediately without restarting the process.
- Read-only protection: Servers manually written to
cordis.patch.yml(such asobscura) are marked as external configurations to prevent accidental modification by the plugin.
Custom Integration¶
Supports manually adding servers of type STDIO or streaming HTTP, with fields for launch command, arguments, environment variables, and request headers.
Slash Invocation¶
After installation, servers automatically appear in the / list. Entering /name task directly triggers the corresponding MCP tool. Three syntaxes are supported: /name, //name, and /@scope/name.
Installation and Enablement¶
- In the DSH left sidebar, go to the Plugins page.
- Click + Add Plugin in the upper-right corner.
- Paste the repository URL into the input field:
https://github.com/JokerAn/dsh-mcp-manager
- Click Install.
After installation, you must completely quit and reopen DSH before the plugin appears under Settings → Built-in Plugins → MCP.
Usage¶
Installing from the Public Directory¶
Switch to the “Public MCP Directory” and search. For servers that require no credentials, click “One-Click Install”. For servers that require a token (such as GitHub), a form appears after installation.
Installing an npm Package¶
Switch to the npm source or enter a package name directly (such as @scope/name), then click the “Direct Install” card. The command is automatically inferred from the package’s bin field.
Custom Server¶
Click + Add, choose the STDIO or streaming HTTP type, fill in the configuration, and save.
Using Tools¶
Tools from installed servers are registered to the model in the format mcp__<name>__<tool>, and can be used without restarting.
Notes¶
- Display name: Server names may have restrictions due to naming rules and may not display Chinese characters. The plugin supports setting a separate display name; this name is stored locally only and does not affect the server configuration.
- Permissions and security: The plugin runs with the permissions of the current DSH process. Please ensure you review the source code and license before installing.
Summary¶
dsh-mcp-manager solves the difficulty of MCP discovery through live registries and npm search, and solves the complexity of configuration through card-based management and custom integration. After installation, configurations can be adjusted dynamically without restarting, making it suitable for developers who need to quickly connect and extend external services in DSH.
