A
licenseNot graded
qualityD
maintenanceEnables AI agents to perform GitHub analytics and management tasks, including repository analysis, PR summarization, issue triage, release notes generation, and contributor statistics.
16
MIT
GitHub MCP Server
by radireddy
Related Servers
Alternatives to GitHub MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI assistants to search and inspect code repositories, manage issues and pull requests, and analyze user contributions.13MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to access and analyze GitHub profile data, providing insights on repositories, commit history, coding patterns, and generating portfolio summaries for developers and recruiters.82MIT
- FlicenseNot gradedqualityCmaintenanceEnables autonomous coding agents to inspect Git commits, create pull requests, parse issue threads, and post reviews on GitHub repositories.-
- AlicenseBqualityBmaintenanceEnables AI agents to interact with GitHub (search repos, read files, issues, PRs), analyze code for quality and issues, and manage tasks with priority sorting.7MIT
- 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
TDQS
A4.1/5.0
Scored across 6 tools
Disambiguation4/5
Most tools have distinct purposes focused on different aspects of GitHub activity (PRs authored, reviews, comments, stats), but there is some overlap between getCommentImpact and getReviewComments/getUserComments in analyzing comments. The descriptions help clarify differences, but an agent might occasionally confuse which tool to use for comment-related analysis.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern with 'get' as the verb (e.g., getAuthoredPRs, getCommentImpact, getPRReviews). The naming is uniform and predictable, using camelCase throughout without any deviations or mixed conventions.
Tool Count4/5
With 6 tools, the count is reasonable for a GitHub analytics server, but it feels slightly thin for comprehensive coverage. The tools focus on user activity metrics, missing broader operations like repository management or issue handling, which might limit scope. However, each tool serves a clear purpose within this niche.
Completeness3/5
The toolset covers user-centric analytics well (e.g., PRs, reviews, comments, stats), but there are notable gaps for a GitHub server, such as no create, update, or delete operations, and missing tools for repositories, issues, or code search. This limits agents to read-only analysis without full lifecycle coverage.
Maintenance
ActivityInactive
ResponsivenessNo issues