Skip to main content
Glama
Sign In
deepseek_harness

deepseek_harness

by XiangyunHu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to deepseek_harness

No user-submitted related servers found.

    Related Servers

    • TodoServer

      loki495
      A
      license
      Not graded
      quality
      B
      maintenance
      A host-local stdio MCP server that lets AI agents read and create tasks, comment, and run a full claim/heartbeat/release/complete lifecycle with automatic process identification, all through local-first actions that sync to a task workspace without exposing a GitHub token.
      MIT

    • t2a mcp

      isnotry
      A
      license
      Not graded
      quality
      B
      maintenance
      Exposes a local-first task board over stdio JSON-RPC so MCP-capable agents can list and create projects and tasks, atomically claim the next ready task with a lease, heartbeat, log progress, manage dependency graphs, and mark tasks done or failed with results. All state lives in a single local SQLite file, so no shell command assembly or external services are needed.
      MIT

    • Standalone Agent Orchestrator

      muratangin187
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients to delegate work to nested subagents running on Codex and Claude Code, keeping each task's session, turn history and results durable in SQLite while the main chat continues. Supports async or blocking waits, mid-session context updates, git worktree isolation, read-only-by-default permission inheritance, and cancelling whole subagent trees.
      MIT

    • codex-exec-mcp

      JaegerY
      A
      license
      Not graded
      quality
      C
      maintenance
      Lets Claude and other MCP clients hand coding tasks to the Codex CLI as a sub-agent, running under the user's own Codex configuration so any configured model provider (OpenAI, DeepSeek, local models) does the work. Provides tools to start, poll, cancel and inspect jobs with compact change summaries, long-task handling, token-saving lean mode and clean process teardown.
      MIT

    • hanako-codex-bridge

      TheEarlyWinter
      A
      license
      Not graded
      quality
      B
      maintenance
      A local stdio MCP server that lets Hanako and Codex delegate one-off or persistent text tasks to each other, check local service and executable status, and manage bounded concurrent delegations without exposing tokens or paths.
      MIT

    • swarm-engine

      PRIYAGDEV
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to spawn, parallelize, and synchronize multi-agent programming swarms through a stdio MCP interface. Provides tools for DAG-scheduled task dispatch, isolated Git worktree execution, atomic file locking, shared blackboard memory, and clean merging of completed agent work back to the main repository.
      1 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

    A3.5/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool maps to a clearly distinct lifecycle action: start (submit_task), read (get_task), wait (wait_task), interact (continue_task), and stop (cancel_task). The descriptions clarify subtle differences such as immediate read versus waiting for events, and starting a new task versus continuing an existing session.

    Naming Consistency5/5

    All five tool names follow a consistent snake_case verb_noun pattern: submit_task, get_task, wait_task, continue_task, cancel_task. There are no deviations or mixed conventions.

    Tool Count5/5

    Five tools is well-scoped for a task harness, covering the essential lifecycle operations (start, monitor, wait, continue, cancel) without redundancy or missing core actions. Each tool earns its place.

    Completeness4/5

    The core task lifecycle is covered: submission, status retrieval, waiting, feedback continuation, and cancellation. However, there is no list_tasks operation to discover queued or running tasks, and no delete/archive operation, which are minor gaps that agents can work around if task IDs are known.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues

    Resources