Back to directory

dsh-mcp-panel

Curated pickMaintenance: Active

perrylink/dsh-mcp-panel

MCP management console for the official DeepSeek Harness MCP client: /mcp command with health diagnostics and pipeline trial calls, a Settings MCP tab with server CRUD (approval-gated writes, automatic backups) and a tool trial console over the official tool pipeline (Apache-2.0, dsh-plugin).

View on GitHubHomepage
$ dsh plugin --profile web add dsh-mcp-panel

72

stars

7

forks

TypeScript

Language

Apache-2.0

License

2026-08-14

Created

2026-09-25

Last push

A read-only, reversible MCP console layered on DeepSeek Harness's official MCP client — manage servers, diagnose health, and trial tools from a settings page, without hand-editing cordis.yml.

DSH integration

Native runtime

Author-claimed

Safety audit

Unaudited

Last verified

2026-09-01

License

Apache-2.0

01What can it help you accomplish?

  • Manage MCP servers (add, edit, remove, trial-call) from a settings page in DeepSeek Harness

    A Settings → Plugins → MCP console with per-server status cards, health diagnostics, server CRUD, and a tool trial console over the official tool pipeline

    DeepSeek Harness users running MCP servers who want a safe, reversible, GUI alternative to hand-editing cordis.yml

  • Diagnose failing MCP servers with derived self-heal suggestions

    `/mcp <server> health` output mapping errors (ENOENT, ECONNREFUSED, timeouts, 401/403/404, DNS, rate limit, reconnect exhaustion) to fixes, honestly labeled

    Operators debugging MCP connectivity inside DeepSeek Harness who need readable status without grepping logs

02How to install into DeepSeek Harness

Prerequisites

  • DeepSeek Harness `0.1.1-rc.2`–`0.2.0` installed (the `dsh` CLI)
  • Node.js `^22.19.0 || >=24.0.0`

Installation steps

  1. 01

    `dsh plugin --profile web add dsh-mcp-panel` — install the published npm release

    $ dsh plugin --profile web add dsh-mcp-panel

  2. 02

    `dsh plugin --profile web add "github:PerryLink/dsh-mcp-panel#main"` — install the latest `main`

    $ dsh plugin --profile web add "github:PerryLink/dsh-mcp-panel#main"

  3. 03

    Restart DeepSeek Harness, then open Settings → Plugins → MCP (or run `/mcp`)

Verify the integration

  • `dsh --profile web --dump-config | grep -A3 'id: mcp-panel'` — confirm the `mcp-panel` row is present
  • Run `/mcp` and confirm per-server status rows render

Rollback

  • Remove the `mcp-panel` row from `cordis.patch.yml` (the web surface hot-reloads it)
  • Delete the package from the profile's `node_modules`
  • Verify with `dsh web --dump-config` that no `mcp-panel` row remains

03DSH integration and capability boundaries

DSH integrationNative runtime

Native dsh-plugin: a cordis plugin that layers a console on the official @deepseek-ai/dsh-mcp-client bridge

  • Settings → Plugins → MCP console (server CRUD + tool trial)

    DeepSeek Harness web profile (cordis.patch.yml) with configured MCP servers→a settings UI for per-server status, health diagnostics, server CRUD, and panel-side tool trial calls

    append-only, approval-gated writes to `cordis.patch.yml` with automatic backups (never rewrites the file)
  • `/mcp` command suite (status / tools / health / call)

    MCP server name and optional JSON tool arguments→per-server status rows, `mcp__*` tool names, derived self-heal suggestions, and trial-call results via the official tool pipeline

  • Recommended MCP server directory & config import/export

    built-in community catalog (filesystem, git, github, fetch, playwright, …) and versioned JSON export documents→`catalogEntries` overlay for one-click add; `exportConfigs()` / `importPreview()` for safe config migration

04Who is it for? When not to use it?

Good for

  • DeepSeek Harness users running MCP servers who want a safe, reversible, GUI alternative to hand-editing cordis.yml
  • Operators debugging MCP connectivity inside DeepSeek Harness who need readable status without grepping logs

Not for

  • The official client bridges tools only; Resources and Prompts are pending upstream support, and the panel never fakes connection state (unobservable fields read `unknown` / `-1` / `—`).

05Compatibility, maintenance and safety notes

  • The official client bridges tools only; Resources and Prompts are pending upstream support, and the panel never fakes connection state (unobservable fields read `unknown` / `-1` / `—`).
  • Runs only on the DeepSeek Harness web profile (dual-face host + browser GUI); requires Node.js `^22.19.0 || >=24.0.0` and Harness `0.1.1-rc.2`–`0.2.0`.
  • Every profile write is append-only, approval-gated, and backed up (newest `backupCount` backups); `writeEnabled: false` rejects all writes while copy still works.
2026-08-142026-08-30v0.6.2

Apache-2.0 · maintained by PerryLink (one of 33 DeepSeek Harness plugins); latest release v0.6.2 (2026-08-30)

06Frequently asked questions

How do I install dsh-mcp-panel into DeepSeek Harness?

Run `dsh plugin --profile web add dsh-mcp-panel` for the published npm release, or `dsh plugin --profile web add "github:PerryLink/dsh-mcp-panel#main"` for the latest `main`. Then restart and open Settings → Plugins → MCP, or run `/mcp`.

Does it replace the official @deepseek-ai/dsh-mcp-client?

No. The official client is the only bridge (one row per MCP server in cordis.yml). dsh-mcp-panel is the experience layer on top: it reads status through the `mcp/status` seam and writes only append-only, approval-gated `cordis.patch.yml` fragments. Transport, OAuth, and protocol are never changed.

How does it diagnose failing MCP servers?

Run `/mcp <server> health`. The panel derives self-heal suggestions from sanitized error text (ENOENT → missing dependency, ECONNREFUSED, timeouts, 401/403/404, DNS, rate limit, reconnect exhaustion). Fields with no upstream observation read `unknown` / `—` — it never invents exit codes or stderr.

Is it safe to write profile changes?

Yes. Every write is append-only, approval-gated, and backed up (newest `backupCount` backups, default 5). The `writeEnabled` kill switch (`false`) rejects all writes while copy still works, and URL query credentials, bearer tokens, and JWTs are redacted before rendering.

What are the known limitations?

The official client bridges tools only, so Resources and Prompts are pending upstream support; the panel marks both as such rather than faking them. It runs on the DeepSeek Harness web profile and requires Node.js `^22.19.0 || >=24.0.0` and Harness `0.1.1-rc.2`–`0.2.0`.

08Data and sources

  • Author-claimedgithub.comcb98f2749845…

    The MCP management console for the official DeepSeek Harness MCP client — add, edit, remove, and trial-call MCP servers…

  • Author-claimedgithub.comcb98f2749845…

    Official client = bridge, this plugin = console: read status through the `mcp/status` seam, write only append-only, appr…

  • Author-claimedgithub.comcb98f2749845…

    ## PerryLink DSH Plugin Family

This page is generated from the project’s public documentation, repository metadata and a structured parse of DSH Plugins; last verified on 2026-09-01. Found an error? Submit a correction.

🏆

Best DeepSeek Harness Plugins

Twelve plugins worth installing first — picked from the whole catalog, across every category.

DSH Plugins is an independent community directory of DeepSeek Harness plugins. Not affiliated with or endorsed by DeepSeek. Third-party plugins are not security-audited — review the source before installing.

New DeepSeek Harness plugins, weekly. No spam.