Edge-Echo/dsh-mcp-bridge
Curated MCP server bundle: one install brings demo, memory, filesystem, GitHub, Playwright and remote HTTP MCP servers, plus a connectivity verifier tool and CI checks.
dsh-mcp-bridge is a curated, CI-verified MCP server bundle for DeepSeek Harness. One install gives your agent a set of battle-tested MCP servers — not a raw YAML to configure manually. Every curated server has a machine-readable definition in servers/ and connectivity is verified by CI. Tools appear as mcp<serverName><toolName>, matching the Claude Code / Codex naming convention. Uses DSH's built-in dsh-mcp-client with stdio + streamable-http, auto-reconnect, and HMR hot-swap.
Install
dsh plugin --profile web add dsh-mcp-bridgenpm package dsh-mcp-bridge 0.1.3 (registry-verified 2026-08-24). Requires pnpm on PATH (npm i -g pnpm; dsh plugin forwards to pnpm). After install restart dsh web. The demo server (MCP official everything) is enabled by default — no API key, pure local npx. Additional curated servers are defined in the servers/ directory; each is machine-readable and CI-verified for connectivity via scripts/verify-servers.mjs.
Compatibility
DeepSeek Harness web profile. pnpm required on PATH. Uses DSH's built-in @deepseek-ai/dsh-mcp-client (stdio + streamable-http, auto-reconnect, HMR hot-swap). Tools appear as mcp<serverName><toolName> (Claude Code / Codex compatible naming). CI verifies each server's connectivity.
Details
- Repo: Edge-Echo/dsh-mcp-bridge
- Category: Tools & Capabilities
- Stars: 5
- Version: npm dsh-mcp-bridge 0.1.3 (registry-verified 2026-08-24)
- Last push: 2026-08-15
- First seen: 2026-08-14
Recent updates
0.1.3: curated servers/ directory (machine-readable definitions); CI connectivity verification (verify-servers.mjs); demo server enabled by default (MCP official everything, no key, npx); mcpserverNametoolName naming; DSH built-in dsh-mcp-client (stdio + streamable-http, auto-reconnect, HMR).
FAQ
- What is included by default?
- The MCP official everything demo server is enabled by default — no API key required, runs locally via npx. Additional curated servers are defined in servers/ and must be enabled in your patch configuration.
- How are servers verified?
- Each server definition in servers/ is machine-readable. The script scripts/verify-servers.mjs runs CI checks on each server's connectivity — so 'verified' is a CI-guaranteed claim backed by automation.
- How do tool names appear to the model?
- Tools appear as mcp<serverName><toolName>, matching the server-qualified naming convention used by Claude Code and Codex. This makes it straightforward to use the same MCP servers across harnesses.
Alternatives
omdsh-dev-dsh-web-review · TonyDua/dsh-web-search-exa · omdsh-dev/dsh-plugin-skills