Skip to main content
Glama

Related Servers

Alternatives to dsh-any-agent

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Lets Claude Code, Codex, or any MCP client drive DeepSeek Harness as a long-lived coding agent: starting and resuming conversations, dispatching tasks in the background, streaming live output and reasoning stats, interjecting or interrupting mid-turn, handling approval prompts, and collecting results later. Sessions persist by ID, so work survives process restarts and can be handed back to a DSH GUI when needed.
      16
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Lets any MCP-capable coding harness (Cursor, Claude Code, Codex, Gemini CLI, VS Code/Copilot, opencode, and others) hand a self-contained task to a real, isolated DeepSeek Harness process that works in a chosen workspace with its own context window, model, and toolchain, then returns the final answer. Exposes task submission with time estimates and acceptance criteria, status polling with live progress and process-tree telemetry, graceful cancel and forced kill of whole process trees, and a health probe reporting concurrency, deadlines, and recent jobs.
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables any MCP-capable client (Claude Code, Cursor, VS Code, and others) to deliver messages into a local DeepSeek Harness over stdio or Streamable HTTP. It also exposes a pull-based task queue so producers can publish work that clients claim, complete, or list.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A 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.
      299 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Connects an MCP client such as Codex to a running DeepSeek Harness instance, letting it start or continue workspace conversations as delegated tasks, poll task status, answer intercepted questions, and cancel turns. Agent progress, findings, and blockers flow back to the coordinator through a durable on-disk mailbox.
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables MCP-compatible clients to delegate complex multi-step programming and research goals to coordinated teams of specialized subagents, with cross-session messaging, swarm and pipeline workflows, sandboxed workspace tools, persistent SQLite state, and a live dashboard.
      22
      74 npm
      1
      MIT

    TDQS

    A4.2/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools target a clearly distinct lifecycle action (start/send/read/get/interrupt/release), and the descriptions aggressively cross-reference the sibling tool to disambiguate (read vs get, status vs list, inbox vs approval_decide vs review). The residual overlap is small but real: dsh_send(queue=true), dsh_interject(queue), and dsh_interrupt all touch 'steering a running turn', and dsh_release vs dsh_interrupt both stop work — an agent has to read carefully to pick correctly.

    Naming Consistency5/5

    Every tool uses the same dsh_ prefix plus a lowercase action word (start, send, read, get, list, status, interrupt, release, doctor). No camelCase or mixed verb styles anywhere; the surface reads as one predictable namespace.

    Tool Count4/5

    15 tools sits at the top of the well-scoped band, and the domain (managing long-lived async coding-agent conversations with locks, queues, approvals and reviews) genuinely needs most of them. A few, such as dsh_doctor and dsh_takeover, are narrow operational escapes that most sessions never touch, pushing it slightly past lean.

    Completeness4/5

    The lifecycle is well covered end to end: create, dispatch, watch live output, collect results, steer, stop, queue management, approvals, review verdicts, lock preemption, release/forget, and health checks. Gaps are minor — no way to change a conversation's configuration (workspace, permission tier, profile) or to enumerate past runs beyond the in-memory 20 / sentinel file, so history and reconfiguration require working around the surface.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data