colmena-mcp
Related Servers
Alternatives to colmena-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables 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
- AlicenseNot gradedqualityBmaintenanceEnables 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
- FlicenseNot gradedqualityAmaintenanceEnables a primary AI coding assistant to delegate tasks to specialized sub-agents in parallel, share project context, and synthesize their responses. It uses existing local CLI tools and API subscriptions to coordinate Codex, Claude, Cursor, and Gemini without extra cost.-
- FlicenseNot gradedqualityDmaintenanceCoordinates multiple Claude Code agents to work collaboratively on projects with role-based task management, shared state, and automated code review.21 npm2-
- AlicenseNot gradedqualityCmaintenanceTurns Claude Code into an engineering project manager by orchestrating feature development with isolated Git worktrees, structured task validation, and approval-gated integration.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude Code to launch and supervise multiple concurrent Claude Code sessions in tmux, sending them briefs, reading their progress, answering their prompts, and managing isolated git worktrees.2MIT
TDQS
Scored across 17 tools
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.
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.
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.
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.