bobleer/deepseek-harness-plugin-mcp

MCP server that lets any agent discover, install, and run DeepSeek Harness plugins (topic: dsh-plugin).

About deepseek-harness-plugin-mcp

MCP server that lets any agent discover, inspect, install, and run DeepSeek Harness plugins.

Catalog source: github.com/topics/dsh-plugin.

DSH plugins are Cordis bundles (dsh.bundle.patch → cordis.patch.yml). Foreign agents speak MCP, not Cordis. This server is the inverse of @deepseek-ai/dsh-mcp-client:

Plane Needs DSH? What the agent can do --------- Catalog No Search/list/inspect every public dsh-plugin repo, read README and cordis.patch.yml Profile dsh on PATH dsh plugin add / remove into a real profile Runtime dsh on PATH + --allow-runtime Boot that profile and call composition tools as dsh

UI/TUI/skin plugins are catalogued and installable. They do not become MCP tools; their UI stays in DSH.

Cursor / Claude Desktop / Claude Code / Codex (stdio)

Enable install and runtime (this runs dsh plugin and plugin code):

dsh must be on PATH for the profile and runtime planes.

Point the agent at http://127.0.0.1:8765/mcp. GET /health is a process liveness check.

The live Harness then serves Streamable HTTP MCP (default http://127.0.0.1:8765/mcp) and mirrors ctx.tools — every first-party and third-party tool the composition registered.

- dshpluginstatus / dshpluginrefreshcatalog / dshpluginlist / dshpluginsearch - dshpluginget / dshplugininspect / dshpluginreadme - dshpluginlistinstalled / dshplugininstall / dshpluginuninstall - dshruntimestart / dshruntimestop / dshruntimeload / dshruntimeunload / dshruntimelisttools

From the project README.

Maintaining this server?

Add the radar badge to your README — it shows your project was picked up by MCP Radar and links to this page:

[![On MCP Radar](https://mcp.liqiwa.com/badge.svg)](https://mcp.liqiwa.com/s/bobleer--deepseek-harness-plugin-mcp.html)

Related MCP servers