Skip to main content
Glama
xmtlzzz

dsh-any-agent

by xmtlzzz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to dsh-any-agent

No user-submitted related servers found.

    Related Servers

    • dsh-mcp

      Moer2831
      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.
      325 npm
      15
      MIT

    • dsh

      xDJTomato
      A
      license
      Not graded
      quality
      A
      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.
      MIT

    • dsh-mcp-connector

      ganmayou2333
      A
      license
      Not graded
      quality
      A
      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

    • dsh-bridge

      controlledentropy
      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.
      288 npm
      MIT

    • DSH_MCP

      greatZhaoFD
      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

    • MCP Agent Orchestrator

      ShashankIIITN
      A
      license
      Not graded
      quality
      A
      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.
      1
      MIT
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A4.1/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools target clearly distinct operations (start, send, interrupt, release, takeover, approval_decide), but there is real overlap between dsh_get, dsh_status, and dsh_read — all report on a session's state/output — and between dsh_interject (interrupt mode) and dsh_interrupt. The descriptions do disambiguate these (read=cursor-based live output, status=lightweight check, get=full detail/run result), so confusion is limited but not zero.

    Naming Consistency4/5

    All names use a consistent dsh_ prefix with snake_case, and 9 of 11 follow a clean verb style (start, send, release, list, read, get, interject, interrupt, takeover). The deviations — dsh_approval_decide (noun_verb) and dsh_status (noun) — are minor and still readable.

    Tool Count5/5

    11 tools is well within the sweet spot for a session-management server, and each tool maps to a distinct lifecycle concern: create, dispatch, observe, steer, cancel, reclaim, and approve. Nothing feels redundant in count.

    Completeness4/5

    The lifecycle is well covered: create, send, list, read, get, interject, interrupt, release (with forget), takeover, and approval handling, plus auto-resume via ACP. Minor gaps: no explicit resume/open tool, no way to change a session's permission profile or on_approval setting after creation, and no delete/purge beyond release+forget.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources