GitHub Triage Agent MCP Server
Related Servers
Alternatives to GitHub Triage Agent MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceExposes GitHub issue and pull-request triage capabilities to any MCP client: fetching repository context, classifying and prioritizing requests, finding duplicates, and applying labels, comments, assignments, closures, or reopenings. All writes are policy-gated, dry-run by default, and destructive actions require explicit two-step human confirmation.10MIT
- FlicenseNot 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.-
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with GitHub issues, pull requests, and Actions workflows through MCP tools.-
- AlicenseNot gradedqualityCmaintenanceEnables an autonomous coding agent to fetch GitHub issues, safely inspect and patch code in isolated Docker sandboxes through standardized MCP tools, self-heal via iterative unit-test feedback, and open pull requests.-
- AlicenseAqualityCmaintenanceMCP server for auditable repository self-maintenance, turning GitHub issues and failed CI into independently verified pull requests with full audit trails, human approvals, and runbook archival.143Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents and teams to turn GitHub Projects v2 into an autonomous task substrate for registering, claiming, tracking, reviewing, and completing work, while also supporting AI-powered PRD generation, sprint planning, issue triage, roadmap creation, GitHub Actions/releases/branches, and MCP resources/prompts.272 npmMIT
TDQS
Scored across 10 tools
Each tool maps to a distinct resource-action pair: fetching issues vs PRs, searching, labeling, commenting, assigning, closing, reopening, and retrieving repo context or recent activity. No two tools appear to overlap in purpose, and descriptions clarify the boundaries.
All tools follow a consistent verb_noun snake_case pattern (get_issue, search_issues, add_labels, close_issue, etc.). The naming style is uniform and predictable across the entire set.
10 tools is well-scoped for a GitHub triage agent: it covers fetching, searching, acting on issues/PRs, and gathering repository context without unnecessary redundancy or bloat.
The surface covers the core triage workflow: discover, inspect, label, comment, assign, close, and reopen. Minor gaps exist such as no explicit remove_labels, unassign, or edit_issue, but agents can work around these without major dead ends.