Introduction¶

If you maintain a set of MCP (Model Context Protocol) servers locally, the tools are always available, but when switching to the DSH web environment, these tools cannot be directly called by the model by default. The common practice is to manually migrate configurations and rewrite the access logic. dsh-mcp-sync turns this process into a plugin: it scans local MCP configurations, connects to MCP servers, and registers the discovered tools for direct model invocation.

Below is an introduction to its positioning, features, and installation methods.

What is it¶

dsh-mcp-sync is a DSH (DeepSeek Harness) plugin maintained by nan1010082085 and licensed under MIT. One-sentence positioning: scan local MCP configurations, connect to MCP servers, register tools for direct model invocation, and includes built-in retry logic and statistics.

Background information: The README of this GitHub repository is currently organized as a dsh-plugins monorepo, containing three plugin packages: chat-sync, ima-sync, and mcp-sync, with mcp-sync being one of them; the repository itself corresponds to the dsh-mcp-sync declared in package.json.

Core Features¶

According to the README and package.json descriptions, the plugin performs four main tasks:

Scan local MCP configurations;
Connect to MCP servers and discover tools;
Register tools for direct model invocation;
Built-in retry logic and statistics.

Several technical details:

Runtime dependencies @modelcontextprotocol/sdk ^1.0.0 and @deepseek-ai/schemastery ^3.18.0;
package.json declares dsh.client.platform as web, with client-side injection of @deepseek-ai/dsh-client-runtime, @deepseek-ai/dsh-client-locale, @deepseek-ai/dsh-client-ui-settings;
Keywords include claude-code, codex, cursor, model-context-protocol, mcp-client, tool-registration.

Installation and Usage¶

The installation command uniformly includes --profile web, corresponding to the declared web platform inside the package. The three methods are as follows:

# GitHub install (recommended, independent repo, version sync)
dsh plugin --profile web add github:nan1010082085/dsh-mcp-sync

# npm install
dsh plugin --profile web add dsh-mcp-sync

# local link install (take effect after modifying source code and restarting dsh web)
dsh plugin --profile web add link:$(pwd)/packages/mcp-sync

The first line installs from the GitHub independent repository; the README recommends this method as versions sync with releases. The second line uses npm. The third line is for debugging, provided that the local dsh-plugins monorepo has been checked out and the packages/mcp-sync directory is linked; modifying the source code and restarting dsh web will take effect. After the steps above, the plugin is installed into the web profile.

Development and Publishing¶

This section is intended for those who wish to modify code or participate in maintenance. After modifying the source code, you can perform a syntax check first:

node --check packages/mcp-sync/lib/*.js

Under the monorepo structure, each package has an independent version release: enter packages/<plugin> and execute npm publish; after publishing, you must execute ./scripts/sync-repos.sh to sync the package to the independent GitHub repository. This supports full synchronization or synchronization by package name (e.g., ./scripts/sync-repos.sh ima-sync). Ordinary users installing the plugin do not involve these steps.

Suitable Scenarios and Notes¶

Who is it suitable for? Developers who already have local MCP configurations and servers and want these tools to be directly available in the DSH web profile without having to rewrite the access code.

Notes before use:

The plugin runs with the permissions of the current dsh process and will scan local configurations and connect to MCP servers. It is recommended to read the source code once before installation to confirm that the behavior matches expectations; the license is MIT, and the packages share the same source.
The installation command includes --profile web, and the package declares dsh.client.platform as web, targeting usage within the web profile.
Regarding version numbers: as of the time of writing this article (2026-09-07), the README in available materials lists the version as 0.7.0, while package.json lists it as 0.7.1. The two versions are inconsistent, and the actual release in the repository takes precedence.

Summary¶

dsh-mcp-sync solves a specific problem: transforming “local MCP tools” into “tools that can be directly called by the model in DSH”. It completes scanning, connection, and registration in one step, accompanied by retry and statistics. If you already have an existing MCP environment, you can simply install and reuse it.

GitHub repository: https://github.com/nan1010082085/dsh-mcp-sync
Community plugin directory entry: https://www.skillhub.cn/plugins/nan1010082085/dsh-mcp-sync (Community site, independently operated, with no official affiliation with DeepSeek / Huanfang)

dsh-mcp-sync: Scan local MCP configurations and register tools for direct model invocation.