NexusAgentX/dsh-mcp-adapter
MCP adapter for DeepSeek Harness — one proxy tool instead of dumping every MCP schema into context.
dsh-mcp-adapter lets DeepSeek Harness use MCP servers without burning the context window: instead of loading every tool from every server up front, it exposes one mcp proxy tool with lazy server start and on-demand search / describe / call. From the Web UI, /mcp opens a management popup with Status / Sources / Prompts panes, one-click presets for DeepWiki, Context7, Notion, GitHub and Chrome DevTools (written to the project .mcp.json), Connect/Authorize for OAuth servers, and Disable/Remove with confirmation. Custom servers can be added from chat (/mcp add docs url=…, /mcp add fs command=npx args=-y,@modelcontextprotocol/server-filesystem,/tmp) and reload in-process. The model then asks for a capability by search terms — e.g. mcp({ search: "screenshot" }) — and only the matching tool description is loaded, keeping prompt cost constant as server count grows. Tool cards reuse the official DisclosureRow/StateDot/SearchBlock chrome.
Install
dsh plugin --profile web add dsh-mcp-adapternpm dsh-mcp-adapter 0.6.3 verified 2026-09-03 (repository field → github.com/NexusAgentX/dsh-mcp-adapter; README EN primary with zh edition). One-command install: dsh plugin --profile web add dsh-mcp-adapter, then restart dsh web and hard-refresh the browser. The package is dual-face: the Host half registers tools and commands; the Web client half adds the /mcp popup and MCP tool cards. There is no MCP form under Settings → Plugins (official plugin settings are an allowlist); configuration happens in the /mcp menu or JSON files.
Compatibility
DeepSeek Harness (dsh); uses .mcp.json project files; connects MCP servers over stdio or HTTP; OAuth browser flow for auth-required servers.
Details
- Repo: NexusAgentX/dsh-mcp-adapter
- Category: Agent Capabilities
- Stars: 0
- Version: npm dsh-mcp-adapter 0.6.3
- Last push: 2026-08-14
- First seen: 2026-08-14
Recent updates
One mcp proxy tool; lazy server start; on-demand search/describe/call; /mcp WebUI with presets + OAuth; .mcp.json project config; constant prompt cost across N servers.
FAQ
- Why is there no Settings → Plugins entry for MCP?
- Official plugin settings are an allowlist, so out-of-tree plugins cannot register a card there. dsh-mcp-adapter configures itself through the /mcp menu or JSON files instead.
- How does it keep the context window small?
- Rather than listing every tool of every server, the model searches tool descriptions on demand and only the selected capability is loaded into context.
- Where are added servers stored?
- One-click presets and /mcp add commands write to the project .mcp.json file and reload in-process.
Alternatives
ben7am1n/dsh-mcp-proxy · Js2Hou/dsh-mcp-manager · nexusagentx/dsh-lens