nomArmy MCP server

Every byte verified. 🍪

nomarmy.dev · Docs · Sponsor

Your coding assistant plans; sandboxed workers build; nothing counts until nomArmy has checked it.

AI coding workers are confident. Their "done, all tests pass" is a claim, not evidence. nomArmy lets your coding assistant (Claude Code, Codex or Cursor) hand work to workers called noms, then checks every change itself before anything is committed: the real diff, your tests run in a fresh sandbox, a check that those tests actually catch the change, and a secret scan.

TL;DR

Windows is supported with the engine in WSL2. Follow the Windows setup.

1. Have Git, Node 24.16+ (or 26.1+), Podman, and Claude Code, Codex or Cursor installed and signed in. On macOS, give Podman 8 GiB: brew install podman && podman machine init --memory 8192 && podman machine start.

1. Install and set up:

npm install -g nomarmy
   cd your-project
   nomarmy setup

nomarmy setup is a playbook. It shows a checklist and runs the next step each time you say yes:

✓ Where models run: hosted
   ✓ Installed: OpenClaw 2026.10.1
   → Agents: add a hosted agent
     Roles: add an agent first
     This repo: configure this project
     Check: verify the installation
   Run `nomarmy agents add` now? [Y/n]

Stop anytime; nomarmy setup picks up where you left off. Want every step spelled out? Example setup: Claude Code, Codex and an API key goes command by command.

1. Use it: restart Claude Code in the project and ask it to use nomArmy for one small bug that has a test. When that works, try /feature .

Prefer a plugin? After step 2, Claude Code users can run /plugin marketplace add rayson-tech/nomarmy and /plugin install nomarmy@nomarmy instead of using nomarmy connect; Codex works too (plugins).

Stuck? nomarmy doctor checks the machine and nomarmy health checks everything nomArmy runs on. Upgrading later? nomarmy update.

How every byte gets verified

Shortened. The full README is on GitHub.