# nomarmy

Source: https://glimind.com/server/npm%2Fnomarmy
Registry id: `npm/nomarmy`
Status: unknown

## Install

```json
{
  "mcpServers": {
    "nomarmy": {
      "command": "npx",
      "args": [
        "-y",
        "nomarmy"
      ]
    }
  }
}
```

Claude Code:

```sh
claude mcp add nomarmy -- npx -y nomarmy
```

## Tools (16)

- `army`
- `local_worker`
- `local_worker_capacity`: What this host can take right now: context per nom and the brief/report budgets derived from it, memory pressure and whether another job would be admitted, and 
- `local_worker_cleanup`
- `local_worker_config`
- `local_worker_jobs`
- `local_worker_start`: Start one worker or scout in the background and return immediately with a job_id. Poll it with local_worker_status (optionally long-polling with wait_seconds). 
- `local_worker_status`
- `local_worker_stop`: Stop a running job's worker, for example one burning a frontier model's usage on the wrong track. Its worker ends within about 15 seconds, without the report-re
- `local_worker_sweep`
- `local_workers`
- `repo_evidence`: Deterministic repository evidence with exact [path:line] citations and no model involved. ops: ${EVIDENCE_OPS.join(", ")}. definitions/references take a symbol 
- `run_finish`: Close a /feature run as complete or stopped, with a one-paragraph summary. A closed run admits no more jobs. Nothing is merged: the run's branch still waits for
- `run_start`
- `run_status`: A /feature run's limits, what it has used (jobs, api spend, hours), per-agent jobs/spend/tokens, warnings (80% of a limit, paused agents), and its log path. Rea
- `stats`

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.