npm / mcp
DSH MCP Manager
by Nichts
Manage global MCP servers from the DSH Web settings page and connect them at runtime.
CAPABILITY INDEX
MCP
01Explore MCP DSH plugins for registering, connecting, monitoring, and managing Model Context Protocol servers and tools.
DSH CATEGORY GUIDE
How to choose MCP DSH plugins
MCP DSH plugins connect DeepSeek Harness with Model Context Protocol servers and the tools they expose. They can simplify server registration, connection lifecycle, status visibility, and configuration, especially when a setup uses multiple local or remote MCP services.
Where these plugins help
- Registering and managing MCP servers
- Monitoring connections and tool availability
- Coordinating local and remote tool providers
How to compare
Compare supported transports, startup and shutdown behavior, reconnect handling, authentication, per-server configuration, logs, and whether tools can be enabled selectively. A manager should make failures visible instead of leaving disconnected servers in an ambiguous state.
Before you install
Add one MCP server at a time, validate its tool list, and keep credentials outside committed configuration. Confirm how child processes are terminated and whether remote servers receive prompts, files, or other sensitive context.
FAQ / 02
Frequently asked questions
Do I need an MCP manager plugin?
A small setup may not. A manager becomes useful when several servers need independent configuration, status visibility, reconnection, or runtime enable and disable controls.
Are remote MCP servers trusted automatically?
They should not be. Review the operator, authentication method, exposed tools, and data sent over the connection. Limit each server to the capabilities required for its intended workflow.