Overview
dsh-project-mcp-bridge
Per-project MCP loading for DeepSeek Harness: sessions of a project automatically get the MCP servers declared in its .dsh/mcp.json (mcpServers JSON shape, shared with Claude Code / Cursor / VS Code). Client bridge — consumes MCP servers, not an MCP server, not an official DeepSeek package.
README / EN
Package documentation
Registry summary
Per-project MCP loading for DeepSeek Harness: sessions of a project automatically get the MCP servers declared in its .dsh/mcp.json (mcpServers JSON shape, shared with Claude Code / Cursor / VS Code). Client bridge — consumes MCP servers, not an MCP server, not an official DeepSeek package.
dsh.pub verifies the pinned bundle contract, runtime facts, and distribution semantics. The complete README remains in the source repository.
Read the full README on GitHubLIMITATIONS
Known limitations
- Resources and prompts from MCP servers are not bridged (tools only). - Connections are **per agent, never pooled**: N sessions calling the same server = N processes. Heavy servers (e.g. chrome-devtools) cost one process per active session — the idle timeout keeps unused ones short- lived. Session creation also pays one brief schema-sync spawn per server. - Streaming/task-based MCP execution is not supported (call only).