bobleer/deepseek-harness-plugin-mcp
MCP server that lets any agent discover, install, and run DeepSeek Harness plugins (topic: dsh-plugin).
An MCP server that lets any agent discover, inspect, install and run DeepSeek Harness plugins, described in the README as the inverse of @deepseek-ai/dsh-mcp-client. It separates three planes: the catalog (no DSH needed — search, list and inspect every public dsh-plugin repository, reading README and cordis.patch.yml), the profile (dsh on PATH — dsh plugin add / remove into a real profile) and the runtime (dsh on PATH plus --allow-runtime — boot a profile and call its composition tools as dsh__*). Control-plane tools cover status, catalog refresh, list/search/get/inspect/readme, installed-plugin listing, install/uninstall and runtime start/stop/load/unload/list-tools, with resources such as dsh-plugin://catalog and dsh-plugin://github/{owner}/{repo} and prompts like search-dsh-plugins and install-dsh-plugin. UI/TUI/skin plugins are catalogued and installable but do not become MCP tools.
Install
dsh plugin --profile web add github:bobleer/deepseek-harness-plugin-mcpREADME documents this DSH-bundle form: add the package to the web profile and start the profile; the live harness then serves Streamable HTTP MCP at http://127.0.0.1:8765/mcp and mirrors ctx.tools. The README also documents a global CLI form — npm install -g deepseek-harness-plugin-mcp or npx deepseek-harness-plugin-mcp --help (Node ^22.19 || >=24) — but a registry check on 2026-09-12 returned 404 for deepseek-harness-plugin-mcp, so verify publication before relying on the CLI form. Agents are wired through an mcpServers entry (Cursor / Claude Desktop / Claude Code / Codex stdio) using npx -y deepseek-harness-plugin-mcp; install and runtime planes stay off until you add --allow-install and --allow-runtime. Streamable HTTP runs with dsh-plugin-mcp --http --port 8765 --allow-runtime.
Compatibility
Node ^22.19 || >=24. dsh must be on PATH for the profile and runtime planes; the catalog plane needs only GitHub access (optional GITHUB_TOKEN). Node 22+ for the DSH bundle path.
Details
- Repo: bobleer/deepseek-harness-plugin-mcp
- Category: Agent Capabilities
- Stars: 3
- Version: GitHub install; the npm name deepseek-harness-plugin-mcp returned 404 on registry.npmjs.org on 2026-09-12
- Last push: 2026-08-13
- First seen: 2026-08-13
Recent updates
The README tables the flag and environment surface — --http, --host, --port, --allow-install, --allow-runtime, --profile, --dsh-root, --cache-dir, --no-catalog — with install and runtime off by default and the catalog always available. It also documents a protocol smoke test using the official MCP Inspector CLI and a typical agent flow of search → inspect (preferring isDshBundle: true) → install → runtime start → call dsh__* tools.
FAQ
- How do I install DeepSeek Harness Plugin MCP?
- As a DSH bundle: dsh plugin --profile web add github:bobleer/deepseek-harness-plugin-mcp. The README also documents npm install -g deepseek-harness-plugin-mcp, but that name returned 404 on registry.npmjs.org on 2026-09-12 — verify it is published before using the CLI form.
- Does it need dsh installed to browse plugins?
- No. The catalog plane works without DSH — it searches, lists and inspects public dsh-plugin repositories directly. The profile and runtime planes (installing into a profile, booting it and calling tools) do require dsh on PATH, and the runtime plane additionally needs --allow-runtime.
- Will it install or run plugins without asking?
- No — install and runtime are off until you explicitly opt in with --allow-install and/or --allow-runtime. The README states catalog access is always available while those two planes stay disabled by default.