Preface¶
The DSH plugin ecosystem emphasizes that “everything is a plugin.” For developers who need to integrate MCP tools into agents, manually organizing server commands, transport methods, tool naming, and startup failure behaviors can easily lead to configuration inconsistencies. dsh-mcp-bridge packages a set of commonly used MCP servers as DSH plugins and provides connectivity verification scripts, making it easy to confirm that servers are reachable before handing them over to the model.
What This Is¶
dsh-mcp-bridge is an MCP server bundle designed for DeepSeek Harness (dsh). A single installation provides access to demo, memory, filesystem, GitHub, Playwright, and remote HTTP MCP servers.
It uses DSH’s built-in @deepseek-ai/dsh-mcp-client, supporting stdio and streamable-http, automatic reconnection, and HMR hot-swap. Each curated server has machine-readable definitions under servers/; the scripts/verify-servers.mjs script checks the connectivity of each server, making “verified” a claim that can be rechecked via script.
Repository URL:
https://github.com/Edge-Echo/dsh-mcp-bridge
License:
MIT
Core Features¶
Demo Server Enabled by Default¶
The everything demo server is enabled by default and requires no API key. It provides echo, add, long-running ops, and tiny image tools. After installation and restart, the model can invoke mcp__everything__echo.
Other Servers¶
memory: Provides entities and relations for in-session knowledge graphs.filesystem: Supports file reading, writing, and searching, scoped to explicit roots.github: Supports repositories, issues, and PRs, requiring aGITHUB_TOKEN.playwright: Supports browser automation, such as navigate, click, screenshot.remote-http: Supports connecting to your own or hosted HTTP MCP servers, requiring a URL and an optional token.
Tools appear on the model side in the format mcp__<serverName>__<toolName>.
Installation and Activation¶
Prerequisites: dsh and pnpm must be in your PATH. dsh plugin forwards to pnpm. If pnpm is not installed locally, run:
npm i -g pnpm
To install the plugin:
dsh plugin --profile web add dsh-mcp-bridge
To install from a local checkout:
dsh plugin --profile web add ./dsh-mcp-bridge
Restart the profile:
dsh web
The first run downloads the server packages via npx; subsequent runs use a cache.
Typical Usage¶
After restarting, you can ask the model in a conversation:
call the everything server's echo tool with hello
The model should use mcp__everything__echo.
To enable commented-out presets, uncomment the corresponding server blocks in the profile’s cordis.patch.yml.
Verification and Troubleshooting¶
In the repository directory, run:
npm install
npm run verify
Or directly:
node scripts/verify-servers.mjs
npm install brings in @deepseek-ai/dsh-mcp-client, which corresponds to the MCP SDK.
To adjust the timeout per server, set:
VERIFY_TIMEOUT_MS=15000 npm run verify
To troubleshoot a single server, run:
node scripts/probe-server.mjs npx -y your-mcp-server
If failOnStartupError: false is configured, the entry may still activate on connection failure, but with no available tools.
Use Cases and Notes¶
Suitable for developers who need to quickly integrate a set of MCP tools into a dsh agent and want to perform connectivity checks first.
Notes before use:
- The plugin runs with the current dsh process’s privileges; inspect the source code and license before installation.
filesystemrequires explicit root directories.githubrequires aGITHUB_TOKEN.remote-httprequires a URL and an optional token.playwrightdownloads browsers on first run, which is heavy and excluded from CI.- Node engine requires
>=22. - If the profile requires
@deepseek-ai/dsh-headlessindsh.profile.bundles, headless verification may hang; runningdsh plugin add @deepseek-ai/dsh-headlessdirectly returns 404 due to its unpublished dependencies. - The DSH community directory is an independent site with no official affiliation with DeepSeek or High-Flyer; don’t treat it as an official app store.
Links¶
GitHub:
https://github.com/Edge-Echo/dsh-mcp-bridge