A
licenseA
qualityD
maintenanceMCP server that spawns autonomous Claude Code agents in GitHub repos, enabling task delegation with persistent state, multi-step workflows, and job monitoring.
47
187 npm
2
Apache 2.0
ClaudeArmy
Related Servers
Alternatives to ClaudeArmy
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables multiple Claude Code agents to communicate, share messages, specs, and statuses, solving coordination problems across different workspaces.2MIT
- FlicenseAqualityFmaintenanceAn MCP server for coordinating multiple Claude Code sessions across related projects.11-
- AlicenseNot gradedqualityCmaintenanceAn MCP server that lets any MCP-capable agent spawn and drive Claude Code sessions — effectively turning Claude Code into an orchestratable sub-agent fleet.72 npmMIT
- FlicenseNot gradedqualityCmaintenanceA local MCP server that coordinates Claude Code CLI as subagents, providing tools to spawn, message, wait for, and interrupt agents.-
- AlicenseNot gradedqualityBmaintenanceMCP server that provides cross-session awareness for Claude Code, tracking active sessions, file conflicts, and shared todos to enable agent coordination without blocking tool calls.860 npmMIT
TDQS
A4.1/5.0
Scored across 6 tools
Disambiguation4/5
The tools are mostly distinct: dispatch_task creates, check_tasks monitors overall status, get_task_output retrieves output, cancel_task stops, purge_tasks cleans up, and get_agent_team drills into team hierarchy. However, check_tasks and get_agent_team both report status, with get_agent_team being more detailed, so there is minor potential for misselection.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern with underscores, such as check_tasks, get_task_output, and dispatch_task. The verbs are clear and related to task management, and the minor pluralization difference (task vs tasks) does not affect readability.
Tool Count5/5
Six tools is well within the ideal range for a focused task-management server. Each tool corresponds to a distinct action in the agent lifecycle—dispatch, monitor, retrieve, cancel, purge, and team inspection—so none feel redundant or missing.
Completeness4/5
The server covers the core lifecycle of Claude Code agents: creation (dispatch_task), status monitoring (check_tasks, get_agent_team), output retrieval (get_task_output), cancellation (cancel_task), and cleanup (purge_tasks). Minor gaps include no explicit retry or update mechanism, and get_agent_team only applies to team-based tasks, but the primary workflows are covered.
Maintenance
ActivityInactive
ResponsivenessNo issues