Skip to main content
Glama
zkonikishi

Codex DSH MCP

by zkonikishi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Codex DSH MCP

No user-submitted related servers found.

    Related Servers

    • deepseek_harness

      XiangyunHu
      A
      license
      A
      quality
      B
      maintenance
      A task-level STDIO MCP server that lets Codex or any other MCP client hand off scoped coding jobs to an asynchronous worker agent which reads the code, edits files, and runs tests, while the client keeps ownership of planning and acceptance. Exposes submit, wait, query, follow-up, and cancel tools so multiple clients can queue and monitor tasks against a chosen project root.
      5
      1
      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-bridge-mcp

      jiuyue970
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables Codex to delegate coding tasks to DeepSeek Harness (DSH) for file reading, editing, and checking, while Codex handles planning and review. It manages scheduled workflows with concurrency safety and acceptance evidence.
      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

    B3.3/5.0

    Scored across 15 tools

    Disambiguation3/5

    Several tools have overlapping read/status or dispatch purposes, such as workflow_status vs review_pending and workflow_dispatch vs dsh_prompt. The detailed descriptions clarify most boundaries, but an agent relying on tool names alone could easily misselect within these clusters.

    Naming Consistency3/5

    The prefix families workflow_, review_, dsh_, and codex_ provide some structure, but the verb/noun pattern is mixed: status, history, sessions, and pending are noun-style, while dispatch, archive, bind, complete, and wait are verb-style. All names are readable snake_case, but there is no consistent verb_noun convention.

    Tool Count4/5

    At 15 tools, the count is at the upper bound of the typical range but is largely justified by the broad Codex/DSH/review workflow scope. A few read-only DSH inspection tools could potentially be consolidated, but none feel wholly redundant.

    Completeness3/5

    The core workflow lifecycle—bind/dispatch, status, review, and archive—is largely covered, and DSH inspection/history/wait tools support observation after submission. However, there is no terminal failure/reject/cancel path, since workflow_archive only handles accepted records and bounded rework does not model permanently failed work.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources