Prerequisites are DSH ≥ 0.1.2-alpha.1, Node.js ≥ 18, and pnpm ≥ 9. This plugin is maintained by sojo-negai and aims to simplify the configuration and monitoring of MCP servers in DSH through a Web interface. It supports editing JSON configuration directly on the DSH Settings page, viewing connection status in real time, and automatically completing tool registration, without manually modifying files or restarting the application.

Core Features

  1. Graphical Management: Edit JSON configuration directly on the DSH Settings → ‘MCP Servers’ page, without manually modifying yml files.
  2. Real-time Status: Each server displays a status dot — 🟢 Connected / 🟡 Connecting (blinking) / ⚪ Disconnected or disabled.
  3. Independent Start/Stop: Each server supports the enabled toggle; disabling does not delete the configuration, it only stops the connection.
  4. Automatic Reconnection: After saving the configuration, the plugin automatically reconnects and re-registers tools without restarting DSH.
  5. Format Compatibility: Paste Claude Desktop-style mcpServers JSON directly to import the configuration.

Installation and Activation

After cloning the repository, run the following commands in the project root directory to build and install:

pnpm install && pnpm build
node scripts/install.mjs --profile web

After installation is complete, refresh dependencies and restart DSH to use it.

Usage Flow

  1. Start DSH and open the Web interface.
  2. Click ‘Settings’ in the sidebar, then switch the top tabs to ‘MCP Servers’.
  3. Click ‘Edit Config (JSON)’, paste or edit the server configuration, then click ‘Save’.

Configuration and Status Description

Supported Configuration Formats

The plugin supports three configuration shapes. The first one (object mapping) is recommended because it is compatible with Claude Desktop’s mcpServers configuration:

{
  "chrome-devtools": {
    "command": "cmd.exe",
    "args": ["/c", "npx", "-y", "chrome-devtools-mcp@latest"],
    "enabled": true
  }
}

Status Indicators

The dot before each server name in the list indicates real-time connection status:
* 🟢 Connected: Tools are registered and can be invoked by the Agent.
* 🟡 Connecting: Starting or handshaking (blinking status); the first cold start may take longer.
* ⚪ Not Connected: Connection failed. Check whether command and args are correct, or view the terminal logs.
* ⚪ Disabled: enabled: false; the configuration is retained but not connected.

Tool Registration Names

The server name defined in the configuration is used as a prefix. The tool registration name format is: mcp__<server name>__<tool name>.

Notes

  • Source Code Mode: If using source code mode for development, you need to manually create a cordis.yml patch file to attach the TS entry to the profile. This file is not committed to the repository.
  • Permissions: The plugin runs with the permissions of the current DSH process. Ensure the configured command paths and environment variables are available in the current environment.