
Rerunplan
io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 3, 2026
Rerun or fix? Classify a failed check from past-run evidence: infra flake, flaky, or real.
Overview
Rerunplan's local MCP server; no sign-in required; STDIO.
No AI overview yet: these facts come from the registry entry and the server itself.
Installation
In SourceWeft
- Open Rerunplan in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
rerunplan
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 claims
Rules 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.
CLI
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.
MCP server
MCP client config:
Tools
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?}objects
Docker
Development
License
MIT — Copyright (c) 2026 Rene Turcios
Source: README.md at commit c90106a
Tools
0Version history
1- v0.1.0LatestNov 3, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts