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
Agentloopkit
Overview
Description from the maker (original English)
Read-only MCP server for AgentLoopKit tasks, policies, reports, handoffs, and status.
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": {
"agentloopkit": {
"command": "npx",
"args": [
"-y",
"agentloopkit"
]
}
}
}Run this in your terminal
claude mcp add agentloopkit -- npx -y agentloopkitOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"agentloopkit": {
"command": "npx",
"args": [
"-y",
"agentloopkit"
]
}
}
}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": {
"agentloopkit": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"agentloopkit"
]
}
}
}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 abhiyoheswaran1, 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 32466 servers in this category
- Published to the registry more recently than 17% of the other 32466 servers in this category
- Basic checks equal to or better than 100% of the other 32466 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 Agentloopkit 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 (1.2.0) reached the registry 4 months ago.
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, HotCodePush
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
HotCodePush
by hotcodepush-team
Manage over-the-air (OTA) updates for React Native, Expo, Capacitor and Cordova apps.
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.
AgentLoopKit
A drop-in engineering loop for software agents.
An open-source Baseframe Labs developer tool.
Your software agent can produce a diff. AgentLoopKit helps you decide whether that work is reviewable, verifiable, and merge-ready.
It gives Codex, Claude Code, Cursor, OpenCode, Gemini CLI, GitHub Copilot CLI, and other engineering agents a local acceptance layer: task contracts, safety rules, verification evidence, review-readiness scores, PR descriptions, and reviewer handoffs.
Unstructured automation produces code. Agentic engineering produces auditable work.
ProjScan finds the risk. AgentLoopKit controls the work. AgentFlight proves the result.
The screenshots and terminal demos in this README are generated from committed sources in docs/assets/readme/ with Playwright and VHS. You can regenerate them locally.
What It Does
AgentLoopKit is a repo-level toolkit for developers using Codex, Claude Code, Cursor, OpenCode, Gemini CLI, GitHub Copilot CLI, and other engineering agents.
Keep your agent, IDE, and CLI. AgentLoopKit gives those tools a repeatable local workflow:
- Specify the task.
- Constrain the risk.
- Implement the smallest useful change.
- Verify with real commands.
- Review the diff.
- Hand off with evidence.
- Ship only when the work is reviewable.
Run init inside an existing repository and AgentLoopKit creates:
.agentloop/for tasks, reports, handoffs, gates, policies, templates, and agent instructionsAGENTS.mdfor agent-facing repo guidanceAGENTLOOP.mdfor the working loopagentloop.config.jsonfor local command and path settings
Generated AGENTS.md includes a specialist roster for product, CLI, template, verification, security, release, docs, compatibility, MCP, and repo-steward work. It helps future agent sessions split work without adding a background service.
The CLI demo shows the normal path: initialize a repo, create a task, run reviewed verification, score review readiness, draft PR copy, inspect review context, and trace why a file changed.
Install
Use it with npx from the repository you want to configure:
cd /path/to/your/reponpx agentloopkit init --dry-run npx agentloopkit init
init writes files into the current directory. --dry-run previews the same plan and writes nothing.
Commit the generated harness baseline before your first feature task when you want clean diff evidence. If the harness files are still uncommitted, explain-diff, Guard, and resume packs will include those generated files as local work, which is accurate but noisier than the steady-state loop.
After setup, non-init commands search upward for the nearest agentloop.config.json and use that folder as the AgentLoop root. You can run agentloop status, agentloop verify, agentloop ship, or agentloop prepare-pr from a nested source folder and still write tasks, reports, runs, and handoffs to the initialized repo root.
Do not run init from your home directory unless you intend to configure your home folder. AgentLoopKit refuses that by default; --force allows it and prints a home-directory target warning. If you want local agent guidance but do not want to commit the generated files, use local-only mode:
npx agentloopkit init --local-only--local-only writes the harness, asks Git for this clone's metadata directory, then adds a marked block to that clone's info/exclude for .agentloop/, AGENTS.md, AGENTLOOP.md, and agentloop.config.json. It does not edit .gitignore, global Git config, shell profiles, or other project files.
The examples below use agentloop after setup. If you are not installing the package locally or exposing its binary on PATH, keep using the one-off form, for example npx --yes agentloopkit@latest doctor --redact-paths.
Check the published package explicitly:
npx --yes agentloopkit@latest versionnpx --yes agentloopkit@latest init
For repeatable CI or team setup, replace @latest with a vetted version.
Before initialization, exploratory preflight can be advisory:
npx --yes agentloopkit@latest doctor --advisory --redact-pathsAdvisory mode keeps missing-setup diagnostics visible but exits 0 so first-run scripts can continue. Use plain doctor or doctor --strict for gates that should fail on setup errors.
Pinned team usage:
pnpm add -D agentloopkitpnpm agentloop init
Existing Repos
Repos that already use AgentLoopKit can update the CLI without rewriting local harness files:
cd /path/to/existing/reponpx --yes agentloopkit@latest version npx --yes agentloopkit@latest doctor --redact-paths npx --yes agentloopkit@latest upgrade-harness --details --redact-paths npx --yes agentloopkit@latest init --dry-run
These commands inspect the published package. This repository may document unreleased guidance before the next publish; check release status before expecting agentloopkit@latest to include new subcommands.
init skips existing generated files and appends to unmarked AGENTS.md files instead of overwriting maintainer edits. Use upgrade-harness to find older guidance that does not tell agents to run agentloop doctor and agentloop start before broad reads, list handles with agentloop context handles when available, or expand source truth with agentloop context show . Copy only the useful pieces into AGENTS.md, AGENTLOOP.md, or .agentloop/harness/*.
You can use the latest loop before refreshing old guidance:
npx --yes agentloopkit@latest create-task --type bugfix --title "Fix checkout bug"npx --yes agentloopkit@latest start --for generic --goal implement --redact-paths npx --yes agentloopkit@latest verify npx --yes agentloopkit@latest ship npx --yes agentloopkit@latest prepare-pr npx --yes agentloopkit@latest maintainer-check
Core Workflow
First useful loop after init:
agentloop doctoragentloop create-task --type bugfix --title "Fix checkout bug" --include-config-commands agentloop status --brief agentloop start --for codex --goal implement --redact-paths agentloop loop create --goal "Keep checkout work release-ready" --budget-tokens 50000 --max-iterations 5 agentloop loop tick agentloop loop scorecard agentloop ready agentloop verify --task-commands --progress agentloop ship agentloop prepare-pr agentloop task done
That sequence creates a task contract, checks the repo setup, gives the next software agent a compact start briefing, records a local loop contract with token receipts, scores whether another loop pass should continue, checks readiness gates, runs only reviewed verification commands, records review-readiness evidence, drafts PR copy, and closes the active task. It does not post to GitHub, publish packages, call an LLM, execute a coding agent, or run hidden commands.
Make Your Agent Start Here
Before a software agent broad-scans the repo, run:
agentloop doctor --redact-pathsagentloop start --for codex --goal implement --redact-paths agentloop context handles --redact-paths agentloop context show --redact-paths
doctor checks the Agent Readiness Matrix: Doctor-before-Start guidance, Start guidance, context-handle guidance, broad-read avoidance, MCP guidance, and installed agent instruction files. start gives the current task, proof, risk, context budget, and source handles. context handles lists which handles are available now. context show expands exact local source truth only when the agent needs detail.
npx agentloopkit initagentloop create-task --title "Fix login redirect bug" --type bugfix \ --acceptance "Password-reset login redirects to the requested page" \ --include-config-commands \ --verification "npm test -- auth"
Run Codex, Claude Code, Cursor, OpenCode, Gemini CLI, or another software agent.
agentloop verify --task-commands --only-task-commands --progress agentloop ship --github-comment agentloop prepare-pr
create-task sets the new contract as the active task. Use agentloop task set only when you need to switch to another contract. Add --include-config-commands when you want the task contract to copy non-empty test, lint, typecheck, and build commands from agentloop.config.json. Task creation records those commands; it does not run them. Use verify --task-commands --only-task-commands when the active contract already includes the full check list. Use verify --post-verification-gates only for reviewed task gates that need the verification report to exist first. After verification and ship, use agentloop prepare-pr for reviewer copy and agentloop task done to close the active task before starting unrelated work.
Use agentloop status or agentloop next when an agent needs the next local action without reading every file:
npx agentloopkit statusnpx agentloopkit status --brief npx agentloopkit next npx agentloopkit next --redact-paths
When status or next recommends create-task in a dirty repo, the reason calls out existing dirty non-evidence files so agents can confirm the next task scope before implementation. When create-task sees that same pre-existing dirty work, it also adds a bounded Risk Notes bullet to the generated task contract so later review evidence preserves the baseline count and examples.
Use agentloop start --for codex --goal implement --redact-paths when a software agent needs the repo truth before broad reads. Start is the preflight: current task when one exists, decisive state, next safe command, read-first handles, risk summary, verification freshness, context-budget impact, and source handles. Use agentloop context handles to list available handles and normal empty states, then agentloop context show to expand source truth only when needed. Use agentloop context pack --for codex --goal continue --redact-paths when you need the lower-level receipt and omission details directly. Use agentloop guard when you want a live local check for scope drift, stale verification, proof debt, and context-budget pressure before review. Use agentloop explain-diff when you need to understand whether the current changed files are covered by task scope, recent run evidence, fresh verification, and risk guidance. Use agentloop resume-pack --for codex, --for claude, --for cursor, --for generic, or --for human when you need the older compact continuation surface. These commands are read-only by default and use local evidence only.
agentloop start is the agent starting point. It keeps agents from guessing by turning task state, changed files, verification, risk, and context pressure into one compact preflight. The Context Contract sits underneath it: context pack explains why each item is present, names what was left out, and provides local handles for the source truth. A large changed-file list becomes a small briefing the agent can expand only when it needs detail.
agentloop loop adds a local loop contract on top of normal task contracts. agentloop loop create records the goal, budget, stop conditions, suggested commands, native task path, and a token receipt.
Only the beginning is shown; read the rest in the repo