dsh-relay
References the Codex guide and dsh-mcp-codex README for documenting the workflow and setup instructions.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@dsh-relayrun relay_doctor and then relay_write_mcp_config for codex"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
dsh-relay
English | 中文
Web-profile helper that diagnoses the Codex MCP launch path and writes host configuration so Codex, Cursor, or Claude Code can spawn dsh --profile codex. It does not run the MCP stdio server in the Web process.
Install into a profile:
dsh plugin --profile web add github:tonytanglab/deepseek-harness-relay-mcpor install the GitHub Release tarball for a prebuilt lib/. Restart dsh web after install. Then run /relay-setup or ask the agent to call relay_doctor and relay_write_mcp_config.
What it does
apply registers one slash command and two tools on the Web profile:
/relay-setupprints the doctor summary and MCP launch JSON. WhenmcpConfigPathis set, it also writes that JSON. Extra input is rejected.relay_doctorchecks thatprocess.argv[1]is an absolute existing dsh entry, thatprocess.execPathexists, and that the credentials path exists, without reading credential contents and without starting MCP stdio.relay_write_mcp_configbuilds the npx launch block from the Codex guide. It writes the block whenpathis an absolute JSON file, mergingmcpServersso other servers remain.
The generated command is npx --yes --package=@deepseek-ai/dsh@0.1.0-rc.5 -- dsh --profile codex. The helper never uses npx.cmd or shell: true, and it never imports StdioServerTransport.
Related MCP server: Claude Code Subagent MCP
Configuration
Field | Default | Meaning |
|
| Key under |
| unset | Absolute JSON path |
|
| Empty reads |
|
| Shared credentials document; also |
|
| Codex service homes; also |
|
| Pinned package in generated npx args |
|
| Default host for |
Users override rows in the profile cordis.patch.yml. Invalid configuration fails plugin load.
After setup
Point the MCP host at the printed launch block. Session start, wait, steer, and cancel stay on dsh --profile codex, documented in @deepseek-ai/dsh-mcp-codex and the Codex guide. The bundled skill names that workflow.
Model Experience
Tool schema
What the model sees
relay_doctor has an empty parameter object. relay_write_mcp_config requires host as codex, cursor, or claude-code, and accepts optional absolute path.
Token effect
Fixed schema cost on every request where the tools are visible.
KV Cache effect
Prefix-stable while the definitions and visibility are unchanged.
Tool-call history and result
What the model sees
relay_doctor returns JSON with ok, launcher direct/exists/shell: false, workspace roots, and credentials path/exists. It never includes credential file contents. relay_write_mcp_config returns { written, path, host, serverName, config } whose config.args contain --profile and codex. /relay-setup success text starts with DSH Relay is loaded in this Web profile. It does not run the MCP stdio server here. Extra input returns The /relay-setup command does not accept extra input.
Token effect
Per call, bounded by the JSON report and the launch block.
KV Cache effect
Independent of earlier turns.
Known Limitations and Deferred Work
No in-process MCP stdio — installing this bundle into the web profile does not expose the eleven Codex MCP tools. Those remain on
dsh --profile codex.No Settings UI — there is no
dsh.clientform in v0.1.0;/relay-setupand the two tools are the configuration path.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Alicense-qualityCmaintenanceEnables MCP clients to spawn and control Codex CLI and Claude Code sessions on the host machine, with session management and filesystem access.4MIT
- Alicense-qualityBmaintenanceA stdio MCP server that lets Codex Desktop/CLI delegate implementation tasks to Claude Code CLI with workspace validation, Git status checks, and session resume capabilities.4MIT
- AlicenseAqualityBmaintenanceA project-local MCP bridge that allows Codex Desktop to plan tasks and OpenCode to execute them within the current project directory, with session reuse and native OpenCode background subagents.41MIT
- Alicense-qualityBmaintenanceProvides a read-only MCP tool to diagnose zoxide installation and shell setup, returning a JSON report with setup and troubleshooting guides.316MIT
Related MCP Connectors
Scans MCP servers for tool poisoning, prompt injection and supply chain risks.
Persistent memory and cross-session learning for AI coding assistants (hosted remote MCP).
A paid remote MCP for OpenAI Codex agent coordination MCP, built to return verdicts, receipts, usage
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/tonytanglab/deepseek-harness-relay-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server