GitHub Triage Agent MCP Server
Related Servers
Alternatives to GitHub Triage Agent MCP Server
No user-submitted related servers found.
Related Servers
- 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.1 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants to interact with GitHub issues, pull requests, and Actions workflows through MCP tools.-
- AlicenseAqualityAmaintenanceMCP 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.1429 npm3Apache 2.0
- FlicenseNot gradedqualityCmaintenanceMCP server that triages GitHub issues by classifying, ranking priority, and assigning an engineer using a local LLM (Ollama) with full traceability.-
- FlicenseNot gradedqualityCmaintenanceEnables automated GitHub pull request review through a multi-agent system using LangGraph and MCP tools, analyzing PR metadata, files, patches, comments, and policies with RAG, guardrails, HITL approval, and Langfuse observability.-
- FlicenseNot gradedqualityBmaintenanceEnables headless Claude to review pull requests and triage CI failures on a real GitHub repository, routing all GitHub write actions through the MCP server.-
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.