github-mcp
Related Servers
Alternatives to github-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityNot gradedmaintenanceA Model Context Protocol server that provides comprehensive GitHub integration for Claude Desktop, allowing users to manage repositories, issues, and pull requests. It supports file operations, branch management, and repository searches through natural language commands.538 npm-
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that connects Claude AI directly to the GitHub API, enabling natural language queries for live repository data, issues, PRs, and contributions.1-
- AlicenseNot gradedqualityCmaintenanceA Model Context Protocol (MCP) server that enables AI assistants like Claude to interact with the GitHub API directly.19 npmMIT
- FlicenseNot gradedqualityNot gradedmaintenanceModel Context Protocol server that enables interaction with GitHub repositories, issues, pull requests, and search functionality through natural language.1-
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI assistants like Claude to interact with GitHub repositories, issues, and pull requests.10 npmMIT
- AlicenseAqualityCmaintenanceA local MCP server that lets Claude Desktop access GitHub via a personal access token, with tools for repos, issues, PRs, code search, and more.9538 npmISC
TDQS
Scored across 26 tools
Each tool targets a distinct resource-action pair, such as list_repos vs get_repo vs create_repo. Even similar tools like get_issue and get_pull_request operate on different object types with clear descriptions.
All tools use snake_case with a consistent verb_noun pattern: list_* for listings, get_* for retrieval, create_* for creation, and delete_*/merge_*/trigger_* for actions. There are no mixed conventions or vague verbs.
With 26 tools, the server is larger than the typical 3-15 scope, but GitHub's broad API justifies this size. Every tool serves a distinct purpose with no redundancy, so the count feels appropriate for the domain.
The server covers core GitHub workflows: repository, branch, file, issue, pull request, workflow, search, and user operations. Minor gaps like updating or deleting repositories are missing, but agents can work around them using existing tools.