A self-hosted service that answers "what happened in CI" — over MCP, REST and a CLI.
It reads GitHub Actions runs, jobs, steps and logs; it does not poll in the background, does not keep a central token pool, and never treats a cached run as the truth when GitHub can still answer.
| Ask once, in any protocol | ci_status, find_runs, get_run, get_job, get_job_log, search_job_log, wait_for_run, trigger_workflow — over MCP (Streamable HTTP), REST and a CLI. One flow, three shapes; a model or a script uses the same answers. |
| Three layers, one step each | get_run names the job that failed, get_job names the step, get_job_log returns its text. No call answers two layers, so no caller has to know which one it is looking at. |
| Step-level logs, kept | GitHub splits a run into per-step files for about an hour; after that the same endpoint returns one merged document. The service captures the split while it exists, stores it as ordinary rows, and reads it forever. Missed capture is reported honestly — never replaced by another step's text. |
| Windows that address, not interpret | tail, an explicit line range, or your own regex. No guessing at test summaries or teardown output, because a general CI tracker cannot know what any project prints. |
| Trigger and wait, without burning minutes | trigger_workflow dispatches on request; if_absent=true answers "this commit already ran" without starting a second run. wait_for_run is a bounded long poll whose timeout comes from the workflow's own history. |
| PostgreSQL, and it says so | Log tables are partitioned by month so old data is one DROP TABLE; the schema is the service's own renderer; the test suite runs against a real server. |
Three different things, and the third is the easiest to underestimate.
- Context: a 4,000-line job log becomes
grepand a few lines of context; a 12-job matrix becomes a 12-line roster. Some of that log does not fit in a context window at all, so the choice is not cheaper but possible. - Time:
wait_for_runis one bounded call instead of a polling loop;cancel_runandif_absent=truestop minutes you would otherwise spend, andtrigger_workflowreturns p50/p90 so you can decide what to wait for. - Wrong conclusions:
attempt/is_latestseparates a capacity blip from a broken backend;has_logplusreasonseparates "no output" from "nothing was captured";ci_status.health.alertsreports its own silent degradation as an executable list.
For the long version — including an operator's measured session and what we saw using the service on itself — see What it saves.
- Documentation (English) — deployment, the API, the CLI, development
- 文档（简体中文）