Skip to main content
Glama
github-triage-mcp

github-triage-mcp

by yangchoi

Related Servers

Alternatives to github-triage-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Ranks your open pull requests by urgency with human-readable reasons, surfacing changes requested, unresolved review threads, real failing checks, merge conflicts, and reviewer silence. Exposes tools for an attention report, a simple list of open PRs, and a per-PR deep dive covering reviews, checks, and threads.
      87 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents and developers to check, before they comment or write code, which issue claims have gone stale and which finished fork branches never became a pull request. It ranks abandoned claims oldest-first, flags parked branches with compare data, and reports every claimant and linked PR for a single issue.
      94 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables an AI agent to retrieve assigned tickets and their context, assign and mark tickets in progress, create pull requests that close tickets, and move tickets through review and done states while leaving Git actions to the agent and merges to humans.
      5
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Generates engineering intelligence reports (standups, weekly summaries, sprint retrospectives) from GitHub and Jira data, accessible via MCP clients or CLI.
      10
      MIT

    TDQS

    A3.9/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool serves a distinct purpose: triage provides an overview, get_issue retrieves full thread content, search_issues queries by syntax, and linked_issues discovers cross-references. There is no overlap or ambiguity between them.

    Naming Consistency3/5

    get_issue and search_issues follow a clear verb_noun pattern, but triage is a bare imperative and linked_issues is a descriptive noun phrase rather than an action. The mixed conventions are still readable, but not fully consistent.

    Tool Count5/5

    Four tools is exactly right for a focused triage server. Each tool covers a necessary step in the triage workflow without redundancy or bloat.

    Completeness5/5

    The tool surface covers the complete read-only triage workflow: get an overview, drill into full details, search, and trace relationships between issues and PRs. No obvious gaps exist for the stated purpose.

    Maintenance

    ActivityStale
    ResponsivenessNo recent community issues