- MCP setup guide
- Checked 25 Oct 2026
DeepSeek Harness MCPAdd an MCP server to DSH
Add any MCP server to DeepSeek Harness, or connect SpringBrand once for live search, social data and 861 APIs.
Or skip local setup and try it right now
The same tools as the MCP connection, in SpringBrand's cloud agent. Type a task to start.
Opens SpringBrand in a new tab with your task filled in. 300 free credits to start.
DSH talks to MCP servers through its own plugin, @deepseek-ai/dsh-mcp-client. Each server is one entry in a Cordis patch file, usually ~/.dsh/profiles/web/cordis.patch.yml. Once it connects, the server's tools show up as mcp__<server>__<tool>. For servers that sign in through the browser, add dsh-oauth-mcp-client.
Checked 25 October 2026 against the deepseek-harness and dsh-oauth-mcp-client READMEs on GitHub and @deepseek-ai/dsh 0.2.1-rc.2 (npm latest).
Direct answer
How DeepSeek Harness connects to MCP
There is no MCP server switched on by default. You add one entry per server, DSH connects at startup, and the tools appear before the first turn.
- 01
The built-in client: @deepseek-ai/dsh-mcp-client
DSH's own MCP client plugin. It uses stdio for a local program and streamable-http for a remote service (a URL plus optional headers). Every tool is named mcp__<serverName>__<tool>, so two servers can both have a search tool.
dsh-mcp-client README - 02
Where the config lives: cordis.patch.yml
To try a server once, run dsh web --patch <file>. To keep it, merge the entry's - insert: block into $DSH_HOME/profiles/<profile>/cordis.patch.yml for one profile, or $DSH_HOME/cordis.patch.yml for every profile. Merge it in. Don't overwrite the file, because it may hold other patches.
Official MCP memory guide - 03
Servers that need a browser login: dsh-oauth-mcp-client
The built-in client takes a URL and static headers. For servers that use OAuth, the community plugin @dsh-external/dsh-oauth-mcp-client (maintained by SpringBrand, MIT) adds OAuth 2.1 with PKCE, a loopback callback, stored tokens and reconnects.
dsh-oauth-mcp-client README - 04
Settings → Plugins → MCP Connections
With that plugin installed, DSH Web gets a Settings → Plugins → MCP Connections page. Enter a unique name and the HTTPS MCP URL, select Add and sign in, and finish the login in your browser. The page writes the connection to ~/.dsh/profiles/web/cordis.patch.yml, so it survives a restart.
Setup generator
Connect SpringBrand MCP to DSH in three choices
SpringBrand runs one MCP endpoint, https://connector.springbrand.ai/mcp, for its whole catalog of web search, social data, lead, SEO and media APIs. Pick a starting job and an install method, then copy.
3Copy, run, then send the first prompt
Prompt for your coding agent
Set up DeepSeek Harness with SpringBrand on my machine using https://github.com/springbrand-lab/dsh-oauth-mcp-client. Install official DSH, build and add the SpringBrand OAuth MCP client to my DSH Web profile, start DSH, then stop for my browser OAuth. Verify that SpringBrand MCP tools are registered.First prompt in DSH
Use SpringBrand to search the web for this week's news about <topic>. Give me the 5 most useful results with one line each and the link.Next: when DSH starts, a browser opens to sign in to SpringBrand. New accounts get 300 free credits. Then check Settings → Plugins → MCP Connections for the live status.
Create a free SpringBrand accountWhat you get
One sign-in, the whole SpringBrand catalog
DeepSeek Harness runs the agent. SpringBrand gives it live web search, social data and media generation through one MCP connection, with a single OAuth sign-in instead of a key for every provider.
28 providers861 APIs16 social platforms
Live web search & scraping
Search results, page text and structured extraction from Exa, Serper and Firecrawl.
Social data from 16 platforms
Posts, profiles, comments and trends from Xiaohongshu, Douyin, TikTok, X and more.
Image, video & voice
Generate with Seedream, GPT Image 2, Seedance 2.0 and ElevenLabs text to speech.
SEO & lead data
Backlinks and keyword metrics from Ahrefs and Semrush, contacts from Apollo.
Any MCP server
Generate a cordis.patch.yml entry for any MCP server
Type a name and the server's MCP URL. The snippet follows the examples in the official dsh-mcp-client docs and the dsh-oauth-mcp-client README. Nothing you type leaves this page.
Letters, numbers, - and _, up to 32 characters. It becomes part of every tool name.
The server's Streamable HTTP endpoint, usually ending in /mcp.
cordis.patch.yml entry
- insert:
- id: my-mcp-mcp-oauth
name: '@dsh-external/dsh-oauth-mcp-client'
config:
serverName: my-mcp
url: 'https://mcp.example.com/mcp'
credentialRef: MY_MCP_MCP_OAUTH
failOnStartupError: trueMerge this into ~/.dsh/profiles/web/cordis.patch.yml (don't replace the file), then restart DSH. The tools will show up as mcp__my-mcp__<tool>. For an API token, set the environment variable before you start DSH.
OAuth entries need the dsh-oauth-mcp-client plugin installed in the same profile first. Use the manual commands above, or add the server from Settings → Plugins → MCP Connections instead.
Field reference: dsh-mcp-client README on GitHubCommon errors
DSH MCP errors and how to fix them
Most failures fall into one of three groups: the OAuth sign-in never completes, Node.js is too old, or the server connected but registered no tools.
The browser login never finishes, or the OAuth callback fails
- Cause
- The plugin listens for the callback on your computer's loopback address and waits 5 minutes (authorizationTimeoutMs is 300000). The login timed out, or the browser ran on a different machine from DSH.
- Fix
- Restart DSH and finish the login within 5 minutes in a browser on the same computer. If it keeps failing, remove the connection in Settings → Plugins → MCP Connections and add it again.
pnpm install or pnpm build fails on the plugin
- Cause
- dsh-oauth-mcp-client requires Node.js 22.19 or later.
- Fix
- Run node --version. Upgrade to Node.js 22.19+ and run corepack enable, pnpm install and pnpm build again.
DSH starts, but no mcp__ tools appear
- Cause
- The first connection or tool sync failed. With the built-in client, DSH still starts, logs the error and registers no tools from that server. Two entries with the same serverName also fail: the later one doesn't load.
- Fix
- Check the DSH log for the server error, give every entry a unique serverName, and confirm the URL is a Streamable HTTP MCP endpoint. Discovery runs in the background, so wait for the tools before your first prompt.
The tools were there, then disappeared
- Cause
- After 10 failed reconnect attempts in a row, the client removes that server's tools and stops retrying.
- Fix
- Restart DSH or edit the entry to reload it once the server is reachable again.
Sources
Where these facts come from
Read on 25 October 2026.
- deepseek-harness: packages/mcp/mcp-client README
Config fields, tool naming, startup failure and reconnect behavior.
- deepseek-harness: MCP memory guide
--patch for one run, and where to merge a patch to keep it.
- springbrand-lab/dsh-oauth-mcp-client README
Requirements, install commands, MCP Connections page, manual OAuth config.
- @deepseek-ai/dsh on npm
latest tag 0.2.1-rc.2 at the time of checking.
Next step
Need the job to keep running after you close the laptop?
Local DSH stops when your computer sleeps. SpringBrand's cloud agent can run the same task 24/7 and on a schedule.
SpringBrand is independent, not affiliated with DeepSeek. dsh-oauth-mcp-client is a community plugin maintained by SpringBrand.