triage-mcp
Related Servers
Alternatives to triage-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceLets agents read a GitHub repository's live issues through read-only tools for listing, filtering, fetching details with comments and cross-references, searching, and exploring labels and milestones, with transparent pagination and provenance notes.5MIT
- AlicenseAqualityBmaintenanceEnables AI coding agents to read GitHub repositories, files, commits, issues, pull requests, releases, Actions, and search results through 18 read-only MCP tools. It reuses existing credentials, routes around unreliable networks, and caches responses on disk to stay within rate limits.34274 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables local models to query GitHub read-only through nine compact tools that return small, capped results, such as repositories, issues, pull requests, commits, code search, and file contents.2MIT
- AlicenseAqualityCmaintenanceEnables AI agents to analyze public GitHub repositories directly through tools for repo health scoring, recent commit summaries, good first issue discovery, and semantic Q&A over docs and issues.432 npm1MIT
- FlicenseAqualityBmaintenanceEnables coding agents to read and modify GitHub issues, project boards, pull requests, repositories, releases, and Actions through configurable toolsets, with read-only and write-confirmation controls.322,864 npm-
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with GitHub repositories, issues, pull requests, code, and more through a comprehensive set of tools.-
TDQS
Scored across 5 tools
Each tool targets a distinct step of issue triage: fetching an issue, searching issues, searching code, checking for existing fixes, and fetching contribution rules. Minor overlap exists between get_issue (returns assignees) and check_existing_fix (checks assignment status) and between the two search tools, but descriptions make the boundaries clear.
Four of five names follow a verb_noun snake_case pattern (get_issue, find_related_code, check_existing_fix, search_issues). repo_contribution_rules breaks the pattern by dropping the verb, but it is still readable and unambiguous.
Five tools is well-scoped for a narrow triage workflow, and each one maps to a distinct decision an agent needs to make before claiming an issue. Nothing appears redundant or padding the surface.
The read-only triage lifecycle is well covered: discover an issue, search related issues/code, verify no existing fix, and check contribution rules before acting. Gaps are minor (no full untruncated issue body, no direct PR inspection or comment listing beyond what get_issue returns), but an agent can work around them.