dsh-mcp-bridge

Skip the raw YAML: one install brings a curated, CI-verified set of MCP servers.

What problem it solves

Wiring up MCP servers usually means hand-maintaining YAML and debugging each one. This plugin turns verified MCP servers into a ready-to-use bundle: one install gives you everything (demo), memory (in-session knowledge graph), filesystem (file access scoped to explicit roots), github, playwright, and remote-http. Every curated server has a machine-readable definition, and scripts/verify-servers.mjs checks each one’s connectivity, so “verified” is a CI-guaranteed claim, not marketing.

Tools surface to the model as mcp__<server>__<tool> — the same server-qualified shape as Claude Code / Codex. The bridge is DSH’s built-in @deepseek-ai/dsh-mcp-client, with stdio / streamable-http, auto-reconnect, and HMR hot-swap.

Key features

• everything demo: echo, add, long-running ops, and tiny image tools, on by default with no API key (✅ 13 tools)
• memory knowledge graph: in-session entities / relations (✅ 9 tools)
• filesystem access: read/write/search strictly scoped to explicit roots (✅ 14 tools)
• GitHub integration: repos / issues / PRs, needs GITHUB_TOKEN
• Playwright automation: navigate / click / screenshot
• remote-http: connect your own or hosted HTTP MCP server
• CI verification: npm run verify prints PASS / SKIP / FAIL per server and exits non-zero on any failure
• Your own servers: each server is one client entry; add it to the profile patch layer and HMR applies it

Quick start

dsh plugin --profile web add dsh-mcp-bridge
dsh web   # restart the profile

The everything demo server is on by default (pure local npx, no key). After restart, ask the model to “call the everything server’s echo tool with hello” — it should use mcp__everything__echo. The first run downloads server packages via npx and caches them afterwards; to enable github, playwright, and other presets, uncomment their blocks in the profile’s cordis.patch.yml (hot-reloaded via HMR).

Who it is for

• Newcomers who want to try MCP without fiddling with config
• Project teams that need a stable MCP foundation
• Users of other agent harnesses (Reasonix / CodeWhale) who want to share the same MCP servers