Skip to main content
Glama
umeshmynampati3-cmd

GitHub Triage Agent MCP Server

Related Servers

Alternatives to GitHub Triage Agent MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Exposes GitHub issue and pull-request triage capabilities to any MCP client: fetching repository context, classifying and prioritizing requests, finding duplicates, and applying labels, comments, assignments, closures, or reopenings. All writes are policy-gated, dry-run by default, and destructive actions require explicit two-step human confirmation.
      10
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      MCP server for auditable repository self-maintenance, turning GitHub issues and failed CI into independently verified pull requests with full audit trails, human approvals, and runbook archival.
      14
      95 npm
      3
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents and teams to turn GitHub Projects v2 into an autonomous task substrate for registering, claiming, tracking, reviewing, and completing work, while also supporting AI-powered PRD generation, sprint planning, issue triage, roadmap creation, GitHub Actions/releases/branches, and MCP resources/prompts.
      35 npm
      MIT

    TDQS

    A3.7/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool maps to a distinct resource-action pair: fetching issues vs PRs, searching, labeling, commenting, assigning, closing, reopening, and retrieving repo context or recent activity. No two tools appear to overlap in purpose, and descriptions clarify the boundaries.

    Naming Consistency5/5

    All tools follow a consistent verb_noun snake_case pattern (get_issue, search_issues, add_labels, close_issue, etc.). The naming style is uniform and predictable across the entire set.

    Tool Count5/5

    10 tools is well-scoped for a GitHub triage agent: it covers fetching, searching, acting on issues/PRs, and gathering repository context without unnecessary redundancy or bloat.

    Completeness4/5

    The surface covers the core triage workflow: discover, inspect, label, comment, assign, close, and reopen. Minor gaps exist such as no explicit remove_labels, unassign, or edit_issue, but agents can work around these without major dead ends.

    Maintenance

    ActivityStale
    ResponsivenessNo issues