ci-triage-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_pr_checksA | List all CI checks for a GitHub PR with conclusion + URL. Input: {repo: "owner/repo", prNumber: number}. Returns aggregated check rollup. |
| get_failed_jobsA | List only failed jobs for a workflow run. Input: {repo: "owner/repo", runId: number}. Returns jobs with conclusion=failure: name, databaseId, url. |
| 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). |
| 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}. |
| 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.