GitHub MCP Server
Related Servers
Alternatives to GitHub MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceEnables analysis of GitHub Pull Requests, including details, diff, file lists, and review tracking.3-
- FlicenseAqualityCmaintenanceEnables LLM clients to list, read, review, and comment on GitHub pull requests, turning an AI assistant into a fully capable code reviewer.61-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to perform comprehensive GitHub pull request code reviews, including analysis of code patterns, complexity, and security issues, while managing review comments and ensuring compliance with team coding standards.2MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to autonomously review GitHub Pull Requests by listing PRs, retrieving diffs, and submitting structured reviews.-
- FlicenseNot gradedqualityDmaintenanceEnables the analysis of GitHub Pull Requests to extract metadata, commits, and code changes for structured AI insights. It also supports the optional creation of Notion pages to store and organize the resulting analysis.-
- FlicenseNot gradedqualityDmaintenanceEnables fetching and analyzing Gemini Code Assist reviews from GitHub pull requests, with smart defaults and pagination.-
TDQS
Scored across 5 tools
Each tool targets a distinct aspect of GitHub PR workflows: authentication, listing, comments, checks, and detailed info. There is no functional overlap, so an agent can easily select the appropriate tool based on the task.
All tools follow a consistent github_verb_noun pattern (set_token, list_pull_requests, get_pr_details, etc.). The naming is uniform and predictable, making the tool set easy to navigate.
With five tools, the server is well-scoped around pull request operations. Each tool serves a clear purpose without redundancy, falling comfortably within the ideal range for a focused server.
The tool set is read-only for pull requests, lacking create, update, or delete operations. Despite the server name suggesting broad GitHub coverage, no issues or repository management are included, leaving significant gaps for typical workflows.