GitHub MCP Server
Related Servers
Alternatives to GitHub MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceA simple MCP server that provides repository information (list repos, get repo details) using GitHub's public REST API, without needing any API keys or tokens.-
- 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-
- AlicenseAqualityCmaintenanceA lightweight MCP server that exposes GitHub tools for searching repositories, listing issues, and reading file contents.3305 npmISC
- -licenseNot gradedqualityAmaintenanceMCP Server for the GitHub API, enabling file operations, repository management, search functionality, and more.89,959 npm90,399MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server for managing your repositories on Forgejo/Gitea server.67Mozilla Public 2.0
- AlicenseNot gradedqualityDmaintenanceMCP server for the GitHub API, enabling file operations, repository management, search functionality, issues, pull requests, and more.71 npmMIT
TDQS
Scored across 5 tools
Each tool targets a distinct PR operation: create, comment, get, list, and merge. There is no overlap or ambiguity between the actions.
The naming follows a predictable verb_noun/reference pattern (create_pr, get_pr, list_prs, merge_pr), with the only minor deviation being comment_on_pr using an extra preposition. Overall, the convention is consistent and readable.
With 5 tools focused entirely on pull request management, the count is well-scoped for a single-purpose server. Each tool serves a clear need without redundancy.
The core PR lifecycle is covered: create, read, list, comment, and merge. Missing operations like updating a PR or closing without merging are minor gaps that agents can work around, but the surface is mostly complete.