
Claude Army
io.github.robbhimself-1337Published by GitHub account robbhimself-1337v0.3.1Updated Oct 24, 2026
Orchestrate multiple Claude Code agents in parallel from chat
The publisher's own server: Claude Platform Docs
Overview
Local MCP server that lets Claude dispatch and monitor multiple autonomous Claude Code agents working in parallel across project directories.
- What you can do
- Dispatch Claude Code agents to project directories, optionally in team mode where a lead agent splits work into parallel sub-agents
- Monitor status of running and completed agents, including sub-agent summaries
- Retrieve an agent's full output and what it did
- Inspect a lead agent and its sub-agent tree with status, runtime and output previews
- Cancel a running agent gracefully or purge finished and failed tasks
- When to use it
- Useful when you want to kick off coding work across one or several projects at once, keep chatting normally, and check back on progress later. Best for users already working with Claude Code who want parallel, autonomous task execution from the chat client.
- Requirements
- Runs as a local stdio process installed from the npm package claude-army (or cloned repo with npm install) and configured in the Claude Desktop config file. Needs Node.js 18+, Claude Code installed and authenticated, and an MCP-compatible client such as Claude Desktop. The Claude Code binary path and max concurrent tasks (default 5) are set as constants in the source file.
Installation
In SourceWeft
- Open Claude Army in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
🪖 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.
Tools
Setup
-
Clone this repo
-
npm install -
Add to your Claude Desktop config:
- Linux:
~/.config/Claude/claude_desktop_config.json - macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
- Linux:
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
Tasktool - Sub-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 vulnerabilities - Add
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-agents check_tasksnow shows sub-agent summary for team operationsdispatch_taskgainsmodeparameter:solo(default) orteam- Cross-platform: fixed Windows binary (
claude.cmd) and signal handling - Error 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 activity - Better error surfacing: actionable messages for CLI not found, permission denied, and mid-run failures
- Fixed output duplication in
get_task_output - Demo 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 timestamps- Structured 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
Source: README.md at commit 64212fb
Tools
0Version history
1- v0.3.1LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.
Other Claude integrations
Claude Platform Docs
com.claude.platformOfficial publisher
Remote MCP server that lets an assistant search and read the Claude Platform documentation and API reference.

Insta Edits for Claude
Published by GitHub account faisalkhanzemi
Bridge that lets Claude drive the full 274-tool editor in Instagram Edits for Mac, keeping the tool list in sync as projects open.

Claude Checkpoint Mcp
Published by GitHub account daniel-munoz
Local MCP server that saves Claude Code session state to a checkpoint file in the project and reloads it as a compact resume brief.

Qwen DAP MCP — C/C++ Debugger for Claude Code, Codex & Qwen
Published by GitHub account spk-c
Qwen DAP MCP — C/C++ Debugger for Claude Code, Codex & Qwen's local MCP server; no sign-in required; STDIO; 18 tools.

AVE for Claude Code — Local Video Editing
Published by GitHub account lemberalla
Local AVE timeline editing and exports for Claude Code only. Existing AVE connection required.