agent-pool-mcp
Related Servers
Alternatives to agent-pool-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceAn orchestration server that enables AI agents to collaborate across multiple AI models for advanced code analysis, debugging, and development workflows. It maintains context persistence across sessions, allowing agents like Claude to delegate subtasks to other models like Gemini or O3 seamlessly.42-
- AlicenseNot gradedqualityAmaintenanceProvides a provider-agnostic MCP server that coordinates structured multi-agent workflows, owning task claims, action logs, handoffs, and server-side health gates for coding agents. It enables tracked specs, tasks, reviews, and verified completion across Claude Code, Codex CLI, Cursor, Grok Build, and OpenCode.29 npmMIT
- 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 gradedqualityAmaintenanceEnables AI coding providers to run structured multi-agent workflows with document specifications, tracked tasks, handoffs, and server-owned health evidence. It coordinates task claims, repairs, reviews, and completion gates across Claude Code, Codex CLI, Cursor, Grok Build, and OpenCode.29 npmMIT
- AlicenseAqualityAmaintenanceOrchestrates multiple AI coding agents declaratively to automate software development workflows for engineering teams.1238,833 PyPI1,330Apache 2.0
- FlicenseNot gradedqualityCmaintenanceMulti-model agent orchestration MCP server that enables plan-code-review-deliver pipelines with configurable providers and models.-
TDQS
Scored across 42 tools
Most tools have distinct purposes, but delegate_task and delegate_task_readonly are very similar, differing only in intent signal. The large number of tools (42) introduces some risk of confusion, though descriptions are clear.
Tool names consistently follow a verb_noun pattern (e.g., get_pipeline_status, create_skill, list_groups). Only minor deviations like bounce_back, but overall the pattern is clear and predictable.
With 42 tools, the set is quite large for a single server. While each tool serves a specific purpose, the count exceeds the typical well-scoped range (3-15). It may overwhelm agents, but the complexity of the domain partially justifies the number.
The tool surface covers core workflows: delegation, pipelines, scheduling, groups, skills, workflows, messaging, and file tracking. Minor gaps exist, such as missing update/delete operations for pipelines and groups, but the set is generally comprehensive.