A
licenseNot graded
qualityB
maintenanceMCP server providing maximum practical control over GitHub via REST and GraphQL APIs, exposing 22 tools for repository management, file operations, issues, PRs, Actions, and more.
MIT
GitHub MCP Server
by Pawangunjkar
Related Servers
Alternatives to GitHub MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides tools for interacting with the GitHub API, enabling AI assistants to query repositories, pull requests, issues, commits, users, and more.305 npmISC
- AlicenseBqualityCmaintenanceMCP server that exposes GitHub operations as tools for AI agents, enabling code search, issue management, and PR review.12MIT
- AlicenseNot gradedqualityBmaintenanceMCP server that wraps the GitHub REST API into tools for repo queries, issue/PR management, code review, search, and authentication, letting coding agents operate GitHub directly in conversations.6 npmMIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that enables GitHub API operations such as managing repositories, issues, and pull requests through natural language.305 npmISC
- FlicenseNot gradedqualityCmaintenanceMCP server exposing tools to fetch GitHub repository details, issues, and commits, enabling AI agents to query and summarize GitHub data via local LLMs.-
TDQS
B3/5.0
Scored across 73 tools
Disambiguation2/5
Multiple tools have overlapping purposes, such as github_list_repos, github_list_user_repos, and github_list_org_repos, where the first already supports owner filtering. Similarly, close_issue and close_pr duplicate the state-changing capabilities of update_issue and update_pr, creating ambiguity about the preferred tool. While descriptions are clear, the boundaries between these tools are not distinct enough for an agent to reliably choose.
Naming Consistency5/5
All tool names follow a consistent 'github_verb_noun' pattern using snake_case, such as github_list_repos, github_create_branch, and github_merge_pr. The prefix and verb-first structure are uniform across the entire set, making the naming highly predictable and easy to navigate.
Tool Count1/5
With 73 tools, this server vastly exceeds the typical 3-15 tool range and even the 50+ extreme threshold. Many tools are redundant or could be consolidated (e.g., repo listing variants, close vs update), inflating the count and overwhelming agents with too many choices.
Completeness3/5
The server provides broad coverage across repos, branches, files, PRs, issues, workflows, releases, users, search, gists, and notifications. However, notable gaps exist, such as lack of commit history APIs, no update for gists or releases, and no PR review submission, which are significant for a complete GitHub lifecycle.
Maintenance
ActivitySlowing
ResponsivenessNo issues