labmimors/dsh-mcp-lens
Progressive-disclosure MCP gateway that searches large remote catalogs through mcp_search, then invokes exact schemas through mcp_call with lazy connections and bounded caches.
dsh-mcp-lens shrinks huge MCP catalogs to a two-tool model surface: instead of sending every tool schema on every turn, it keeps two stable model-facing interfaces (search + call) and reveals exact schemas only for a small ranked set when a tool is actually needed. In the README's dated three-task pilot, estimated input cost dropped from $0.0307 to $0.0035 per task and request header tool JSON shrank from ~674 KB to ~27 KB, while both arms completed 3/3 tasks. rc.9 reuses the tokenized search index for each frozen catalog and policy generation, invalidating only when the catalog changes; final server/tool calls are still gated by the host's allowTools/denyTools policy. A companion website and a local schema-budget calculator let you measure your current tool-schema bytes before installing.
Install
dsh plugin --profile web add dsh-mcp-lens@0.1.0-rc.9npm dsh-mcp-lens 0.1.0-rc.9 verified 2026-09-03 (repository field → github.com/labmimors/dsh-mcp-lens; README EN primary with 简体中文 edition). Install: dsh plugin --profile web add dsh-mcp-lens@0.1.0-rc.9 (npm next tag resolves to the same version); GitHub Release tarball path documented with SHA-256 verification. Requires DeepSeek Harness 0.1.0-rc.6, Node ^22.19.0 or >=24, pnpm on PATH.
Compatibility
DeepSeek Harness 0.1.0-rc.6 (dsh plugin delegates to pnpm); Node.js ^22.19.0 or >=24.0.0; works with dozens-to-thousands of MCP tools across many servers.
Details
- Repo: labmimors/dsh-mcp-lens
- Category: Development & Runtime
- Stars: 0
- Version: npm dsh-mcp-lens 0.1.0-rc.9
- Last push: 2026-09-11
- First seen: 2026-08-14
Recent updates
0.1.0-rc.9 is the current release (verified 2026-09-03); changelog highlights index reuse across catalog changes.
FAQ
- When should I install this?
- When you have dozens to thousands of MCP tools across multiple servers and the per-turn tool schemas are eating input context; skip it if you only use a handful of tools every request.
- Does it weaken tool security?
- No — search only reveals schemas for a ranked subset and the final server/tool invocation remains gated by allowTools/denyTools on the host.
- Which MCP servers does it support?
- Any servers you connect to DeepSeek Harness; it is catalog-agnostic and works on the MCP tool seam.
Alternatives
NexusAgentX/dsh-mcp-adapter · Js2Hou/dsh-mcp-manager