Skip to main content
Glama

Related Servers

Alternatives to github-triage-agent

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to search and retrieve GitHub issues and labels, validate duplicate references, and optionally add labels or post comments with writes disabled, dry-run, or live.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants and MCP hosts to inspect GitHub repositories, pull requests, issues, and activity, and to create issues through schema-validated tools, resources, and prompts, with write actions gated by host or CLI confirmation.
      5
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables any MCP client to read GitHub repositories, branches, tags, pull requests, files and Actions workflow runs, and optionally create branches and pull requests, comment, assign, approve, trigger workflows, merge and delete. Read-only by default, with separate opt-in switches for write and destructive operations, working against github.com or GitHub Enterprise Server.
      11
      MIT

    TDQS

    A3.7/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: issue retrieval, PR retrieval, repo context, recent activity, search, labeling, commenting, assigning, closing, and reopening. The retrieval tools have clearly different scopes (specific issue, search results, recent updates), so agents can select correctly without ambiguity.

    Naming Consistency5/5

    All tool names use consistent snake_case and follow a predictable verb_noun pattern. Retrieval tools use get_ or search_, while mutation tools use clear action verbs like add_, post_, assign_, close_, and reopen_.

    Tool Count5/5

    Ten tools is well-scoped for a GitHub triage agent. Each tool covers a focused triage operation, and there is no obvious bloat or redundancy in the set.

    Completeness4/5

    The surface covers the core triage lifecycle: reading issues/PRs, searching, labeling, commenting, assigning, closing, reopening, and fetching repository context. Minor gaps remain, such as removing labels, unassigning users, or editing issue/comment content, but agents can work around these for most triage workflows.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues