dsh-orchestrator
Related Servers
Alternatives to dsh-orchestrator
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceA stdio MCP server that wraps DeepSeek Harness's local /api into 9 tools, letting any standard MCP client create or adopt named dsh sessions, dispatch task briefs, poll asynchronously, and retrieve auditable per-turn results. It also enforces pre-validated model allowlists, workspace/alias boundaries, and a persistent session ledger, so agents can collaborate across harnesses without modifying dsh or installing client plugins.331 npmMIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that bridges Codex with DeepSeek Harness to delegate coding tasks into isolated worktrees, providing profile-based model routing, single/multi-agent orchestration, and reviewable artifacts.26 npm1Apache 2.0
- AlicenseNot gradedqualityCmaintenanceBridges DeepSeek Harness ACP services to MCP stdio hosts like Codex, enabling session management, model selection, background tasks, cancellation, and subagent observation.MIT
- AlicenseNot gradedqualityCmaintenanceExposes a local loopback MCP endpoint that lets Codex spawn, wait on, follow up with, and close DeepSeek Harness sessions as workers and read back their final answers, while letting DSH agents dispatch work back to Codex in return. Includes delegation-depth and rate-limit guardrails, per-working-directory worker quotas, and persisted worker state that survives restarts.1,234 npm4MIT

dsh-bridgeofficial
AlicenseNot gradedqualityBmaintenanceMCP server enabling bidirectional messaging and collaborative development between DeepSeek Harness (DSH) sessions and ChatGPT desktop/Codex CLI sessions, with session ownership management and queued delivery.331 npmMIT- AlicenseNot gradedqualityAmaintenanceEnables Codex to supervise long-running DeepSeek Harness sessions through MCP, providing tools for progress monitoring, handoffs, and artifact management while keeping the host independent.MIT
TDQS
Scored across 13 tools
Most tools have distinct purposes, but dsh_followup/dsh_continue are explicit aliases and dsh_observe is an alias for dsh_wait+dsh_tail, creating selection ambiguity. dsh_host_status and dsh_status also have overlapping names, though their descriptions clarify the difference.
All tools share a consistent dsh_ prefix and snake_case style, and most use verb-first names (delegate, cancel, wait). Minor deviations include noun-based names like dsh_status/dsh_host_status and the alias dsh_continue that duplicates dsh_followup.
At 13 tools, the set is well-scoped for an orchestrator, covering session, task, and approval management without overwhelming bloat. The count is within the ideal 3-15 range.
The surface covers session creation (dsh_delegate), continuation (dsh_followup), monitoring (dsh_status, dsh_tail, dsh_wait), cancellation (dsh_cancel), and human-interaction handling (dsh_answer_question, dsh_resolve_approval). A minor gap is the lack of an explicit session close/termination tool, though dsh_release_workspace handles part of the teardown.