Skip to main content
Glama

Related Servers

Alternatives to deepseek_harness

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables 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 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables 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 npm
      MIT

    TDQS

    C2.8/5.0

    Scored across 3 tools

    Disambiguation2/5

    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.

    Naming Consistency3/5

    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.

    Tool Count2/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data