In the DeepSeek Harness (DSH) plugin ecosystem, connecting external tools via the Model Context Protocol (MCP) is an important way to extend agent capabilities. Managing MCP server configurations in a CLI environment is relatively straightforward, but Web interfaces often lack an intuitive management entry point. Below is an introduction to a visual management plugin for dynamically managing MCP services in the DSH Web interface.

Plugin Introduction

dsh-plugin-mcp-connector is a visual MCP protocol management plugin for DeepSeek Harness, maintained by developer gxinxing, under the MIT license. The core problem it solves is: under a DSH Web Profile, how to add, remove, enable, or disable MCP servers through a graphical interface, and how to view tool invocation status.

Core Features

The plugin mainly provides the following capabilities:

  • Visual Panel: Access the management page at the /mcp path in the DSH Web GUI.
  • Dynamic Management: Supports adding, removing, enabling, disabling, and restarting MCP services.
  • Automatic Tool Registration: After a service starts, its defined MCP tools are automatically registered to DSH for use by the conversation system.
  • Invocation Logs: Captures MCP tool call parameters and return results for easier debugging.
  • Persistent Configuration: The service list is stored in ~/.dsh/mcp-servers.json, so the configuration remains valid after a restart.

Installation and Enabling

Installing the plugin requires a Node.js environment and a DSH Web Profile.

  1. Enter the plugin directory.
  2. Install dependencies and build.
  3. Install to the DSH Profile.
  4. Restart DSH and access the panel.
# 1. 安装依赖
pnpm install

# 2. 构建
pnpm build

# 3. 安装到 DSH Profile
dsh plugin --profile web add .

# 4. 启动 DSH Web
dsh --profile web

# 5. 浏览器访问管理面板
# http://127.0.0.1:3080/mcp

Typical Usage

When configuring an MCP service, note the following rules:

  • Transport Mode: Supports three modes: stdio (local subprocess communication), sse (Server-Sent Events), and streamable-http.
  • Tool Naming: Each MCP tool’s public name in DSH follows the mcp__<serverName>__<rawToolName> pattern.

Use Cases and Notes

This plugin is suitable for developers who need to frequently adjust MCP service configurations or debug tool invocation logic.

Note: The plugin runs with the permissions of the current dsh process. Ensure that you are familiar with the plugin source code and license before installing it.

Summary

With this plugin, DSH users can manage the full lifecycle of MCP services in the Web interface without manually editing configuration files. Refer to the plugin directory or GitHub repository for more details.