DeepSeek Bridge for Claude Code
deepseek-bridge
An MCP server that hands bulk file work to a local DeepSeek Harness agent so file contents never enter Claude's context
Low risk
We rate an entry low when it mostly gives the agent instructions and reference material.
Why this level
- Runs a local DSH process and reads its output, with no access to production infobases
- Requires a DeepSeek API key in the bridge's environment
Install
Manual install
npm i -g @deepseek-ai/dshInstalls DeepSeek Harness, a separate product with its own setup. Alternative: the DSH Desktop app.
This is third-party code. Review the repository files before installing.
What it does
The server spawns a locally installed DeepSeek Harness (DSH) as a separate agent and hands it bulk, file-heavy work. DSH opens the needed files itself by path, so their contents never enter Claude Code's context, and tokens are spent only on the instruction and the answer. The bridge spawns the process, parses its output, and manages timeouts and sessions. It fits especially well with 1C:Enterprise, where configurations unpack into large sets of BSL files.
Who it is for. For Claude Code developers who need to offload context on bulk file-reading tasks, especially when working with 1C:Enterprise.
Good fit when
- You need to analyze many files without bloating Claude Code's context
- DeepSeek Harness is already set up and authorized
- You work with large 1C configuration exports
Not a fit when
- DeepSeek Harness is not installed: setting it up is a separate task that is not quick
- There is no DEEPSEEK_API_KEY for the bridge
- You are not on Windows: the POSIX branches are untested
Example request
Ask DeepSeek Harness to scan every module in this 1C configuration and find calls to a deprecated procedureLimitations
The bridge installs and configures nothing by itself: DSH is set up separately, and the README explicitly warns to budget an evening rather than five minutes for it. A DEEPSEEK_API_KEY is required in the bridge's own environment; the key from DSH Desktop settings is not inherited. Built and tested on Windows 11 only, and it needs Node.js 22.11 or newer.
How to disable. Remove the deepseek-bridge server from Claude Code MCP settings, and uninstall DeepSeek Harness separately if it is no longer needed.
MCP
- Transport
- stdio
- Authentication
- API key
| Environment variables | |
|---|---|
| DEEPSEEK_API_KEY required, secret | DeepSeek key, required in the bridge's environment, not inherited from DSH Desktop. |
| DSH_BIN | Explicit path to the DSH binary when autodetection fails to find the install. |
Security check
- Runs a local DSH process and reads its output, with no access to production infobases
- Requires a DeepSeek API key in the bridge's environment
README in short
The README stresses the bridge is a thin adapter, not a replacement for DSH: installing and authenticating DeepSeek Harness is entirely on the user. It cites a benchmark: a 30 KB markdown file is parsed in 14 seconds with zero bytes of the file in Claude's context. It covers the Node.js requirement, the need for DEEPSEEK_API_KEY specifically in the bridge's environment, and the Windows-only support.
FAQ
Why don't files enter Claude's context?
DSH opens files itself by the paths given in the task, and the bridge passes Claude only the final answer.
Is setting the key in DSH Desktop enough?
No, a headless run without DEEPSEEK_API_KEY in the bridge's environment fails with a missing credential error.
Related
A skills library that gives coding agents a development process: brainstorming, planning, TDD, subagents and code review
Skills for real engineers by Matt Pocock
Skills For Real Engineers
Small composable skills for engineering with agents: plan grilling, TDD, bug diagnosis, code review and architecture
GitHub toolkit for spec-driven development: the specify CLI adds agent commands and skills to a project, from principles to implementation
Reference MCP servers
Model Context Protocol servers
Official reference MCP servers: Filesystem, Fetch, Git, Memory, Sequential Thinking, Time and Everything