A
licenseNot graded
qualityC
maintenanceEnables AI agents to manage GitHub repositories, branches, issues, pull requests, releases, and actions through natural language.
221 npm
5
MIT
GitHub Master MCP
Related Servers
Alternatives to GitHub Master MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables AI assistants to inspect local Git repositories and interact with the GitHub API for reading commits, diffs, files, issues, comments, pull requests, and project boards.10130 npmISC
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with GitHub via natural language, supporting repository management, issue tracking, file commits, and more.ISC
- FlicenseNot gradedqualityBmaintenanceEnables AI applications to retrieve GitHub repository information, manage issues, and monitor workflow statuses through the GitHub REST API.-
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to manage GitHub repositories and automate workflows through natural language.-
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to interact with GitHub directly by fetching repository information, creating issues, and triggering repository_dispatch events through natural language.MIT
TDQS
B3.2/5.0
Scored across 30 tools
Disambiguation4/5
Most tools map to a clear resource+action (repos, branches, commits, PRs, issues, releases, Actions, local files), and the local-vs-GitHub distinction is spelled out in descriptions. Two overlaps remain: commit_changes vs commit_and_push vs push_branch (the combined tool is a strict superset of the other two), and analyze_project reporting Git status overlaps with git_status.
Naming Consistency4/5
The dominant pattern is snake_case verb_noun (list_repositories, create_branch, merge_pull_request, read_project_file), applied consistently across nearly all tools. Deviations are minor: github_whoami uses a namespace prefix plus a non-verb, and git_status/git_diff are bare git-style names rather than verb_noun.
Tool Count3/5
30 tools is above the comfortable range, though the server genuinely spans several sub-domains (GitHub API, Actions, local git, local file/script operations). The count is inflated by redundancy: commit_and_push duplicates commit_changes + push_branch, and analyze_project partially duplicates git_status plus file-listing tools.
Completeness4/5
Core lifecycle is well covered: open/fork/create repo, branch, edit files, diff, commit, push, open PR, merge PR, create issue, create release, inspect and rerun workflows. Gaps are in the issue/PR secondary surface — no update/close issue, no comment on issues or PRs, no get-single-PR details, no branch deletion.
Maintenance
ActivityMaintained
ResponsivenessNo issues