Back to search
dsh-small-mcp-server
MCP serverGitHub
DSH web plugin: manage MCP servers from the settings panel. View, edit, remove, enable, and disable MCP servers. Toggling a server applies on the spot — one click, no Save. Add / edit / remove are…
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Checked yesterday
Badge for your README
Markdown
[](/listings/liujianqiao701--dsh-small-mcp-server)HTML
<a href="/listings/liujianqiao701--dsh-small-mcp-server"><img src="/api/listings/liujianqiao701--dsh-small-mcp-server/badge.svg" alt="findsafeskills safety rating" /></a>Install
i
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
dsh plugin --profile web add dsh-small-mcp-server
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
README.md · README · 142 lines
- # dsh-small-mcp-server
- English | [中文](README.zh.md)
- DSH web plugin: **manage MCP servers from the settings panel**. View, edit, remove,
- enable, and disable MCP servers. **Toggling a server applies on the spot** — one
- click, no Save. Add / edit / remove are staged and hot-reload on **Save**. Either
- way nothing restarts the process, because each server is a live
- `@deepseek-ai/dsh-mcp-client` loader entry.
- > **DSH 0.2 only** (`>=0.2.1-rc.1 <0.3.0-0`; verified on `0.2.2-rc.3`).
- > See [PORTING.md](./PORTING.md) for the incompatibilities the older 0.1.x code
- > had to fix in order to load on 0.2, and the 0.2.2-rc.3 adaptation.
- > **Author:** liujianqiao701 ([github.com/liujianqiao701](https://github.com/liujianqiao701)).
- > Based on an anonymous MIT-licensed v0.1.x upstream; this fork ported it to DSH 0.2
- > and reworked the settings page. Attribution is kept in [LICENSE](./LICENSE) and
- > [PORTING.md](./PORTING.md).
- ## What this fork changes
- Ported to DSH 0.2 and then reworked, so it is not a drop-in copy of upstream:
- - **Toggling no longer commits your other drafts.** `mcp/save` is a whole-table
- reconcile, and upstream sent the entire draft table on every toggle — so
- clicking one switch silently saved every other pending edit. A toggle now
- submits the saved table plus that one flipped row, and leaves every other
- draft untouched.
- - **Each in-flight phase has its own badge.** `pending`, `loading` and
- `unloading` used to collapse into one "Loading" label, which made a queued row
- and a tearing-down row look identical to a starting one.
- - **Unsaved rows say so.** A row that differs from what is on disk shows an
- "Unsaved" badge instead of a blank slot.
- - **Editing an unsaved row keeps its content.** Opening a newly added, not-yet-saved
- server for editing used to fall back to a blank "new server" form and drop what
- you had typed; it now edits the draft row.
- - **The hot-reload window is explained.** Save shows what is happening during the
- 1–4 s restart instead of appearing frozen, and a partial failure says that
- earlier entries may already be live (`save` is reconcile, not a transaction).
- ## What it does
- - **View** — lists every configured MCP server with its `serverName`, transport
- (stdio / Streamable HTTP), command or URL, and live state (enabled / disabled,
- plus the connection phase: `active`, `failed`, `loading`, …).
- - **Add / Edit** — full editor for a server: `serverName`, transport, `command`
- - `args` + `cwd` + `env` (stdio), or `url` + `headers` (HTTP), plus the
- per-call timeout and the `failOnStartupError` flag.
- - **Remove** — deletes the server's loader entry (with a confirm prompt).
- - **Enable / Disable** — toggles the entry's `disabled` flag without touching
- its config, so a disabled server keeps its full configuration. **Applies
- immediately on click** (it calls `mcp/save` for you) — no **Save** step.
- - **Save → hot reload** — add / edit / remove are staged locally; **Save** reconciles the
- loader tree (`create` / `update` / `remove`), then writes the server set back
- to the profile's `cordis.patch.yml` (the durable patch layer). Each operation
- restarts only the affected `dsh-mcp-client` instance, which is the same
- hot-swap the harness HMR performs.
- ## Architecture
- A dual-face npm package installed into the `web` profile:
- | Half | Entry | Role |
- | -------- | --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
- | Server | `lib/index.js` | Cordis plugin (`inject: ["loader"]`): mounts the `ctx.mcp` typert service that projects and reconciles the loader's `@deepseek-ai/dsh-mcp-client` entries. |
- | Protocol | `lib/typert.js` | Host TYPERT face (`mcp/list`, `mcp/save`), auto-registered by `dsh-typert-loader`. |
- | Browser | `lib/client.js` | React page mounted into the `settings.section` slot; calls the host through the installed `remote.mcp` namespace. |
- The client↔server channel is the DSH typert protocol: strict zod codecs validate
- every argument and result on both sides.
- ## Install
- ```sh
- dsh plugin --profile web add dsh-small-mcp-server
- ```
- ## How it maps to `cordis.patch.yml`
- The plugin manages the `dsh-mcp-client` rows in the profile's `cordis.patch.yml`
- (the user patch layer — **not** `cordis.yml`, which the launcher resets to an
- empty list on every boot). A stdio server is the same as:
- ```yaml
- # cordis.patch.yml
- - insert:
- - id: mcp-github
- name: "@deepseek-ai/dsh-mcp-client"
- config:
- serverName: github
- transport: stdio
- command: npx
- args: ["-y", "@modelcontextprotocol/server-github"]
- env:
- GITHUB_TOKEN: ...
- ```
- and a Streamable HTTP server is the same as:
- ```yaml
- # cordis.patch.yml
- - insert:
- - id: mcp-web
- name: "@deepseek-ai/dsh-mcp-client"
- config:
- serverName: web
- transport: streamable-http
- url: http://localhost:3000/mcp
- headers:
- Authorization: ...
- ```
- The tool names the model sees stay server-qualified (`mcp__<serverName>__<tool>`),
- exactly as with hand-written entries.
- ## Development
- This package ships **built output only** — the original TypeScript sources,
- `tsconfig` and bundler config were never part of the published npm tarball, so
- there is no build step here. Edit `lib/*.js` directly (it is unminified and
- comment-preserving). To check a change:
- ```sh
- npm install --legacy-peer-deps --no-package-lock # zod + js-yaml
- node --check lib/index.js
- ```
- Runtime deps (`zod`, `js-yaml`) are declared in `dependencies` rather than
- `peerDependencies`: DSH profiles run with `autoInstallPeers: false`, so a peer
- would not be installed and the host half would fail to import.
- ## Known limitations
- - **`reconnect` is not surfaced by the editor.** A disabled/enabled toggle and
- edits to other servers keep the stored `reconnect` block; the editor itself
- cannot view or change it.
- - **Advanced `reconnect` fields and future MCP capabilities** (resources,
- prompts) are out of scope for this panel; they remain configurable directly in
- `cordis.patch.yml`.
- - **Save is a reconcile, not a transaction.** Operations apply sequentially; if
- a later entry fails (e.g. the server process can't start), earlier operations
- are already applied and the failure is reported in the panel.
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.