ClaudeArmy
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ClaudeArmy Refactor GarbageFire to be more modular, and add a Salesforce adapter to my Reporting Tool"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
🪖 ClaudeArmy
An MCP server that lets Claude orchestrate multiple Claude Code agents working autonomously across different projects.

What It Does
ClaudeArmy gives Claude (in the chat interface) the ability to spawn background Claude Code processes that work independently on coding tasks. Think of it as a chain of command:
You → give strategic direction
Claude (chat) → breaks it down and dispatches agents
Claude Code agents → execute autonomously, spawning their own sub-agents as needed
This means you can kick off work across multiple projects simultaneously, keep chatting normally, and check in on progress whenever you want.
Related MCP server: cc-agent
Tools
Tool | Description |
| Deploy a Claude Code agent to a project directory. Supports |
| Monitor status of all running/completed agents |
| Retrieve what an agent did and its full output |
| Detailed view of a lead agent and all its sub-agents |
| Stop a running agent gracefully |
| Clean up completed/failed tasks |
Setup
Clone this repo
npm installAdd to your Claude Desktop config:
Linux:
~/.config/Claude/claude_desktop_config.jsonmacOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
"claude-army": {
"command": "node",
"args": ["/path/to/claude-army/src/index.js"]
}Windows note: Use forward slashes in the path value (e.g.
"C:/Users/you/claude-army/src/index.js").
Restart Claude Desktop
Usage Examples
Single project task:
"Refactor GarbageFire's app.py into modular components"
Multi-project parallel work:
"Refactor GarbageFire to be more modular, and add a Salesforce adapter to my Reporting Tool"
Claude will dispatch separate agents to each project directory and let them work autonomously.
Check progress:
"How are the agents doing?"
Agent Teams
Use mode: "team" on dispatch_task to have the lead agent automatically decompose work and spawn specialized sub-agents that run in parallel.
How it works:
The lead agent analyzes the task and breaks it into focused subtasks
Each subtask is delegated to a sub-agent via Claude Code's
TasktoolSub-agents work in parallel, each with a well-defined scope
The lead agent synthesizes results once all sub-agents complete
Monitoring teams:
check_tasksshows a sub-agent summary (e.g. "3 sub-agents: 1 running, 2 completed")get_agent_teamgives a detailed tree view of the lead agent and every sub-agent, including status, runtime, and output previews
Configuration
Edit the constants at the top of src/index.js:
CLAUDE_BINARY- Path to your Claude Code binaryMAX_CONCURRENT_TASKS- Max simultaneous agents (default: 5)
Requirements
Claude Code installed and authenticated
Node.js 18+
Claude Desktop or any MCP-compatible client
Changelog
v0.4.1
Bump
@modelcontextprotocol/sdkto ^1.26.0, resolving 3 high severity supply chain vulnerabilitiesAdd
repositoryfield to package.json
v0.4.0
Agent team support: track sub-agents spawned via Claude Code Task tool
New
get_agent_teamtool: tree view of lead + all sub-agentscheck_tasksnow shows sub-agent summary for team operationsdispatch_taskgainsmodeparameter:solo(default) orteamCross-platform: fixed Windows binary (
claude.cmd) and signal handlingError messages now show platform-appropriate diagnostic commands
README: added setup paths for Linux, macOS, and Windows
v0.3.0
Fixed stream-json parsing to correctly handle assistant message content arrays
Staleness indicator:
check_tasksnow shows time since last agent activityBetter error surfacing: actionable messages for CLI not found, permission denied, and mid-run failures
Fixed output duplication in
get_task_outputDemo GIF added to README
v0.2.0
Real-time progress tracking via Claude Code's stream-json output
check_tasksnow shows recent agent activity (file reads, edits, bash commands) instead of just runtimeget_task_outputincludes a full progress timeline with timestampsStructured event parsing for tool use, assistant messages, and results
v0.1.0
Initial release
Core tools: dispatch_task, check_tasks, get_task_output, cancel_task, purge_tasks
Fire-and-forget architecture with background process management
Max 5 concurrent agents
stdio transport for MCP communication
License
MIT
Available Tools
6 toolscancel_taskA
Cancel a running Claude Code agent task. Sends SIGTERM to gracefully stop the agent.
Inputs: task_id (required).
check_tasksA
Check the status of all deployed Claude Code agents. Shows which tasks are running, completed, or failed. Use this to monitor progress of background agents.
Inputs: status_filter.
dispatch_taskA
Deploy a Claude Code agent to work on a task in a specific project directory. The agent runs autonomously with full Claude Code capabilities including sub-agent spawning, file editing, bash execution, etc. Use this to delegate coding tasks to background agents. IMPORTANT: After dispatching, return to the conversation immediately. Do NOT call check_tasks or get_task_output unless the user explicitly asks for a status update.
Inputs: task (required), working_directory (required), mode, model, +1 more.
get_agent_teamA
Get a detailed view of a lead agent and all sub-agents it has spawned. Use this when a task is using Claude Code agent teams to see the full picture of what each sub-agent is doing, their status, and output previews. More detailed than check_tasks for multi-agent operations.
Inputs: task_id (required).
get_task_outputA
Retrieve the full output from a Claude Code agent task. Use this to see what the agent did, including its reasoning and actions taken.
Inputs: task_id (required), tail_lines.
purge_tasksA
Clear completed/failed tasks from the task list. Optionally clear all tasks (cancels running ones).
Inputs: include_running.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
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.
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.
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.
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
Related MCP Connectors
Shared memory MCP server for Claude Code, Codex, Gemini CLI and Cursor. Cited, editable.
MCP server for building and testing AI agents with multi-model experimentation and insights.
Augments MCP Server - A comprehensive framework documentation provider for Claude Code
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Related MCP 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
- AlicenseAqualityDmaintenanceMCP server that spawns autonomous Claude Code agents in GitHub repos, enabling task delegation with persistent state, multi-step workflows, and job monitoring.4729 npm2Apache 2.0
- AlicenseAqualityFmaintenanceAn MCP server for coordinating multiple Claude Code sessions across related projects.11MIT
- 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.107 npmMIT