dsh-plugin-mcp

You have likely already stood up MCP servers for GitHub, PostgreSQL, the filesystem, and beyond, yet the moment you open DeepSeek Harness to write agents, those tools sit scattered across separate processes with no automatic registration and no unified lifecycle management. dsh-plugin-mcp fills that gap. It is a universal MCP bridge for DSH that attaches any MCP server over stdio, SSE, or WebSocket with zero glue code.

Core capabilities span three layers. On the tool side, MCP tools are dynamically registered into the DSH tool registry with JSON Schema validation, and every tool name is automatically prefixed with its server identity (e.g. github_create_issue, postgres_query) to eliminate cross-server collisions. On the resource and prompt side, MCP resources and prompt templates are exposed directly into the agent context, removing the need to hand-wire them together. On the runtime side, a scale engine built for tens of thousands of servers uses a dormant-by-default process pool with JIT worker activation and an LRU idle-process reaper that persists structured previews as local artifacts; each server runs in an isolated lifecycle with its own timeout and non-blocking error handling, all constructed on native Cordis lifecycle hooks.

It is a natural fit for developers and engineering teams who have already invested in the MCP ecosystem and want a Claude Code-level tool-integration experience without leaving the DSH environment.