DSH MCP Bridge
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
DSH MCP Bridge
Bridges a live DeepSeek Harness (DSH) process to external Model Context Protocol clients (OpenClaw, Claude Code, Codex, …) over Streamable HTTP.
An external agent gets two things:
A real conversation partner — send a message to a DSH session and get the agent's answer.
DSH's tools —
read,write,edit,glob,grep,pwsh,web_search, …
OpenClaw agent ──HTTP/JSON-RPC──▶ http://<host>:18790/mcp ──▶ DSH session (agent loop + tools)Endpoint
Item | Value |
URL |
|
Transport | Streamable HTTP ( |
Protocol | MCP |
Auth | optional |
Health |
|
Overview |
|
Related MCP server: dsh-mcp-bridge
Bridge tools (talk to DSH)
Tool | Purpose |
| List sessions: id, cwd, preset, live/cold, running, which one is the execution target. |
| Read the trailing transcript ( |
| Send |
Every other tool name is passed straight through to ctx.tools and executed in the bridge's own
DSH session (see below).
Execution scope — why it is not your chat session
Tool calls and dsh_chat default to one dedicated bridge session (session-dsh-mcp-bridge,
created on first use in the first registered workspace and reused after restarts). Foreign callers
therefore never inherit the operator's chat session, its transcript, or its permission preset.
That session is created with an explicit sandbox/mode event (sandbox: danger-full-access by
default) — see the 0xC0000142 section for why that matters. execSessionId pins any other
existing session instead.
Add it to OpenClaw
Open
http://FNOS.COM:18789→ Settings → MCP.Add server, name
dsh, transport Streamable HTTP.URL:
http://<this-computer-LAN-IP>:18790/mcp.If
tokenis configured, add headerAuthorization: Bearer <token>.Save, then run
openclaw mcp doctor dsh --probe, or ask the agent to calldsh_sessions.
Config
- insert:
- id: mcp-bridge
name: '@local/dsh-mcp-bridge'
config:
host: '0.0.0.0' # bind address
port: 18790 # listening port
path: /mcp # endpoint path
token: '' # empty = no auth (trusted LAN); set to require Bearer auth
execSessionId: '' # pin the session used for tool calls / default chat target
workspace: '' # cwd for the auto-created bridge session (default: first workspace)
tools: [] # allowlist of DSH tool names; empty = every visible tool
chatTools: true # expose dsh_sessions / dsh_history / dsh_chat
sandbox: danger-full-access # sandbox mode recorded on the bridge sessionChange the config
Append an id-targeted override to %USERPROFILE%\.dsh\profiles\desktop\cordis.patch.yml, then
restart DeepSeek Harness. An override replaces the complete config, so repeat every field:
- id: mcp-bridge
name: "@local/dsh-mcp-bridge"
config:
host: '0.0.0.0'
port: 18790
path: /mcp
token: 'change-me-long-random-string'
execSessionId: ''
workspace: ''
tools: []
chatTools: true
sandbox: danger-full-accessWindows 0xC0000142 (STATUS_DLL_INIT_FAILED)
A spawned child process that cannot initialize its DLLs reports 0xC0000142. Nothing ran — it is a
process start failure, not a command failure.
Root cause found here: a freshly created session has no sandbox/mode override, so it inherits
the deployment default (workspace-write). Under that confined sandbox the pwsh child died with
0xC0000142 on every call. The bridge session now records an explicit mode, so this cannot happen
through the bridge:
config:
sandbox: danger-full-access # default; also: workspace-write | read-only | inheritinherit reproduces the old behaviour (deployment default). Whatever the mode, a 0xC0000142
result is retried once without a session scope (a crash means nothing executed, so the retry cannot
duplicate work) and, if that also fails, the reply carries the remediation instead of a bare error.
If you pin execSessionId to your own session, that session's preset is what applies — don't pin a
workspace-write session if you need spawned processes.
Security
With token: '' any host that can reach the port can drive this Harness — including pwsh and
dsh_chat. Keep it on a trusted LAN or set a token. Windows Firewall already allows the DeepSeek
Harness executable inbound on private/public profiles in a default desktop install.
Limits
GETon the MCP path returns 405 by design; the server only answers POSTed JSON-RPC.dsh_chatwaits for the turn to finish; it does not stream partial tokens.Image/file content blocks are reported as an omitted-content placeholder.
Tools are re-listed on every
tools/list; no restart is needed when plugins add tools.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Exposes FEDLIN's public security scanners as agent-callable tools over Streamable HTTP.
Remote MCP server exposing SMI Aware tools, resources, and skills over Streamable HTTP.
Remote MCP server exposing your Node Command fleet (files, shell, processes, browser) to AI hosts.
AI Reasoning Cache & Consensus Layer with 11 MCP tools via Streamable HTTP.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceLifts local stdio MCP servers into remote Streamable HTTP endpoints for cloud-hosted AI clients, with bearer-token auth and tool policy filtering.12 npmMIT
- AlicenseNot gradedqualityDmaintenanceExposes DeepSeek Harness tools to any MCP-compatible client over streamable HTTP, allowing allowlisted operations such as file read, glob, grep, and web search while preserving the harness's sandbox and approval pipeline.2MIT
- AlicenseNot gradedqualityCmaintenanceEnables a remote AI client to work on a PC over Streamable HTTP: reading files, viewing images, applying patches (Codex or unified diff), running one-shot or interactive shell commands, and writing to stdin sessions. It also acts as a gateway that exposes local stdio MCP servers, such as Blender, under namespaced tool names like blender__execute_blender_code.MIT
- AlicenseNot gradedqualityBmaintenanceExposes a local DeepSeek Harness instance to external MCP clients over Streamable HTTP, legacy HTTP+SSE, or a stdio bridge. Enables creating sessions, running multi-turn conversations, reading and full-text searching history, cancelling running turns, and listing or selecting models.44 npm1MIT