Skip to main content
Glama

Related Servers

Alternatives to colmena-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables multiple AI coding CLIs (Claude Code, Gemini/Antigravity, Codex, and OpenCode) to collaborate as a coordinated team by routing cross-agent prompts, sharing messages and review tickets, tracking tasks on a shared store, and isolating each agent in its own Git worktree with turn-budget safeguards—all inspectable and steerable from a local web dashboard.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude to hand scoped, implementation-only coding tasks to any model available in a local opencode install — including Kimi, GPT, Gemini and local models — and to run many of them in parallel. Claude stays the orchestrator: it briefs each worker, collects results and needs-flags, then reviews diffs and runs tests, lint and builds itself.
      1
      MIT
    • 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
      B
      maintenance
      Enables Claude Code to delegate coding jobs to cheaper or free models through opencode while staying the sole interface, relaying permission requests and questions back to the user and running multiple jobs in parallel git worktrees with diff review, verification, cost caps, and merge checks.
      1,479 npm
      MIT

    TDQS

    B3/5.0

    Scored across 17 tools

    Disambiguation4/5

    The set clearly separates most orchestrator actions, but summarize vs compact and wait vs result share reporting/summarization duties, and run/handoff/continue form a related launch-resume family. The descriptions usually resolve these overlaps, though a few boundaries require careful reading.

    Naming Consistency4/5

    Names are consistently lowercase and mostly single words, mixing imperative verbs (run, cancel, merge) with resource nouns (workers, status, result) in a readable way. The only multi-word name, run_many, uses snake_case cleanly, so the convention is predictable despite the verb/noun mix.

    Tool Count4/5

    17 tools is slightly above the ideal 3–15 range, but the agent-orchestration domain is broad and each tool maps to a distinct lifecycle action. No tool is clearly redundant, though a leaner design could combine some summary/reporting operations.

    Completeness4/5

    The surface covers the orchestration lifecycle well: delegation, parallel runs, handoff, monitoring, cancellation, review, merge, cleanup, reporting, and session summarization/compaction. Minor gaps include no tools for inspecting raw job logs or configuring worker budget/priority settings, but agents can mostly work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data