ci-triage-mcp
Provides tools for triaging GitHub Actions CI failures, including fetching PR checks, failed jobs, and log analysis.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ci-triage-mcp summarize the failures in PR #42 in owner/repo"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
ci-triage-mcp
MCP server for GitHub Actions CI failure triage. Wraps the gh CLI to fetch PR checks, failed jobs, and tail/grep failed job logs — with ANSI/timestamp stripping and root-cause extraction. Zero runtime dependencies; stdio JSON-RPC.
Built to turn a 5–10 minute "open the run, find the failed job, scroll the raw log" ritual into a single tool call.
Tools
Tool | Input | Returns |
|
| Aggregated check rollup: failed / pending / success + merge state |
|
| Jobs with |
|
| Last N log lines, ANSI + timestamp prefixes stripped |
|
| Matching lines + 2 lines context. Use when failure is mid-log (E2E, build errors) |
|
| End-to-end: failed checks → failed jobs → log tail → extracted error lines + file:line |
All repo inputs validated as owner/repo (alphanumerics, ., -, _). lines capped at 500, maxMatches at 200.
Related MCP server: tai-mcp-github
Install
One-click install
Click a badge → opens the install page → click the button → your IDE prompts to install.
GitHub strips custom protocol schemes (
cursor://,vscode://) from markdown links for security, so the badges route through a hosted install page on GitHub Pages with real<a href>buttons. The page also covers Claude Code, Claude Desktop, Cline, Windsurf, Zed, and LM Studio.
The install page registers the server under the name ci-triage via npx -y github:aamar-shahzad/ci-triage-mcp (works now, no npm registry publish needed). After install, restart your IDE if the tools don't appear immediately.
Manual install — per client
The server config is the same everywhere; only the file location differs.
Cursor — ~/.cursor/mcp.json:
{
"mcpServers": {
"ci-triage": {
"command": "npx",
"args": ["-y", "github:aamar-shahzad/ci-triage-mcp"],
"env": {}
}
}
}VS Code / GitHub Copilot — ~/.vscode/mcp.json (or workspace .vscode/mcp.json):
{
"mcpServers": {
"ci-triage": {
"command": "npx",
"args": ["-y", "github:aamar-shahzad/ci-triage-mcp"],
"env": {}
}
}
}Claude Desktop — claude_desktop_config.json:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"ci-triage": {
"command": "npx",
"args": ["-y", "github:aamar-shahzad/ci-triage-mcp"],
"env": {}
}
}
}Claude Code (CLI):
claude mcp add ci-triage npx -- -y github:aamar-shahzad/ci-triage-mcpCline / Roo Code / Continue / Windsurf — same mcpServers shape as Cursor, in their respective MCP config files:
Cline:
~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json(macOS)Windsurf:
~/.codeium/windsurf/mcp_config.jsonContinue:
~/.continue/config.jsonunderexperimental.mcpServers
Zed — ~/.config/zed/settings.json:
{
"context_servers": {
"ci-triage": {
"command": "npx",
"args": ["-y", "github:aamar-shahzad/ci-triage-mcp"],
"env": {}
}
}
}LM Studio — deep link:
lmstudio://add_mcp?name=ci-triage&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsImdpdGh1YjphYW1hci1zaGFoemFkL2NpLXRyaWFnZS1tY3AiXSwiZW52Ijp7fX0=Option C — clone + run directly
For local development or to avoid npx cold-install delay:
git clone https://github.com/aamar-shahzad/ci-triage-mcp.git ~/src/ci-triage-mcpThen in your MCP config:
{
"mcpServers": {
"ci-triage": {
"command": "node",
"args": ["/Users/you/src/ci-triage-mcp/src/index.mjs"]
}
}
}Regenerate install links
node scripts/gen-install-links.mjs # prints markdown
node scripts/gen-install-links.mjs --json # prints raw links as JSONAuthentication
No token stored in MCP config. Uses your existing gh CLI authentication (keyring / config file from gh auth login). The server shells out to gh; nothing else.
Requirements:
ghCLI on PATH — install from https://cli.github.comAuthenticated:
gh auth login(scopes:repo,workflowfor CI logs)Node ≥ 20
On initialize, the server probes gh --version and emits a _warning in serverInfo if gh is missing.
Why
Generic GitHub MCPs return raw JSON and stop at the check rollup. This server is opinionated about the triage workflow:
Failed-check discovery —
get_pr_checksfilters toconclusion=FAILUREonly.Job drilldown —
get_failed_jobsmaps a run to its failed job IDs (the part you usually copy by hand).Clean logs —
get_job_logs_tailstrips ANSI escapes and the2026-07-09T20:34:56.5281699Ztimestamp prefix that buries the actual line.Mid-log grep —
grep_job_logsfinds errors anywhere in the log with context. E2E / build failures live mid-log, not at the tail. Tail-only tools miss them.Root-cause extraction —
summarize_pr_failurechains all of the above and extracts error lines +file:linein one call.
Example: a 725-line Cypress job log → grep_job_logs with pattern AssertionError|Timed out returns 1 match with 2 lines context, surfacing Expected to find element: [data-testid="inviteUserButton"], but never found it in one call.
Smoke test
node scripts/smoke.mjsRuns tools/list + a grep_job_logs call against a known public failed job. Requires gh auth.
Development
git clone https://github.com/aamar-shahzad/ci-triage-mcp.git
cd ci-triage-mcp
node src/index.mjs # starts stdio JSON-RPC serverNo build step. Pure ESM .mjs, no dependencies.
License
MIT
Available Tools
5 toolsget_failed_jobsA
List only failed jobs for a workflow run. Input: {repo: "owner/repo", runId: number}. Returns jobs with conclusion=failure: name, databaseId, url.
Inputs: repo (required), runId (required).
get_job_logs_tailA
Fetch tail of a failed job log. Input: {repo: "owner/repo", jobId: number, lines?: number=80}. Returns last N lines of the job log (cleaned of ANSI + timestamp prefixes).
Inputs: repo (required), jobId (required), lines.
get_pr_checksA
List all CI checks for a GitHub PR with conclusion + URL. Input: {repo: "owner/repo", prNumber: number}. Returns aggregated check rollup.
Inputs: repo (required), prNumber (required).
grep_job_logsA
Grep a job log for lines matching a regex (case-insensitive). Returns matching lines with 2 lines context before/after. Use when failure is mid-log (E2E tests, build errors) rather than at the tail. Input: {repo, jobId, pattern: string, maxMatches?: number=50}.
Inputs: repo (required), jobId (required), pattern (required), maxMatches.
summarize_pr_failureA
End-to-end triage: find failed checks on a PR, tail each failed job log, extract error/fail/first-failing-test lines. Input: {repo, prNumber}. Returns per-failed-job summary with likely root cause.
Inputs: repo (required), prNumber (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
Each tool has a distinct purpose: listing failed jobs, fetching log tails, listing all checks, searching logs, and summarizing failures. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., get_failed_jobs, grep_job_logs), making it predictable.
Five tools is appropriate for CI triage—covers listing, log access, searching, and summarization without being excessive or insufficient.
The tool set covers the full triage workflow: identify failures, retrieve logs, search logs, and generate summaries. No obvious gaps for the stated purpose.
Maintenance
Related MCP Connectors
A Model Context Protocol (MCP) application for automated GitHub PR analysis and issue management.…
Remote MCP server for supportsheep: run AI interviews and manage support content for your blog.
Remote MCP server for supportsheep: run AI interviews and manage support content for your blog.
MCP server for siGit (sigit.si): browse repos, search code, manage PRs/issues, web search.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceMCP server that pushes GitHub Actions CI/CD results and PR events into Claude Code sessions, enabling automatic investigation and remediation.42 npm1MIT
- FlicenseAqualityDmaintenanceA minimal MCP server that exposes a focused set of GitHub PR review tools to AI agents, enabling PR listing, detail retrieval, comment viewing, and thread management.5-
- FlicenseNot gradedqualityAmaintenanceA GitHub MCP server that wraps the gh CLI to expose GitHub operations like issues, pull requests, branches, labels, repositories, CI actions, and Projects V2 as tools for MCP clients.-
- FlicenseNot gradedqualityDmaintenanceMCP server for interacting with GitHub pull requests and issues via natural language. Provides tools to list PRs, inspect diffs, check CI status, and post review comments with write-safety guards.-