Skip to main content
Glama

Related Servers

Alternatives to subagent-swarm-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables a primary AI coding assistant to delegate tasks to multiple specialized CLI-based sub-agents in parallel, share project context, and synthesize their responses into a single result. It supports using existing subscriptions and local tools without extra markup.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables users to delegate coding tasks in a chosen project to the official Codex and Claude CLI agents from within an existing chat, then convene a council of configured models to gather independent opinions and review the resulting files and test runs. It also manages multi-provider API connections, model catalogs, and per-task token, time, and cost limits.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables hosts like Claude Code, Codex, Antigravity and Grok to dispatch tasks to DeepSeek Harness agents that appear as native subagents with live progress and token stats. It provides tier and effort selection, escalation and dispatch guardrails, a jobs board, in-host or standalone worker sessions, plus a multimodal bridge that lends text-only models vision and image generation.
      354 npm
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables Claude Code and Claude Desktop to delegate bounded, disposable tasks to local or cheap cloud models, with model scoring, guardrails, and cost-saved tracking.
      53
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables coordinating local coding agents across Antigravity, DeepSeek Harness, Claude Code, and OpenCode with persistent tasks, live public events, file-change artifacts, session follow-ups, process-tree cancellation, and configurable execution permissions.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding providers to run structured multi-agent workflows with tracked tasks, document specifications, handoffs, health gates, and server-owned evidence across providers like Claude Code, Codex CLI, Cursor, Grok Build, and OpenCode.
      29 npm
      MIT

    TDQS

    B3.1/5.0

    Scored across 42 tools

    Disambiguation2/5

    Two large families duplicate each other almost one-for-one: zcode_run/swarm_run, zcode_wait/swarm_wait, zcode_result/swarm_result, zcode_status/swarm_status, zcode_list/swarm_list, zcode_cancel/swarm_cancel, zcode_followup/swarm_followup, zcode_quota/swarm_quota, plus zcode_run_structured vs swarm_run_structured and zcode_structured_result vs swarm_structured_result. There are also three blocking 'wait' tools (hub_wait, zcode_wait, swarm_wait) and multiple progress-inspection paths (hub_log, hub_show, zcode_status, zcode_progress) whose boundaries an agent must infer from dense prose. Descriptions do try to draw lines (e.g. swarm_run subsumes zcode as a backend), but the overlap is severe enough to cause frequent misselection.

    Naming Consistency3/5

    Within each prefix the verb_noun pattern holds (hub_post/hub_board/hub_show, zcode_run/zcode_wait/zcode_result, swarm_run/swarm_status), and prefixes are used consistently as namespace markers. However, the namespaces themselves are not parallel: the same operations exist under both zcode_* and swarm_*, and one tool (codebuddy_usage) is named after a backend while the equivalent exists as swarm_quota, so the scheme doesn't tell an agent which prefix to reach for.

    Tool Count2/5

    42 tools for what is essentially task delegation, monitoring, structured/batch runs, a dispatch hub, and session log reading. Roughly fifteen of those are near-aliases of others, so the count is inflated well beyond the real surface area. The hub_* group is reasonably scoped on its own, but the overall set is too large for the domain.

    Completeness4/5

    The lifecycle is well covered: submit (swarm_run/zcode_run/hub_post), observe (status/board/log/progress), block (wait), collect (result/structured_result), continue (followup/hub_answer/hub_tell), stop (cancel), recover (requeue/batch status), and cost (quota/usage) all exist, plus session-log forensics. Gaps are minor, e.g. there is no operation to archive/delete a hub task or to enumerate the worker roster directly (hub_assign only points at it).

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues