mcp-ci-triage
Related Servers
Alternatives to mcp-ci-triage
No user-submitted related servers found.
Related Servers
- AlicenseAqualityNot gradedmaintenanceConnects AI assistants to GitHub Actions workflows to monitor CI/CD pipelines, view run logs, diagnose failures, and optionally trigger or manage workflows with granular permission controls.101-
- AlicenseBqualityBmaintenanceEnables AI coding assistants to inspect GitHub Actions CI runs, diagnose failures with failed-step summaries and filtered job logs, read per-job coverage, and view pull request checks through read-only, allowlisted access.6MIT

StackVitalsofficial
AlicenseNot gradedqualityAmaintenanceGives AI agents one MCP interface to inspect CI health and flaky tests, pull request flow, delivery/DORA metrics, dependency risks, community health, insights, and org portal data across GitHub repositories. It exposes 11 core tools by default and all 35 with --tools all.Apache 2.0- AlicenseAqualityCmaintenanceProvides tools to analyze and debug GitHub Actions CI failures, including summarizing failures, detecting flaky tests, and suggesting fixes.108 npm1ISC
- AlicenseNot gradedqualityBmaintenanceEnables comparing a pull request's head and base commit check runs and commit statuses to classify every failing CI check as introduced, pre-existing, external, fixed, indeterminate, or pending. Exposes this as the diff_pr_ci and diff_ci_runs tools so agents can gate CI or triage failing PRs without clicking through checks twice.66 npmMIT
- FlicenseNot gradedqualityDmaintenanceExposes GitHub engineering-analytics tools to LLM clients, enabling queries about code review bottlenecks, stale PRs, and commit hygiene.-
TDQS
Scored across 4 tools
Each tool targets a distinct aspect of CI triage: listing recent runs, showing failing jobs, retrieving a log tail, and detecting mixed outcomes. Their purposes do not overlap, and they form a natural progression from discovery to diagnosis.
All tool names use snake_case noun phrases that clearly describe the returned data or signal. There is no mixing of verb styles, casing, or structural patterns.
Four tools is well-scoped for a focused triage server, covering the essential read operations without unnecessary bloat or missing critical steps.
The set covers the core triage workflow: discover recent runs, identify failures, inspect logs, and detect flaky patterns. Minor gaps exist, such as no direct tool for a single run's full details or complete logs, but the bounded tail is sufficient for most triage needs.