ClaudeArmy
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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. |
| 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. |
| 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. |
| cancel_taskA | Cancel a running Claude Code agent task. Sends SIGTERM to gracefully stop the agent. |
| purge_tasksA | Clear completed/failed tasks from the task list. Optionally clear all tasks (cancels running ones). |
| 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/robbhimself-1337/claude-army'
If you have feedback or need assistance with the MCP directory API, please join our Discord server