rerunplan
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
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
npx @reneturcios/rerunplan plan --check unit-tests --signature "Error: boom" --past past-runs.json
npx @reneturcios/rerunplan --versionpast-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.
Related MCP server: CI Investigator MCP
MCP server
npx -y @reneturcios/rerunplan mcpMCP client config:
{
"mcpServers": {
"rerunplan": {
"command": "npx",
"args": ["-y", "@reneturcios/rerunplan", "mcp"]
}
}
}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
docker run -i ghcr.io/cloudcorprecords/rerunplan
docker run --rm -v "$PWD:/w" ghcr.io/cloudcorprecords/rerunplan plan --check unit-tests --past /w/past-runs.jsonDevelopment
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 sourceLicense
MIT — Copyright (c) 2026 Rene Turcios
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Triage failing GitHub Actions jobs and see what self-heal repaired, in natural language.
Flaky test detection, root cause analysis, and fix suggestions for development teams.
Finds the GitHub Actions workflow eating your CI bill and suggests fix diffs, verified against runs.
Change-aware CI validation and affected-test guidance for coding agents.
Related MCP Servers
- FlicenseNot gradedqualityNot gradedmaintenanceA utility that helps diagnose and fix GitHub Actions workflow failures by analyzing run logs, identifying common failure patterns, and suggesting specific fixes through a structured decision tree.1-
- AlicenseAqualityCmaintenanceProvides tools to analyze and debug GitHub Actions CI failures, including summarizing failures, detecting flaky tests, and suggesting fixes.108 npm1ISC
- FlicenseAqualityBmaintenanceEnables CI/CD failure triage for GitHub Actions by inspecting failed runs, classifying root causes with LLM assistance, retrieving relevant runbook guidance, estimating flakiness, and either preparing dry-run fix PRs or publishing structured diagnoses to Discord for human review.2-
- AlicenseNot gradedqualityCmaintenanceEnables AI-driven triage of Allure test results by clustering failures into stable signatures and generating root-cause explanations, so you can turn large failing CI runs into a few actionable categories.MIT