ben7am1n/dsh-mcp-proxy
dsh-mcp-proxy gives context-cheap MCP access for DeepSeek Harness. The shipped dsh-mcp-client registers every tool of every configured server on ctx.tools, so a handful of MCP servers puts hundreds of JSON schemas into the system prompt of every request — whether or not the model ever calls one. This plugin registers exactly two tools regardless of how many servers you configure and reaches those servers lazily: mcp_discover searches the tool catalog by keyword (returns server, name, description, argument names) and mcp_call invokes one tool by server and name. The catalog is cached on disk, so mcp_discover answers from a cold cache, and the standing prompt cost is constant in the number of MCP tools available.
Install
dsh plugin --profile web add dsh-mcp-proxydsh plugin --profile web add dsh-mcp-proxy (npm dsh-mcp-proxy 0.1.0, verified npm 2026-08-31; repo ben7am1n/dsh-mcp-proxy). Then declare your servers by overriding the row (the shipped row has none — see the README's Trust section).
Compatibility
DSH web profile; context-cheap MCP access; two proxy tools regardless of server count; MIT.
Details
- Repo: ben7am1n/dsh-mcp-proxy
- Category: Infrastructure & Deployment
- Stars: 1
- Version: npm dsh-mcp-proxy 0.1.0
- Last push: 2026-08-13
- First seen: 2026-08-13
Recent updates
2 proxy tools (mcp_discover, mcp_call); lazy server reach; disk-cached catalog; constant prompt cost regardless of MCP server count.
FAQ
- Why only two tools?
- To keep the standing prompt cost constant in the number of MCP tools available — the model discovers tools via mcp_discover instead of having every schema injected into every request.
- How do I add MCP servers?
- Override the plugin's row in the profile's cordis.patch.yml to declare your servers (the shipped row has none).
- Is the catalog fast?
- Yes — it is cached on disk, so mcp_discover answers from a cold cache without waking the servers.
Alternatives
Js2Hou/dsh-mcp-manager · KYinCode/dsh-project-mcp-bridge · PerryLink/dsh-mcp-panel