ci-watch-mcp

An MCP server with a single watch_ci tool — it waits for GitHub Actions CI to complete for a commit in a local git repository and, in one call, returns a summary along with the error log if something failed.

Why

Without it, checking whether CI passed after a push is done manually:
push one → sleep → gh run list → if the status is "in_progress", sleep again → gh run list again → if conclusion: failure, work through a separate gh run view <id> --log-failed call to see what broke. watch_ci does all this in a single call and immediately returns the failure log, without a manual wait loop.

Tool

watch_ci

Returns:

• { ok: true, conclusion: "success", url, sha, workflowName } — CI passed;

• { ok: false, conclusion: "failure", url, sha, workflowName, failedLogs } — CI failed; failedLogs contains the tail of gh run view --log-failed (truncated to 8000 chars, from the end — that is the most informative part);

• { ok: false, timedOut: true, status, url, message } — did not finish/start within the allotted time.

If ref does not resolve to an actual commit (i.e. a typo in the SHA), the tool immediately throws an error instead of silently disposing until the timeout.

Installation

cd ci-watch-mcp
npm install

Connect to Claude Code:

claude mcp add ci-watch -s user -- node /шлях/до/ci-watch-mcp/src/server.js

Requires an installed and authenticated gh CLI (gh auth status).

Tests

npm test

The tests run against already finished real runs in the secretscan repository (successful, failed, and a commit with none of the CI runs) — no need to wait for a live push.

License

MIT — Faneraiy14.