Skip to main content
Glama
codeBKashif

CI Investigator MCP

by codeBKashif
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to CI Investigator MCP

No user-submitted related servers found.

    Related Servers

    • pipeline_watch

      j-rdel
      F
      license
      A
      quality
      B
      maintenance
      Enables CI/CD failure triage for GitHub Actions by inspecting failed runs, classifying root causes with LLM assistance, retrieving relevant runbook guidance, estimating flakiness, and either preparing dry-run fix PRs or publishing structured diagnoses to Discord for human review.
      2
      -

    • github-actions-mcp

      lailo
      A
      license
      Not graded
      quality
      D
      maintenance
      Analyzes GitHub Actions workflows and performance, helping identify bottlenecks, failures, and optimization opportunities in CI/CD pipelines.
      18 npm
      MIT

    • Woodpecker CI Pipeline

      aman-11
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables automated analysis of Woodpecker CI pipeline failures with intelligent error detection and fix suggestions. Supports both direct pipeline analysis and IDE-integrated git-context analysis using repository names, PR numbers, or branch information.
      6 npm
      3
      ISC
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose, covering different aspects of CI failure analysis without overlap. For example, ci_health_score computes a health metric, while detect_flaky_tests analyzes flakiness, and explain_failure_root_cause classifies root causes.

    Naming Consistency4/5

    Tool names follow a consistent snake_case pattern and mostly use verb_noun or verb_phrase structure (e.g., detect_flaky_tests, list_failure_trends). One minor deviation is ci_health_score, which is a noun phrase, but it still fits the pattern.

    Tool Count5/5

    With 10 tools, the server is well-scoped for its purpose of CI failure investigation. This count allows comprehensive coverage without being overwhelming.

    Completeness5/5

    The tool set covers the full lifecycle of CI failure analysis: identification (get_failed_runs), summarization (summarize_failure), root cause analysis (explain_failure_root_cause, find_regression_pr_or_commit), trend detection (list_failure_trends, detect_flaky_tests), and remediation (suggest_fix_for_failure, ci_health_score). No obvious gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources