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-
- AlicenseAqualityCmaintenanceProvides tools to analyze and debug GitHub Actions CI failures, including summarizing failures, detecting flaky tests, and suggesting fixes.103 npm1ISC
- AlicenseNot gradedqualityAmaintenanceEnables 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.MIT
- FlicenseNot gradedqualityDmaintenanceExposes GitHub engineering-analytics tools to LLM clients, enabling queries about code review bottlenecks, stale PRs, and commit hygiene.-
- AlicenseAqualityBmaintenanceStreamlines GitHub PR workflows, monitors CI/CD, and sends Slack notifications. Provides tools for PR analysis, CI monitoring, and follow-up tasks.7ISC
- AlicenseNot gradedqualityCmaintenanceEnables read-only integration with GitHub, Jenkins, and Artifactory for DevOps monitoring, analysis, and troubleshooting. Provides repository inspection, build log retrieval, and artifact management through natural language.MIT
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.