Codex-DSH Bridge
Related Servers
Alternatives to Codex-DSH Bridge
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables MCP hosts to submit delegated tasks to configured DSH interfaces, inspect status and results, cancel runs, and answer pending one-time permission requests. It supports workspace isolation and Codex integration while keeping local delegation gated by a host-side switch.1,175 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to delegate bounded tasks to a local OpenCode worker while monitoring progress, reviewing evidence, and managing session rework or recovery. It also supports persistent TUI tabs for delegated task workspaces.2MIT
- AlicenseNot gradedqualityBmaintenanceEnables Codex to delegate scoped tasks to a local DeepSeek Harness over MCP — dispatching read-only reviews or authorized workspace writes, steering and monitoring runs to a terminal state, and returning structured evidence such as changed paths, test results, and assistant text. It also supports exact archival of the terminal session by full session ID.1MIT
- AlicenseNot gradedqualityCmaintenanceExposes DeepSeek Harness agent capabilities over MCP so any MCP client can delegate real coding work to a running agent with its full toolset (bash, filesystem, todo, web). Turns are dispatched asynchronously into sessions and then tracked through status, tail, wait, cancel, compact, and rename tools, with the session log as the source of truth so results survive restarts.MIT
- AlicenseNot gradedqualityCmaintenanceEnables Codex and DeepSeek Harness to hand off work to each other, then track progress, wait for results, cancel running work, and continue the original execution session. Tasks run in a local service independent of the caller, so closing a chat or losing the MCP connection does not stop them.MIT
- AlicenseNot gradedqualityCmaintenanceEnables an MCP client to delegate coding work to independently configured sub-agent sessions with any connected model, agents, skills, parallel execution, permission controls, and full API access, returning answers, changed files, and costs.MIT
TDQS
Scored across 14 tools
Most tools have a clearly distinct purpose (submit/wait/get_result/get_events/continue/cancel map to discrete lifecycle actions), and descriptions explicitly state what each does NOT do. The riskiest overlaps are within the read family — dsh_get_task vs dsh_get_result vs dsh_get_history vs dsh_list_history — where an agent must parse long descriptions to pick correctly.
All names use a uniform dsh_ prefix with snake_case verb_noun structure (dsh_submit_task, dsh_get_events, dsh_cancel_task), which is highly predictable. Minor deviation: the prepare_recovery/recover_task pair splits one conceptual operation across two verbs, and some names are verb_noun_noun (dsh_submit_review, dsh_get_capabilities), slightly reducing uniformity.
14 tools sit comfortably in the expected 3-15 band, and each maps to a real lifecycle stage (discovery, execution, observation, review, export, recovery). The set is on the heavier side but no tool looks redundant or trivially trivial.
The surface covers a full task lifecycle: capabilities, submit, poll/wait, result, events, continue, cancel, review, delivery export, history, and recovery. Minor gaps: there is no way to enumerate live tasks in the current bridge process (only persisted history is listable), and no explicit cleanup/delete of task directories.