Use MCP servers in DeepSeek Harness with Toolport
Toolport is a free, open source local MCP gateway. Add your servers to Toolport once, flip the DeepSeek Harness toggle, and DeepSeek Harness gets all of them through a single gateway entry. Toolport picks a full tool list or search for each client, and you can change it in Clients.
Setup
- Download Toolport for Windows, macOS or Linux, and add your MCP servers to it (or import the ones your other AI agents already have; secrets go to your OS keychain).
- Open the Clients tab and toggle DeepSeek Harness on. Toolport writes its gateway entry into DeepSeek Harness's config, next to anything already there.
- Restart or reload DeepSeek Harness. Your full server set is available through Toolport, and any server you add later shows up without touching DeepSeek Harness again.
Where DeepSeek Harness keeps its MCP config
DeepSeek Harness MCP config
All platforms $DSH_HOME/cordis.patch.yml (~/.dsh/cordis.patch.yml by default)
YAML Cordis patch rows; Toolport adds one insert row for a dsh-mcp-client entry named toolport.
Good to know
- Comments, !!js expressions, other plugins and your own servers stay as they are. Per-profile layers are not changed.
- Start a new dsh session after connecting; the running one keeps the tools it started with.
Why a gateway instead of DeepSeek Harness's own server list?
- One setup, every agent. The same servers work in DeepSeek Harness and every other AI agent on your machine; add a server once and they all get it.
- Secrets in the OS keychain. API keys are injected at runtime and never sit in DeepSeek Harness's config file.
- Watched by default. Rug-pull and tool-poisoning detection on every tool, plus per-tool governance and a destructive-tool kill switch. How the security works.
Free on this machine. Pro puts it on every machine. Team gives it to everyone.