dsh-relay
Related Servers
Alternatives to dsh-relay
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceLaunches the official Codex CLI as a persistent MCP server so DeepSeek Harness can invoke Codex models without storing or transmitting ChatGPT credentials to third parties.MIT
- AlicenseNot gradedqualityBmaintenanceRuns a loopback-only MCP endpoint that lets Codex dispatch coding tasks to a DSH headless agent, which does the actual file edits and command execution while returning structured results, session IDs for follow-ups, and honest failure classifications. It also provides environment introspection and session resumption.1MIT
- AlicenseNot gradedqualityBmaintenanceProvides a read-only MCP tool to diagnose zoxide installation and shell setup, returning a JSON report with setup and troubleshooting guides.29 npmMIT
- AlicenseAqualityCmaintenanceEnables MCP-compatible coding agents to execute the local Codex CLI as a coding agent, including code reviews, session resume/fork, and CLI diagnostics.915 npmMIT
- AlicenseNot gradedqualityAmaintenanceConnects ChatGPT Web to a local development environment, enabling file reads and patches, shell execution, plan updates, and isolated worktree coordination through permissioned MCP tools.4MIT
- AlicenseAqualityCmaintenanceDelegates coding tasks to the locally installed DeepSeek Harness CLI, enabling MCP clients to run prompts through dsh and receive results with exit code and timing.1MIT
TDQS
Scored across 27 tools
The set has clear families, but several tools overlap around run status and reconciliation: get_run, status_run, get_run_summary, wait_run, and reconcile_operation require careful reading to distinguish. start_run, start_review, reply_run, and steer_run are meaningfully different but still easy to confuse without the long descriptions.
Most names are consistent snake_case verb_noun patterns, especially the run and service families. The deprecated status_run alias, bare doctor, and setup_plan/setup_doctor are minor deviations but still readable.
At 27 tools, the surface is heavy for a relay/coordination server and includes a deprecated compatibility alias. The many run, service, operation, and setup tools feel broader than an agent needs for the core workflow.
The tool set covers the major lifecycle: service attachment, run creation, polling, steering, replying, cancellation, interactions, operations, permissions, and setup diagnostics. Minor detail gaps such as direct service or workspace lookup are not fatal because listing tools and open_service cover most needs.