Skip to main content
Glama
Sign In
dsh-mcp-worker

dsh-mcp-worker

by tongsh6
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to dsh-mcp-worker

No user-submitted related servers found.

    Related Servers

    • Codex Local Ops

      hattimon
      A
      license
      D
      quality
      C
      maintenance
      Enables controlled local developer operations including file and process management, shell execution, SSH, WSL, Docker, Git, browser and desktop automation, media processing, and asynchronous jobs through MCP.
      146
      MIT

    • muster

      BrutalSystems
      A
      license
      B
      quality
      B
      maintenance
      Enables launching and supervising local Codex and Claude Code agent sessions and one-shot tasks, exposing run, list, stop, and output operations over MCP with session-scoped permissions and sandbox controls.
      2
      336 npm
      1
      MIT

    • CodePier

      cyeinfpro
      A
      license
      Not graded
      quality
      B
      maintenance
      Connects ChatGPT and MCP clients to authorized local development environments, enabling secure file access, shell execution, persistent tasks, browser/desktop control, and remote management of projects.
      19
      MIT

    • astra_dsh

      Gagelee
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables Codex/Astra to hand off complete task packets to DSH for real execution in a shared local workspace, with progress, tool calls, questions, and results written back to a shared .astra-dsh task board. Supports blocking waits, queued follow-up instructions, interrupts, cancellation, rework requests, and independent verification or diff review of the resulting changes.
      1
      MIT

    • agent-talk

      YanZiBin
      A
      license
      A
      quality
      C
      maintenance
      A local MCP bridge that connects existing Codex and Claude Code conversations with DSH Web, enabling delegation, result retrieval, and human-in-the-loop coordination without leaving native chat apps.
      11
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 13 tools

    Disambiguation4/5

    The lifecycle tools (run/status/result/cancel) and their batch counterparts (batch_run/batch_status/batch_result) are clearly separated by purpose. Minor overlap exists between dsh_result and dsh_read_result, and between dsh_tasks and dsh_search, but descriptions make the boundaries clear.

    Naming Consistency5/5

    All tools use a consistent dsh_ prefix with snake_case verb_noun patterns (dsh_run, dsh_status, dsh_batch_run, dsh_read_result). The batch family mirrors the single-task family predictably.

    Tool Count5/5

    13 tools is well within the ideal 3-15 range and each earns its place: core lifecycle, batch orchestration, result reading, search, audit, metrics, and introspection.

    Completeness5/5

    The surface covers the full async task lifecycle: submit, poll, fetch result, cancel, batch dispatch/status/result, large-output pagination, search, audit trail, metrics, and worker introspection. No obvious dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data

    Resources