Preface¶

When using multiple MCP servers in a DSH profile, common pain points are: scattered addition methods (manually writing configuration, copying JSON from other clients, testing connectivity one by one), no concept of scope (accidentally exposing tools with keys to all sessions), and inconsistent invocation methods (some tools go into the model’s tool list, others can only be called manually).

The AidenX0704/dsh-mcp introduced below (package name dsh-mcp-center-ui) brings these issues into a sidebar page: marketplace browsing, form or JSON import, effective by session/workspace/session scope, two invocation methods: auto and /mcp, and additionally provides a model-side mcp_manager tool.

What is this¶

One-sentence positioning: DSH’s MCP Management Center, a page to manage all MCP servers.

• Maintainer: AidenX0704
• Category: Workflow
• License: MIT
• Requirements: Node >=22, DSH >=0.2.0-rc
• Source: Listed in the community plugin directory skillhub.cn, no official affiliation with DeepSeek / Huanfang

One point that needs to be clarified first: The repository’s README title explicitly states Personal local build — not published to npm, and not meant for anyone else to install. In other words, the author uses the repository as a link: dependency for a local profile, and the fixes in v0.2.1 exist only in this repository and have not been pushed back to the registry. Please read the precautions below before installing.

Core Features¶

1. Sidebar entry mcp (sort order 40, located after Plugins / Automations / Skills Center), clicking opens the MCP Center page in the main column.

2. Three tabs:
   - Configured: A card for each server, showing status light, transport method, invocation method, command/address, number of tools, scope summary; inline actions to enable, edit, test, expand, and delete.
   - Marketplace: Built-in 19 curated real MCP servers, plus 1 offline demo server; supports category filtering, search, and requirement badges.
   - Invoke: Select server, select tool, fill JSON parameters, run and copy result, and provide /mcp cheat sheet.

3. Two addition methods. Manual form supports stdio and streamable-http, fields include command, args, env, URL, headers, timeout; JSON import recognizes Claude Desktop / Cursor’s mcpServers, VS Code’s servers, or single {command} / {url} objects, supports importing multiple at once, with preview before import.

4. Scope: Optional all sessions, specific workspace, specific session. The README explicitly states the consequence of going out of bounds is not “not recommended”: mcp__<server>__* tools will be removed from the session’s tool list, and list_mcp_resources / read_mcp_resource execution will also be rejected.

5. Invocation mode: auto puts tools into the model’s tool list; manual does not put them in, only callable via /mcp call, the Invoke console, or mcp_manager.

6. Model-side control: The mcp_manager tool provides list, tools, market, add, update, remove, toggle, test, call; the /mcp command operates on the same set of Host capabilities as the page actions.

Installation and Enabling¶

This plugin is a DSH bundle. The official documentation provides three installation methods, listed in order.

Method 1, Plugins page in Web GUI: Sidebar Plugins → install → paste repository address:

https://github.com/AidenX0704/dsh-mcp

After installation, press F5 to reload the page. Client modules are loaded when the page starts; the sidebar entry will not appear without reloading.

Method 2, Agent tool invocation, requires a session with danger-full-access:

{"action":"install_bundle","target":"https://github.com/AidenX0704/dsh-mcp"}

This invocation also accepts the shorthand github:AidenX0704/dsh-mcp.

Method 3, Fixed release tag, any git ref or commit can be used:

https://github.com/AidenX0704/dsh-mcp#v0.1.0

Regarding npm: The package name is dsh-mcp-center-ui (the bare name dsh-mcp-center on npm belongs to an unrelated project):

{"action":"install_bundle","target":"dsh-mcp-center-ui"}

However, the README also warns against installing dsh-mcp-center-ui@0.2.0 from the registry or a mirror and explains the reason: its client module registers the browser module using dsh-mcp-center, while the Host declares the boot-graph line using the package name dsh-mcp-center-ui. The unregistered line causes the loader to retry and execute the same file twice, throwing client-modules: duplicate factory registration, causing the Web GUI to fail directly with Failed to load plugins. This defect is only fixed in v0.2.1 of this repository.

Typical Usage¶

The following examples are from the official Quick start and can be fully reproduced.

1. After installing the bundle, press F5 to reload the page.
2. Open sidebar MCP → Marketplace.
3. Find Local demo server (id is demo, category Built in), it doesn’t need network, doesn’t need npx, doesn’t need credentials, click Quick add → Create.
4. Go back to Configured, the card turns green, containing 4 tools: echo, add, now, list_dir.
5. Switch to Invoke, select demo, select echo, set parameters to {"text":"hello"}, and press Run.

Similarly, this call can also be written directly in the input box:

/mcp call demo echo {"text":"hello"}

Common /mcp subcommands are as follows:

/mcp list
/mcp tools [server]
/mcp call <server> <tool> [json]
/mcp add <name> <json>
/mcp rm <server>
/mcp enable <server> / /mcp disable <server>
/mcp auto <server> / /mcp manual <server>
/mcp scope <server> <all|workspace|session> [ids…]
/mcp test <server> [tool] [json]
/mcp market [query]

Scope determination rules: all means always visible; workspaces means the session belongs to the selected workspace, or the working directory is located under the selected workspace path; sessions means the session id is in the selected list.

Suitable Scenarios and Notes¶

Suitable for: people who need to centrally manage multiple MCP servers in a single local DSH profile, need to isolate tool exposure scope by session/workspace, or want the model to manage servers via /mcp and mcp_manager.

A few notes:

1. The plugin runs with the permissions of the current DSH process. The installation, enablement, and invocation capabilities of /mcp are equivalent to what that process can do; please use it in a controlled environment.
2. Check the source code and license before installing. The license is MIT, and the source code is in the GitHub repository.
3. This is a personal local build, and the author has not declared it for public release. If you just want to experience the page layout, you can install and verify it first via Method 1 or Method 2; do not treat it as a product already maintained on the registry.
4. If you have already installed dsh-mcp-center-ui@0.2.0 from the registry or a mirror, the README suggests removing that version first and then switching to the current repository source code to avoid DSH failing to start.
5. Real servers in the Marketplace need to satisfy their respective requirement badges (e.g., API key, OAuth, Node/Python runtime, Docker, network access). The Quick add dialog is generated based on the fields of each entry, so it cannot be filled out if prerequisites are missing.

Closing¶

The value of dsh-mcp lies in turning the “MCP server list” into a management interface with scope, invocation modes, a market, and import paths. It is still a personal maintenance project, and the README explicitly states this, so when judging whether to adopt it, feature matching is more important than list ownership.

• Directory page: https://www.skillhub.cn/plugins/AidenX0704/dsh-mcp
• GitHub: https://github.com/AidenX0704/dsh-mcp