github-triage-mcp
Related Servers
Alternatives to github-triage-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceRanks 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.665 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables 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.0MIT
- AlicenseAqualityCmaintenanceEnables triage of GitHub issues by fetching and filtering issues, checking claim status, and listing new open issues across a watch-list.4MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents and human managers to orchestrate GitHub-based project work by self-assigning tasks, coordinating swarms, tracking token budgets, generating PRDs, planning sprints, triaging issues, and materializing tasks as GitHub issues, milestones, and project views.35 npmMIT
- AlicenseAqualityCmaintenanceGenerates engineering intelligence reports (standups, weekly summaries, sprint retrospectives) from GitHub and Jira data, accessible via MCP clients or CLI.105 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to self-assign and coordinate tasks, track progress and token budgets, and automate GitHub project workflows such as PRD-to-issues pipelines, sprint planning, triage, reviews, and releases.35 npmMIT
TDQS
Scored across 4 tools
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.
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.
Four tools is exactly right for a focused triage server. Each tool covers a necessary step in the triage workflow without redundancy or bloat.
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.