F
licenseA
qualityC
maintenanceMCP server that lets AI agents interact with GitHub using natural language, supporting operations like creating repositories, issues, and commits.
5
-
GitHub PR Issue Analyser
by saidsef
Related Servers
Alternatives to GitHub PR Issue Analyser
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI agents to directly manage GitHub repositories, including PRs, issues, and code search, using natural language.MIT
- AlicenseNot gradedqualityBmaintenanceA production-grade MCP server that provides LLMs with safe, structured, tool-based access to GitHub repositories, including issue management, semantic search, and guarded write operations.MIT
- FlicenseNot gradedqualityDmaintenanceMCP server that enables AI agents to perform GitHub operations like creating repositories, issues, and commits through natural language.-
- FlicenseAqualityCmaintenanceMCP server that enables AI agents to perform GitHub operations (repos, issues, commits, PRs) via natural language, integrated with hosts like Antigravity.8-
- AlicenseBqualityCmaintenanceA comprehensive MCP server that exposes 73 GitHub API tools for managing repositories, pull requests, issues, actions, releases, search, and more, enabling natural language control of GitHub.73MIT
TDQS
A3.5/5.0
Scored across 54 tools
Disambiguation4/5
Within GitHub domains, most tools target distinct actions/resources, and descriptions clarify boundaries. However the PR comment/review cluster (add_pr_comments, add_inline_pr_comment, update_pr_comment, reply_to_review_comment, submit_review) has overlapping purposes that require careful reading, and auxiliary UI/skill tools add another layer.
Naming Consistency4/5
The vast majority follow github_<verb>_<noun> snake_case (e.g., github_create_issue, github_list_repos). Deviations include the bare 'choose', the noun-style 'github_pr_issue_analyser_ui', and inconsistent repo vs repository abbreviations (github_list_repos vs github_get_repository_file), but the core set is predictable.
Tool Count2/5
54 tools far exceeds the 3-15 sweet spot and the rubric's 25+ threshold for 'too many'. The server spans many domains—PRs, issues, releases, projects, user activity, UI rendering, skills—so the surface is heavy and likely overwhelming for an agent.
Completeness4/5
The server covers a broad lifecycle: issue create/get/update/list/search/milestone/assignees, PR create/update/review/merge/diff/status, releases/tags create/list/update/delete, and project board operations. Minor gaps exist (e.g., explicit close/delete issue or comment, full repo creation), but core workflows are well covered.
Maintenance
ActivityActive
ResponsivenessResponsive