dsh-mcp-connect

🔧 Configuration

Servers are a JSON array. Each entry is either stdio or url:

{
  "id": "my-server",                // tool prefix: mcp__
  "command": "npx",                 // executable (stdio only)
  "args": ["-y", "server-pkg"],     // argv after the executable
  "cwd": "/abs/path",               // optional working directory
  "env": { "KEY": "value" },        // optional environment
  "url": "https://x.example/mcp",   // or: remote HTTP/SSE via mcp-remote
  "disabled": false,                // keep configured but inactive
  "allowTools": ["search_*"],       // optional: register only these tools
  "denyTools": ["delete_*"],        // optional: hide these tools
  "timeoutMs": 120000               // optional per-server call timeout
}

Field	Type	Meaning
id	string, required	tool prefix — tools become mcp__
command + args	string + string[]	stdio server executable and its argv
url	string	remote server (HTTP/SSE, bridged through mcp-remote)
cwd	string	working directory (default: the process cwd)
env	object	extra environment variables
disabled	boolean	listed in mcp_status but never connected or validated
allowTools / denyTools	string[]	exact-name filters, combinable — hide destructive tools
timeoutMs	number	per-server call timeout in ms (default 120000)

Set the array through DSH_MCP_SERVERS (JSON), or edit the defaults in resolveServers() inside plugin.js. Ready-made examples: examples/servers.json — filesystem, GitHub, fetch, memory, Postgres, remote.

🔧 配置

server 配置是一个 JSON 数组，每项支持 id / command / args / cwd / env（stdio）或 url（HTTP，经 mcp-remote 桥接）。通过 DSH_MCP_SERVERS 环境变量或编辑 plugin.js 里的 DEFAULT_SERVERS 传入。示例见 examples/servers.json。