Skip to main content
Glama
Sign In
DOT DeepSeek Harness MCP

DOT DeepSeek Harness MCP

by xuanmingguo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to DOT DeepSeek Harness MCP

No user-submitted related servers found.

    Related Servers

    • codex-reasonix-bridge

      qjgoisz
      A
      license
      Not graded
      quality
      B
      maintenance
      Persistently connects Codex to Reasonix Studio so Codex can plan and verify while Reasonix executes, delegating tasks across shared multi-client sessions. Keeps tasks, sessions, approvals, results, and artifact fingerprints durable, with idempotent submission, workspace queuing, session reuse and recovery, manual adjudication of unknown outcomes, explicit retries, cancellation, and bounded shutdown.
      GPL 3.0

    • web-gpt-agent-core

      dbc-hbin
      A
      license
      Not graded
      quality
      B
      maintenance
      Connects ChatGPT Web to a local development environment, enabling file reads and patches, shell execution, plan updates, and isolated worktree coordination through permissioned MCP tools.
      6
      MIT

    • harness-relay-mcp

      ksoulness
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables Codex to delegate scoped tasks to a local DeepSeek Harness over MCP — dispatching read-only reviews or authorized workspace writes, steering and monitoring runs to a terminal state, and returning structured evidence such as changed paths, test results, and assistant text. It also supports exact archival of the terminal session by full session ID.
      1
      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

    • DSH Desktop MCP Bridge

      linglanxin
      A
      license
      Not graded
      quality
      B
      maintenance
      Lets Codex delegate tasks to a running DeepSeek Harness Desktop instance on Windows over authenticated named pipes, with asynchronous dispatch, event waiting, cancellation, and explicit resume. Also supports blocking structured questions tied to a task, plan checkpoints before writes, independent stage review with rework in the same session, and output fingerprinting that invalidates stale approvals when files change.
      453 npm
      1
      MIT
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    B3.4/5.0

    Scored across 48 tools

    Disambiguation3/5

    Most tools target distinct lifecycle stages, but several pairs overlap meaningfully: get_run/get_run_summary/status_run (the latter a deprecated alias explicitly kept), list_runs/list_run_summaries, read_artifact/read_scoped_artifact, and the diagnostic trio doctor/harness_health/setup_doctor. The descriptions do a good job of drawing the boundaries (e.g. queue_run says 'Distinct from steer_run'), and stop_service's name actively misleads about its behavior, but an agent can navigate it with careful reading.

    Naming Consistency4/5

    The dominant pattern is snake_case verb_noun (start_run, get_run, list_runs, wait_run, cancel_run, steer_run), applied consistently across the run/session/deployment families. Minor deviations exist in noun-only names (doctor, harness_health) and a few unusual compounds (close_run_terminals, retry_run_with_fallback), but nothing chaotic.

    Tool Count2/5

    48 tools is heavy even for a large orchestration domain covering runs, session history, file reads, deployment, setup, and diagnostics. Duplicates that earn no new capability — status_run as a deprecated alias, two artifact readers, three-plus diagnostic tools, many list/read variants — push this well past the justified surface.

    Completeness5/5

    The surface covers the domain comprehensively: run creation (start_run/start_review), continuation (reply_run/steer_run/queue_run), cancellation, polling/readback (wait_run/get_run/summaries), queue management, session history search and context, scoped project/artifact reads, deployment plan-to-execute, permission reconciliation, and operation idempotency records. No obvious dead ends for the stated harness-management purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources