Introduction

DeepSeek Harness uses a plugin-based architecture. To use Model Context Protocol (MCP) servers, developers often need to configure them manually or write scripts. meltartica/dsh-mcp-servers is a DSH plugin that exposes MCP servers as native tools and provides a configuration UI, real-time status monitoring, automatic reconnection, and backup/restore via local files or WebDAV.

Core Features

This plugin integrates client-side functionality for connecting to and managing MCP servers. Its key features are as follows:

  • Multi-transport support: Supports stdio, streamable http, and legacy SSE transports, configured through a unified endpoint field in the UI.
  • Automatic tool registration: Tools are automatically registered in the mcp__<serverId>__<toolName> format, following the official MCP client naming convention.
  • Status monitoring and reconnection: Provides real-time status indicators (green for connected, red for failed) and automatically attempts to reconnect when a connection drops (with backoff).
  • Test and edit: Each server card includes a Test button to probe the connection and tool list, and supports editing commands, arguments, environment variables, or HTTP headers.
  • Backup and restore: Provides local JSON export/import and WebDAV synchronization (supports HTTPS and Basic Auth, with optional daily automatic backup).

Installation and Enablement

Use the DeepSeek Harness CLI to install:

dsh plugin --profile <name> add ./dsh-mcp-servers
dsh --profile <name>

After installation, start Harness and go to the MCP Servers tab in the Settings menu.

Typical Configuration Examples

Add a server in the settings interface, click Test to verify the connection, and then click Save to save it.

1. Configure a Stdio Server

Suitable for locally running Node.js processes.

  • Type: stdio
  • Command: npx
  • Command Args: -y and @modelcontextprotocol/server-everything (one argument per line)
  • Env: Key-value pairs, for example API_KEY / your_token

2. Configure an HTTP/SSE Server

Suitable for remote APIs.

  • Type: http or sse
  • URL: https://example.com/mcp
  • Headers: Key-value pairs, for example Authorization / Bearer ...

3. Backup and Restore

In the Backup & Restore tab, you can export the current server list to a JSON file or import it for restoration when needed. Cloud synchronization via WebDAV is supported, with an optional automatic backup daily at 12:00 PM.

Notes

  • Schema limitations: Tool input schemas are filtered through a whitelist, retaining only the JSON Schema subset supported by Harness. Unsupported keywords (such as minLength, format, anyOf, etc.) are discarded.
  • Rendering: Results returned by MCP are rendered as text; image or resource blocks are collapsed into JSON or text and are not displayed as rich text blocks.
  • WebDAV limitations: WebDAV supports HTTPS endpoints only; credentials must not be included in the URL and must be entered separately; the sync route is limited to loopback access.
  • Runtime permissions: The plugin runs with the permissions of the current DSH process; it is recommended to review the source code and license before installation.

Conclusion

This plugin simplifies the process of integrating MCP servers into DeepSeek Harness and provides full lifecycle management capabilities. For more details and the source code, please visit the GitHub repository.