DeepSeek Bridge for Claude Code MCP
deepseek-bridge
An MCP server that hands bulk file work to a local DeepSeek Harness agent so file contents never enter Claude's context
- 2 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Launches the local DeepSeek Harness agent, which can write files and run commands
- What it may do is set by DSH permissions, not by the bridge
- Spends the DeepSeek API key from the bridge environment
Install
- Works in
- Services
Manual install
npm i -g @deepseek-ai/dshInstalls DeepSeek Harness, a separate product with its own setup. Alternative: the DSH Desktop app.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Launches the local DeepSeek Harness agent, which can write files and run commands
- What it may do is set by DSH permissions, not by the bridge
- Spends the DeepSeek API key from the bridge environment
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 procedureMCP
- Transport
- stdio
- Authentication
- API key
Environment variables
DEEPSEEK_API_KEYrequired, 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.
Limitations
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.
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.
Discussion
No questions or reviews yet.
Related
All 1C:Enterprise toolsA DeepSeek Harness plugin-runner: starts and stops the rlm-tools-bsl MCP server for 1C code analysis alongside DSH and registers it in the MCP manager itself
An MCP server built as a 1C external processing that gives Claude access to metadata, queries and the event log of any configuration
HTTP 1C MCP gateway with a dashboard
onec-mcp-universal
A Docker gateway with 40-plus MCP tools for 1C, one address, a settings dashboard and a set of 1C skills for Claude Code
MCP 1C Local Bridge: an agent inside an open 1C session
mcp-1c-local-bridge
An MCP server plus a 1C external data processor that lets an agent run queries and code in the user's already open session, with no gateway in between
A Dockerized MCP server that keeps BSL Language Server running and gives the agent code navigation, diagnostics and refactoring for 1C instead of grep search
MCP bridge to BSL Language Server: navigation, diagnostics and refactoring of 1C and OneScript code for agents
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.