Skip to main content
Glama
Sign In
subtask

subtask

by tedin7
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to subtask

No user-submitted related servers found.

    Related Servers

    • arjun-mcp

      quantumthoughter
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables host agents to launch and supervise durable, long-horizon AI jobs—starting, running, resuming, checking budgets, and inspecting assembled context—so tasks can survive restarts and outlive the conversation with verified completion.
      MIT

    • cursor-agents-mcp

      6e6p1k
      A
      license
      A
      quality
      C
      maintenance
      Enables an orchestrator like Claude Code to hand coding work off to Cursor SDK agents, run as detached background jobs that survive the session and can be listed, inspected, steered, resumed, or stopped. Agents are asynchronous and reusable across follow-up turns, letting expensive frontier models delegate cheaply without blocking or paying to read the results.
      7
      MIT

    • vanth

      holdfast-labs
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to launch, monitor, and manage background shell jobs with durable event tracking, live progress dashboards, and wake-on-attention for interactive sessions.
      1
      Apache 2.0
    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

    C2.8/5.0

    Scored across 18 tools

    Disambiguation3/5

    Most tools target distinct workflow stages, but several boundaries blur: plan versus start/start_many, status versus result/wait/inspect, cleanup versus integrate discard, and general start_many versus specialized consensus/map_reduce. The detailed descriptions help, but an agent could still misselect among orchestration and monitoring tools.

    Naming Consistency3/5

    All names are lowercase snake_case, which is readable, but the convention mixes bare verbs (start, wait, stop, steer) with nouns (status, result, jev, consensus, engines) and does not follow a predictable verb_noun pattern. Two snake_case compound names exist, but semantic naming is inconsistent.

    Tool Count4/5

    Eighteen tools is slightly above the typical well-scoped range, but the server supports a complex orchestration domain with jobs, worktrees, reviews, and specialized workflows. The count is reasonable and most tools appear to earn their place.

    Completeness4/5

    The surface covers job creation, monitoring, steering, stopping, cleanup, integration, review, policy, bisect, consensus, map_reduce, and quota. Minor gaps exist, such as unclear explicit job deletion or group cancellation semantics, but core lifecycle workflows are represented.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources