github-mcp
Related Servers
Alternatives to github-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceAn MCP server that enables AI assistants to interact with GitHub via a fine-grained personal access token — pushing commits, managing branches, opening and merging PRs, creating issues, and reading repositories. It runs locally with no telemetry and supports a read-only mode.151MIT
- FlicenseNot gradedqualityDmaintenanceStandalone MCP server for GitHub that enables repository management, branch operations, pull request handling, and commit retrieval via tools listed in the README.1-
- AlicenseAqualityDmaintenanceAn MCP server that provides operational tooling over the GitHub API — issue triage, PR review monitoring, repo health audits, and team access reviews.111MIT
- AlicenseBqualityCmaintenanceMCP server that exposes GitHub operations as tools for AI agents, enabling code search, issue management, and PR review.12MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for the GitHub API, enabling file operations, repository management, search functionality, issues, pull requests, and more.85 npmMIT
- AlicenseBqualityBmaintenanceMCP server for the GitHub REST API: issues, PRs, repos; read always on, write env-gated.14MIT
TDQS
Scored across 7 tools
Each tool targets a distinct GitHub resource or action: file read/write, PR operations (single fetch, list, merge), health check, and Dependabot alerts. No overlapping functionality.
Most tools follow a verb_noun pattern (get_file, get_pr, list_prs, merge_pr, put_file), but 'health_check' deviates slightly as a noun_verb compound, and 'list_dependabot_alerts' uses a longer but still consistent verb_noun format.
Seven tools is well-scoped for a focused GitHub MCP server, covering key areas without being overwhelming or trivial.
The tool set lacks essential GitHub operations like creating PRs, managing issues, branches, or repository settings, leaving significant gaps for common workflows.