Skip to main content
Glama

Related Servers

Alternatives to gh-triage-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      Not graded
      maintenance
      A context-efficient GitHub MCP server designed for AI agents to manage repositories, issues, pull requests, and actions directly via cloud workflows. It focuses on a compact tool surface to minimize context waste while providing comprehensive read and write coverage without requiring a local Git CLI.
      -
    • F
      license
      A
      quality
      D
      maintenance
      MCP server exposing GitHub tools for issues, pull requests, and code browsing via the GitHub REST API. Designed for local LLM clients with flat arguments and streamable HTTP support.
      15
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      A production-ready server featuring over 28 tools for comprehensive GitHub analysis, including repository metadata, issue tracking, and workflow monitoring. It enables users to search repositories, analyze contributor activity, and inspect codebase health through natural language.
      1
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      Connects an LLM to a GitHub repository's issues, allowing it to list, fetch, and search issues freely while gating new issues, comments, and closures behind a two-step, single-use confirmation token that cannot be bypassed. It provides least-privilege, token-authenticated access to the GitHub REST API through a small typed tool surface.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol server that exposes read-only GitHub tools to LLM clients, enabling browsing of open issues, pull requests, issue details, and recent repository activity via natural language.
      MIT

    TDQS

    A4.3/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: search_issues finds issues, summarize_issue loads details and comments, and draft_comment creates a proposed response. There is no meaningful overlap or ambiguous boundary between them.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case: search_issues, summarize_issue, draft_comment. The naming style is uniform and predictable across the entire server.

    Tool Count5/5

    Three tools form a tight, well-scoped set for an issue triage workflow: find, understand, and draft a response. The count is neither too sparse nor excessive for the stated purpose.

    Completeness5/5

    The server covers the full triage lifecycle: discovering relevant issues, reading issue context with comments, and drafting a comment with optional posting. There are no obvious dead ends for the intended use case.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues