A
licenseA
qualityB
maintenanceEnables autonomous triage of GitHub issues and pull requests through MCP, with classification, deduplication, prioritization, and safe human-in-the-loop actions.
10
MIT
github-triage-agent
by Hemamannam
Related Servers
Alternatives to github-triage-agent
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceAn MCP server that provides operational tooling over the GitHub API — issue triage, PR review monitoring, repo health audits, and team access reviews.111MIT
- FlicenseNot gradedqualityCmaintenanceEnables users to read and manage GitHub repositories through MCP, with destructive operations gated behind explicit confirmation and dry-run previews.1-
- AlicenseNot gradedqualityCmaintenanceEnables AI clients such as Cursor to interact with GitHub repositories and perform issue listing, triage, health checks, prioritization, commenting, weekly digests, and release-note generation through purpose-built MCP tools.3 npmMIT
- FlicenseNot gradedqualityCmaintenanceMCP server for interacting with GitHub pull requests and issues via natural language. Provides tools to list PRs, inspect diffs, check CI status, and post review comments with write-safety guards.-
- AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible AI clients to manage GitHub repositories and issues and trigger repository dispatch events via tools and a REST API.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
ActivityMaintained
ResponsivenessNo issues