KYinCode/dsh-project-mcp-bridge
Per-project MCP loading for DeepSeek Harness: drop a .dsh/mcp.json into a project and its sessions get the MCP
Lets each project declare its own MCP servers: drop a .dsh/mcp.json into a project root and every session of that project gets those servers' tools (mcp<serverName><toolName>). Editing the file takes effect live — no new session, no restart. Configure servers with command/args/env entries, e.g. a GitHub MCP server via npx with a GITHUB_TOKEN env reference. A client bridge that consumes MCP servers, scoped per project.
Install
dsh plugin --profile web add dsh-project-mcp-bridgenpm package dsh-project-mcp-bridge 0.2.1 (registry-verified 2026-08-29). The package is a profile bundle: dsh plugin --profile web add dsh-project-mcp-bridge installs and reconciles dsh.profile.bundles automatically — no manual patching. Restart dsh web once after installing (bundle layers compose at startup); after that, .dsh/mcp.json edits are hot.
Compatibility
DeepSeek Harness web profile. Client bridge (consumes MCP servers) — not an MCP server and not an official DeepSeek package.
Details
- Repo: KYinCode/dsh-project-mcp-bridge
- Category: Coding & Development
- Stars: 2
- Version: npm dsh-project-mcp-bridge 0.2.1 (registry-verified 2026-08-29)
- Last push: 2026-08-14
- First seen: 2026-08-14
Recent updates
per-project MCP via .dsh/mcp.json; live hot-reload of config; mcp<server><tool> namespacing; env var references; client bridge.
FAQ
- How do I enable MCP for a project?
- Drop a .dsh/mcp.json into the project root declaring its mcpServers; every session of that project then has those servers' tools.
- Do changes need a restart?
- No — editing .dsh/mcp.json takes effect live; only the initial plugin install needs one restart.
- Is it an MCP server?
- No — it is a client bridge that consumes MCP servers, not a server itself and not an official DeepSeek package.
Alternatives
PerryLink/dsh-github · cyanseek/dsh-landscape · omdsh-dev/dsh-genui