Skip to main content
Glama

Related Servers

Alternatives to triage-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Lets agents read a GitHub repository's live issues through read-only tools for listing, filtering, fetching details with comments and cross-references, searching, and exploring labels and milestones, with transparent pagination and provenance notes.
      5
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents to read GitHub repositories, files, commits, issues, pull requests, releases, Actions, and search results through 18 read-only MCP tools. It reuses existing credentials, routes around unreliable networks, and caches responses on disk to stay within rate limits.
      34
      274 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables local models to query GitHub read-only through nine compact tools that return small, capped results, such as repositories, issues, pull requests, commits, code search, and file contents.
      2
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to analyze public GitHub repositories directly through tools for repo health scoring, recent commit summaries, good first issue discovery, and semantic Q&A over docs and issues.
      4
      32 npm
      1
      MIT

    TDQS

    A3.6/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool targets a distinct step of issue triage: fetching an issue, searching issues, searching code, checking for existing fixes, and fetching contribution rules. Minor overlap exists between get_issue (returns assignees) and check_existing_fix (checks assignment status) and between the two search tools, but descriptions make the boundaries clear.

    Naming Consistency4/5

    Four of five names follow a verb_noun snake_case pattern (get_issue, find_related_code, check_existing_fix, search_issues). repo_contribution_rules breaks the pattern by dropping the verb, but it is still readable and unambiguous.

    Tool Count5/5

    Five tools is well-scoped for a narrow triage workflow, and each one maps to a distinct decision an agent needs to make before claiming an issue. Nothing appears redundant or padding the surface.

    Completeness4/5

    The read-only triage lifecycle is well covered: discover an issue, search related issues/code, verify no existing fix, and check contribution rules before acting. Gaps are minor (no full untruncated issue body, no direct PR inspection or comment listing beyond what get_issue returns), but an agent can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues