Introduction¶

DSH’s philosophy is “everything is a plugin,” and plugins are typically used to extend the capabilities of DeepSeek Harness. For agents that collaborate with external systems only through MCP, directly searching, inspecting, installing, and running DSH plugins would lack a standard interface layer.

Here we introduce bobleer/deepseek-harness-plugin-mcp. It is an MIT-licensed MCP server designed to allow any agent to discover, inspect, install, and run DeepSeek Harness plugins.

What This Is¶

deepseek-harness-plugin-mcp is an MCP server hosted at bobleer/deepseek-harness-plugin-mcp. The maintainer information in the verified sources is inconsistent: repository clues point to bobleer, while the README states Made by BitFun. Therefore, this article does not establish a definitive relationship between the two.

It splits DSH plugin capabilities into three planes:

• Catalog: Discover, list, and inspect public dsh-plugin repositories, and read READMEs and cordis.patch.yml files.
• Profile: Execute dsh plugin add / remove on real profiles when dsh is on PATH and --allow-install is enabled.
• Runtime: Start profiles and expose DSH tools as dsh__* when dsh is on PATH and --allow-runtime is enabled.

It provides two categories of MCP tools, dsh_plugin_* and dsh_runtime_*, while also exposing dsh-plugin:// resources and the search-dsh-plugins, install-dsh-plugin, and use-dsh-plugin prompts.

By default, the Catalog plane is always available; the Profile and Runtime planes remain disabled until explicitly enabled.

Core Features¶

Catalog¶

The Catalog allows agents to first learn about installable objects. It can search, list, and inspect public dsh-plugin repositories, and read READMEs and cordis.patch.yml files from them.

This step does not require dsh to be installed locally and does not execute plugin code.

Profile¶

The Profile plane is used to add plugins to real DSH profiles. When dsh is on PATH and the server is started with --allow-install, agents can execute dsh plugin add / remove.

This step modifies the plugin list in the local profile and is considered an installation-type operation.

Runtime¶

The Runtime plane is used to start a profile and bridge the DSH tools exposed within it as MCP tools. When dsh is on PATH and the server is started with --allow-runtime, agents can use dsh_runtime_* to start, stop, and load profiles, then invoke tools in the form of dsh__*.

The Runtime path spawns DSH and runs plugin code, so plugin source code and licenses should be inspected before installation and activation.

UI/TUI/skin Plugins¶

UI, TUI, and skin type plugins can be cataloged and installed, but they do not become MCP tools. The interfaces of such plugins remain within DSH.

Installation and Activation¶

Basic Installation¶

First, install the global command. The verified installation command is:

npm install -g deepseek-harness-plugin-mcp

You can also directly view the help:

npx deepseek-harness-plugin-mcp --help

The Node engine requirement is:

^22.19.0 || >=24.0.0

stdio Integration¶

For stdio integration, use the following command:

npx -y deepseek-harness-plugin-mcp

If GitHub API authentication is needed, you can set an optional environment variable:

GITHUB_TOKEN

GITHUB_TOKEN / GH_TOKEN are optional but recommended.

Enabling Profile and Runtime¶

If the agent needs to install plugins or start the Runtime, first confirm that dsh is on PATH, then start:

npx -y deepseek-harness-plugin-mcp --allow-install --allow-runtime

Also set the target profile:

DSH_PLUGIN_MCP_PROFILE

This executes dsh plugin related actions and spawns DSH and runs plugin code in the Runtime path. This should be treated as a permission-sensitive operation; inspect plugin source code and licenses before enabling.

Streamable HTTP¶

When using HTTP, first start the service:

dsh-plugin-mcp --http --port 8765 --allow-runtime

Then point the agent to:

http://127.0.0.1:8765/mcp

Using Within DSH¶

This package can itself be added to a profile as a DSH bundle. The example below uses the web profile:

dsh plugin --profile web add github:bobleer/deepseek-harness-plugin-mcp
dsh --profile web

After these steps, DSH will load this bundle. The specific tools available will depend on the DSH and plugin registration results after startup.

Typical Usage¶

Agents typically work in the following order:

1. Use dsh_plugin_search to search for plugins by task keywords.
2. Use dsh_plugin_inspect to inspect the owner/repo of candidate plugins.
3. If needed, use dsh_plugin_install to install a plugin.
4. Use dsh_runtime_start to start the profile.
5. Invoke the exposed dsh__* tools.

Both the installation and Runtime steps depend on local dsh availability and require the corresponding server-side switches to be enabled.

Applicable Scenarios and Notes¶

• Suitable for developers who need agents to discover, inspect, install, or run DSH plugins.
• The Catalog plane is available by default; the Profile and Runtime planes are disabled by default and require explicit enabling.
• The Profile and Runtime planes require dsh to be on PATH.
• GITHUB_TOKEN / GH_TOKEN are optional but recommended for GitHub API authentication.
• UI/TUI/skin plugins can be cataloged and installed but do not become MCP tools; their interfaces remain within DSH.
• The Runtime path spawns DSH and runs plugin code. Inspect source code and licenses before installing plugins.
• The Node engine requirement is ^22.19.0 || >=24.0.0.
• This project is MIT-licensed.
• It targets public dsh-plugin repositories and should not be described as an official DeepSeek app store, nor does it represent an official affiliation between DeepSeek / High-Flyer and this catalog.
• The verified sources do not provide a confirmable directory page URL, so this article does not list a directory page address.

Conclusion¶

The value of bobleer/deepseek-harness-plugin-mcp lies in integrating DSH plugin discovery, inspection, and running capabilities with MCP, allowing agents to handle plugins through a unified interface. It remains conservative by default: Catalog is available, while installation and runtime require explicit enabling, and a working local dsh must be present.

GitHub:

https://github.com/bobleer/deepseek-harness-plugin-mcp