deepseek_harness
Related Servers
Alternatives to deepseek_harness
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables three-layer Codex-to-DeepSeek coordination with project memory, task dispatch, worker collection, and workspace permission mapping through an MCP bridge over Codex app-server and Harness.MIT
- AlicenseNot gradedqualityBmaintenanceEnables Codex to delegate scoped coding tasks to DeepSeek Harness subagents over MCP using the official ACP, then wait for results, resume the same session with corrections, and forward permission requests. Read-only and workspace-write modes let results be reviewed and independently verified before acceptance.MIT
- AlicenseNot gradedqualityBmaintenanceMCP bridge enabling ChatGPT to create, view, and control DeepSeek Harness agent sessions, with session management, messaging, and approval tools.422 npm28MIT
- AlicenseNot gradedqualityAmaintenanceEnables orchestrators like Claude Code, Codex, Antigravity, and Grok to dispatch work to DeepSeek Harness agents as native subagents with live progress, tier policy, and escalation. It also provides a multimodal bridge that lends the text-only harness vision and image generation.354 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables dispatching work to DeepSeek Harness agents from Claude Code/Codex, with native progress UI, tier policy, and vision/image generation through MCP tools.678 npm220MIT
- AlicenseNot gradedqualityAmaintenanceEnables hosts like Claude Code, Codex, Antigravity and Grok to dispatch tasks to DeepSeek Harness agents that appear as native subagents with live progress and token stats. It provides tier and effort selection, escalation and dispatch guardrails, a jobs board, in-host or standalone worker sessions, plus a multimodal bridge that lends text-only models vision and image generation.354 npmMIT
TDQS
Scored across 3 tools
dsh_delegate_task overlaps with dsh_team's bundled "Worker/task operations," so it is unclear when to delegate versus use team task controls. Only dsh_team_wait is clearly distinct, while dsh_team packs many separate actions (open, snapshot, review, complete, archive, capabilities, help) into one ambiguous entry point.
All names share the dsh_ prefix, but the base conventions are mixed: dsh_delegate_task is verb_noun, dsh_team is a bare noun, and dsh_team_wait is noun_verb. They remain readable, but there is no predictable verb_noun pattern across the set.
Three tools is too thin for a surface that covers delegation, team lifecycle, worker/task operations, review, completion, archive/restore, capabilities, help, and waiting. Much of that functionality is compressed into the single dsh_team mega-tool rather than split into scoped tools.
Delegation, snapshot, review, complete, archive/restore, and waiting are represented, so the core lifecycle is mostly covered. However, explicit task cancellation/abort and granular worker/task operations are only implied inside dsh_team, leaving notable gaps in the visible surface.