Spec Driven Development
by formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Runs on your computer★ 440MITUpdated 14 months ago
Install
nomArmy
Overview
Description from the maker (original English)
Sandboxed coding workers, verified: tests rerun fresh and must fail with the change reverted.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Other
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- The registry lists no key to fill in.
You need
- npmNode.js installed (for the npx command)
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"nomarmy": {
"command": "npx",
"args": [
"-y",
"nomarmy",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add nomarmy -- npx -y nomarmy mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"nomarmy": {
"command": "npx",
"args": [
"-y",
"nomarmy",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"nomarmy": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"nomarmy",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account rayson-tech, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Otheri
- More stars than 0% of the other 32435 servers in this category
- Published to the registry more recently than 98% of the other 32435 servers in this category
- Basic checks equal to or better than 100% of the other 32435 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is nomArmy safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.1.0-beta.18) reached the registry yesterday.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, Apify MCP Server
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Remote Desktop Commander
by desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Runs in the cloud★ 211Updated yesterday
Install
Apify MCP Server
by apify
Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡
Runs in the cloudUpdated today
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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
- 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. Windows is supported with the engine in WSL2. Follow the Windows setup. - Install and set up:
npm install -g nomarmycd 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.3 → 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](https://github.com/rayson-tech/nomarmy/blob/main/docs/setup/example.md) goes command by command.- 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
- Your coding assistant, the General, briefs a job: a task, acceptance criteria, and the tests that prove it.
- nomArmy creates a git worktree from your branch and runs the nom in a Podman sandbox with no network and no host credentials. (One exception, the Claude subscription: see Security posture.)
- The nom edits, runs tests, and ends with a four-line report:
STATUS,TESTS,NOT_DONE,NOTE. - nomArmy treats that report as a claim and checks the evidence itself:
- reads the real diff from git, not the nom's description of it
- runs your verification profile in a fresh sandbox
- reverts the production change and reruns the tests: a test that still passes proves nothing, so the job goes to review instead of being committed
- blocks on secrets, and flags tests made to pass (new skips, stubbed imports) and code nothing calls
- Only then does it commit, on the nom's own branch. It never merges into yours: reviewing and integrating stay with the General, and with you.
Failing verification stays failed, unconditionally. A malformed report isn't automatically a failure: if the repository changed, nomArmy verifies independently and may recover the work. And the checks aren't the General's to waive: a repo's .nomarmy.yml policy (on by default for new repos) makes verification and the revert check mandatory for every job.
Showing what was checked. When a /feature run finishes, the General gets a "Verified by nomArmy" block for the pull request: how many "done, tests pass" claims held up, how many nomArmy caught and why, and the new tests shown to fail without their change. nomarmy stats --share prints the same for any period, and nomarmy stats --badge writes a README badge like nomArmy | 78 claims checked · 11 caught. Every number comes from the verified records.
Checking without building costs nothing: mode: verify runs a verification profile against any branch, with no worker and no model tokens.
Want deeper checks? Three optional validators go further, each only adding review flags: mutation testing (do the tests pin down the changed lines?), Jev (do a scout's citations support its findings, does a report match its diff?, on TypeSafe or a compatible server on your own machine) and a model judge (acceptance criteria, weakened tests).
Where the work runs
- Agents say where a job can run: an API key, your own Claude, ChatGPT, Muse Code or Grok subscription (or another OpenClaw provider), or a local model on llama.cpp.
- The army says which role runs on which agent: Sr and Jr devs build, a security analyst and a data architect review, a PM checks the plan, a PO accepts.
- `/feature` runs a whole feature end to end, from plan through build, review and acceptance, and hands you a branch to merge.
- Harnesses give each repo the right sandbox: Go, Rust, Python and Node (mixed repos too), Playwright browser tests, and fake services like a mock login server, all offline. Adding one never touches core code.
What you get is work you don't have to take on faith, not cheaper work. Delegating costs the General tokens too, for briefing and review: on small, already-diagnosed tickets we measured 4 to 8 times more of the General's tokens than fixing the bug directly, with break-even around 150 lines of context a fix needs to read (the measurements). It pays off on bigger tickets, parallel work, and anywhere you'd otherwise trust an agent's say-so.
Have a GPU or a Mac with plenty of memory? Choose "a local model" in nomarmy setup: no per-token bill and your code stays home, but you pay in hardware, power and speed. nomarmy sizing tells you what fits. A shared model server works too.
Developed and maintained by Rayson Technologies. This is a beta (0.1.0-beta): settings carry across upgrades (see config compatibility).
Docs
| Install | Every setup: hosted (API keys and subscriptions), a local model on macOS, Linux, Windows with the engine in WSL2 or DGX Spark, a shared model server, Bedrock |
| Example setup | Claude Code, Codex and an API key, command by command |
| Agents and the army | Where a job can run, who does what, usage limits, picking an agent |
/feature runs | A feature end to end, and watching what nomArmy is doing |
| Your repository | .nomarmy.yml, verification, dependencies, private registries, what nomArmy checks |
| Validators | Optional deeper checks: mutation testing, Jev, a model judge |
| Harnesses | Ecosystem registry, detection, network levels, and requirements |
| Configuration | Settings, swapping the local model, sizing, admission |
| Reference | Every CLI command and MCP tool |
| Security posture | What the sandbox holds back, and the one exception |
| FAQ | Which model for which role, switching models, usage limits |
| Troubleshooting | Symptoms and fixes |
Security
A nom gets a writable git worktree inside a Podman sandbox and nothing else: no network, no host credentials, no Podman socket. Every model call is made by OpenClaw on your machine, never from inside the sandbox. Verification can climb a network ladder one rung at a time (fake services on a private network, then an allowlist you approve for a test tenant), but noms never leave network none. The exception is a Claude subscription, whose tools run on your machine, so nomArmy refuses build jobs on it unless you allow it. Never hand a nom production credentials, deployment access or SSH keys. Details: Security posture; to report a vulnerability, SECURITY.md.
Status
| Capability | Status |
|---|---|
| Verification core: worktrees, nomArmy-owned git, independent verification, the revert check, kept failed worktrees | Working, end-to-end tested |
mode: verify, secret scanning (secretlint, hard block), test-workaround and unwired-code checks | Unit and live tested; the heuristics are review flags |
Scout and decompose modes, auto_union | Unit and live tested |
| Agents: API keys | Live-verified with xAI; other providers built to OpenClaw's documented interface |
| Agents: subscriptions | ChatGPT (Codex) sandboxed and live-verified; Claude and Muse Code live-verified, but their tools run on the host (scout and review by default) |
| Local (llama.cpp) and Bedrock profiles | Working |
The army and /feature | Used daily on nomArmy itself and our own products: 783 jobs from September 18 to October 10, 2026 (measured results) |
| Harnesses: Go, Rust, Python, Node and mixed repos; Playwright; fake services | Live-verified offline |
| Private registries and a verification-only network allowlist | Live-verified; each passed an independent security review |
| Validators: mutation testing, Jev, a model judge | Unit and live tested; Jev and the judge evaluated on real job records |
nomarmy stats | Checked against a hand-built report on real job records |
What we've learned from real runs, including where delegating pays and where it doesn't, is in [docs/f
Only the beginning is shown; read the rest in the repo