Skip to main content
Glama
Sign In
gha-doctor

gha-doctor

by linnea-bakshi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

Related Servers

Alternatives to gha-doctor

No user-submitted related servers found.

    Related Servers

    • TaskBounty Check

      eliottreich
      A
      license
      A
      quality
      C
      maintenance
      Local-only GitHub Actions and CI maintenance scanner for AI-built apps. Exposes scan, explanation, and fix-planning tools to MCP clients; modifies nothing and makes no outbound requests by default.
      3
      56 npm
      2
      MIT

    • gha-intel-mcp

      barissozudogru
      A
      license
      A
      quality
      B
      maintenance
      MCP server that analyzes GitHub Actions workflow performance, audits configuration for optimization, and provides billing and cache usage insights.
      3
      40 npm
      2
      MIT
    • StackVitals

      StackVitalsofficial

      stackvitals
      A
      license
      Not graded
      quality
      A
      maintenance
      Gives 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

    • cicd-aiops

      AIops-tools
      A
      license
      A
      quality
      B
      maintenance
      Governed CI/CD operations for self-hosted GitLab and Gitea — pipeline-failure, runner, artifact-bloat, and stale-branch RCA, with unbypassable audit logging (MCP + CLI), budget/runaway guards, dry-run, and undo/rollback.
      28
      MIT
    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

    A4.3/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct scope: run_deep_dive for a single run, pr_deep_dive for a PR's CI, analyze_repo for whole-repo health, lint_repo for static linting, explain_rule for rule docs, org_overview for fleet triage, and preview_fixes for diffs. Though pr_deep_dive includes a deep-dive component, its PR-level purpose is clearly separated, and all descriptions are explicit about boundaries.

    Naming Consistency4/5

    Names are consistently snake_case and mostly follow a verb_noun pattern (analyze_repo, explain_rule, lint_repo, preview_fixes). The exception is the two 'deep_dive' suffixes in run_deep_dive and pr_deep_dive, plus org_overview being noun_noun, but these are minor deviations within an otherwise readable and predictable naming scheme.

    Tool Count5/5

    7 tools is well-scoped for a CI analysis server. Each tool covers a meaningful slice of the domain (org, repo, PR, run, lint, rule, fix), and none feel redundant or unnecessary.

    Completeness5/5

    The tool surface covers the full analysis lifecycle: org-level triage, repo health, PR diagnosis, single-run deep dives, static linting, rule explanation, and previewing fixes. There are no obvious dead ends, and the described workflows (e.g., 'why is my PR slow/failing' → pr_deep_dive) are fully supported.

    Maintenance

    ActivitySlowing
    ResponsivenessSyncing

    Resources