Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Rerun or fix? Classify a failed check from past-run evidence: infra flake, flaky, or real.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
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": {
"rerunplan": {
"command": "npx",
"args": [
"-y",
"@reneturcios/rerunplan",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add rerunplan -- npx -y @reneturcios/rerunplan mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"rerunplan": {
"command": "npx",
"args": [
"-y",
"@reneturcios/rerunplan",
"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.
Paste into .vscode/mcp.json in your project
{
"servers": {
"rerunplan": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@reneturcios/rerunplan",
"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.
Runs on your computer; the tool list appears in your AI app after you install it.
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
The registry name was verified with the GitHub account CloudCorpRecords, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
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.
The registry does not list a required key, though some servers ask you to sign in on first use.
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).
The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 4 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Docker on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Symantec Cloud DLP AIops
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
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Governed Symantec Cloud DLP — 14 MCP tools, read-only with audit.
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.
A check failed. Rerun it, or fix it? rerunplan classifies the failure from evidence — the failing check's name, its error signature, and past runs of the same check — and answers with a classification, a recommendation, and the evidence lines that drove the call:
infra_flake → rerun — the error signature matches a known infrastructure pattern (timeout, connection reset, DNS, rate limit, runner loss, gateway errors) and the check is not failing that way every timeflaky → rerun — the check has passed before *and* has failed before with this same error signature; the failure comes and goesreal_failure → fix — the check fails in every usable past run (with the current signature, when one is given); an infra-looking signature that fails *every* time is still a real failureinsufficient_evidence → investigate — no usable history, or a mixed history no rule claimsRules fire in a fixed order and each appends its evidence. Statuses are normalised (success/pass/passed, failure/fail/failed/error); runs for other checks are ignored. Pure local computation: no network, no configuration.
npx @reneturcios/rerunplan plan --check unit-tests --signature "Error: boom" --past past-runs.json
npx @reneturcios/rerunplan --version
past-runs.json is a JSON array of {"check": "unit-tests", "status": "failure", "error_signature": "Error: boom"} objects (check and error_signature optional per run).
Exit codes: 0 on success, 1 on a runtime error (including an unreadable or invalid past-runs file), 2 on a usage error.
npx -y @reneturcios/rerunplan mcp
MCP client config:
{
"mcpServers": { "rerunplan": { "command": "npx", "args": ["-y", "@reneturcios/rerunplan", "mcp"] } } }
plan_rerun — Classify a failed check from its past-run history and recommend rerun, fix, or investigate.check (string, required) — the failed check's nameerror_signature (string, optional) — the current failure's error signaturepast_runs (array, required) — past runs as {check?, status, error_signature?} objectsdocker run -i ghcr.io/cloudcorprecords/rerunplan
docker run --rm -v "$PWD:/w" ghcr.io/cloudcorprecords/rerunplan plan --check unit-tests --past /w/past-runs.json
npm install
npm run build # tsc -> dist/ npm test # tsx --test test/*.test.ts (pure local, no network) npm run dev # run the CLI from source
MIT — Copyright (c) 2026 Rene Turcios