Introduction¶
DeepSeek Harness (DSH) allows agents to invoke external tools via MCP (Model Context Protocol). However, in real-world development, you often need different MCP servers for different sessions (for example: one session connected to a database and another connected to a code repository). Manually managing global and project-level configurations can easily lead to conflicts and does not allow flexible control over the tools available in an individual session. dsh-mcp-master solves this problem by pushing MCP server management down to the session level and providing a unified entry point for project and global configurations.
Plugin Overview¶
dsh-mcp-master is a workflow plugin for DeepSeek Harness. It is maintained by user lastorder. It provides DSH with an MCP server selector located in the Composer line, supports loading server lists from global and project directories, and offers OAuth authentication support and a trust review mechanism for project servers.
Core Features¶
- Session-level selector: Displays
[🔌 MCP 2 ●]in the Composer line of each session. Click it to view and select the servers enabled in the current session. - Multi-directory management: Supports reading the global configuration
~/.dsh/mcp-master/mcp.jsonand project-level configurations (.mcp.json,.cursor/mcp.json,.vscode/mcp.json,.dsh/mcp.json). - Trust review: MCP servers in a project must be trusted before they can run. If a server is marked as “untrusted,” it displays the specific command/URL and provides a “Trust & use” button.
- OAuth authentication: Supports the MCP authorization specification and can use an OAuth provider to dynamically register a client for signing. Tokens are stored in
~/.dsh/mcp-master/state.. - Variable resolution: Supports environment variable resolution such as
${VAR}and${workspaceFolder}. - Transport protocols: Supports stdio, Streamable HTTP, and legacy HTTP.
Installation and Activation¶
The plugin is installed through DSH’s plugin directory. After installation, it generates the cordis.patch.yml configuration file to inject the Host and Client modules.
After installation, DSH must be restarted for the changes to take effect.
Typical Usage¶
- Configure servers: Create
.mcp.jsonin the project root directory, or writemcpServersconfiguration in the global directory~/.dsh/mcp-master/mcp.json. The configuration format follows the MCP standardmcpServersobject. - Create a session: Open a new session. An indicator for the number of MCP servers appears in the Composer line.
- Trust project servers: If this is the first time running a server in the project, click the status dot or the “Trust & use” button in the line to authorize it.
- Switch session servers: During session runtime, click the MCP indicator in the Composer line at any time and select or deselect servers to register/unregister the corresponding tools in the current session.
Applicable Scenarios and Notes¶
- Applicable scenarios: DSH users who need to switch between different external toolchains across sessions; developers managing multi-project environment variables.
- Note: Project servers must be trusted before they can run. OAuth tokens are stored in
~/.dsh/mcp-master/state.and should be treated as sensitive credential files. Logs and the UI automatically redact code, tokens, and Bearer values. Server processes stop 2 minutes after a session ends, and workspaces with no sessions close after 15 minutes of idle time. - Security: The plugin runs with the permissions of the current DSH process. Please review the source code and license before installation.
Ecosystem Context¶
The DSH philosophy is “everything is a plugin.” This plugin is included from a community directory and has no official affiliation with DeepSeek or High-Flyer.
