Neplich/dsh_plugin--packages-feature-dsh-config-mcp ↗★ 1
@neplich/dsh-config-mcp
dsh Web GUI plugin: an MCP Servers settings section — list, add, edit, toggle, and delete MCP servers via the user-level cordis.patch.yml with live HMR reload 适合需要图形化管理 MCP 服务器的用户;写入用户级配置文件并保留注释,仅适用于 Web 配置。
Install
$
npx -p @deepseek-ai/dsh dsh plugin --profile web add github:Neplich/dsh_plugin#c83599509c2f790ba23c59b19d90e521fa774c1d&path:packages/feature/dsh-config-mcpREADME
Read the full README ↗@neplich/dsh-config-mcp
中文版 · English
dsh Web GUI plugin: adds an "MCP Servers" section to the settings panel for full management of MCP servers.
Features
- Live listing of all MCP servers (from Cordis Loader entries): connection state (running/connecting/failed/disabled), transport (stdio/http), command or address summary, registered tool count
- Add / edit / delete "managed" servers (written as
insertrows into~/.dsh/cordis.patch.yml; AST-level editing preserves comments and other rows) - Any server can be enabled / disabled (externally sourced servers via appended
{ id, disabled }override rows) - After saving, dsh's patch watch + HMR hot-reloads automatically (disconnect/reconnect) — no restart needed
- Supported fields: serverName, transport, command/args/env/cwd (stdio), url/headers (http), toolCallTimeoutMs, failOnStartupError
Internationalization
All UI copy (section title, navigation items, status labels, forms, buttons, hints) ships in zh and en through the config-mcp locale namespace and adapts live to the language set in dsh settings. Server-returned error messages stay in English (protocol-level neutral copy).
Install
dsh plugin --profile add @neplich/dsh-config-mcp
dsh web --profile # plugin-set changes require a restart
Available only in a dsh web profile (depends on ctx.webServer).
Config
| Field | Default | Description |
|---|---|---|
maxBodyBytes | 1048576 | JSON body cap for mutation requests |
Known Limitations
- The edit dialog does not support
!!jsexpression values (edit the patch file directly if needed) orreconnect.*fields - Renaming serverName requires delete + recreate (the tool namespace binds to the entry id)
- Edit/delete apply only to servers managed by the user-level patch file; servers provided by other layers can only be disabled