GitHub MCP Server
Related Servers
Alternatives to GitHub MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceAn MCP server that enables Claude and other compatible LLMs to interact with the GitHub API, supporting features like creating issues, retrieving repository information, listing issues, and searching repositories.4-
- 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.9379 npmISC
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that enables AI assistants like Claude to interact with the GitHub API directly.7 npmMIT
- FlicenseNot gradedqualityDmaintenanceA working MCP server that connects to the real GitHub API, enabling users to manage repositories, issues, pull requests, and more through natural language in Claude Desktop.-
- 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.379 npmISC
- AlicenseAqualityDmaintenanceGitHub MCP server for Claude Code, Cursor, Cline, Windsurf, and any MCP-compatible client. Exposes GitHub tools (issues, pull requests, code search, file content) to your LLM via the Model Context Protocol.7MIT
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: create-issue handles issue creation, get-repo-info retrieves repository details, list-issues lists existing issues, and search-repos searches for repositories. There is no overlap in functionality, making tool selection straightforward for an agent.
The tools follow a consistent verb-noun pattern with hyphens (e.g., create-issue, get-repo-info), which is predictable and readable. However, there is a minor deviation in 'get-repo-info' where 'info' is appended, slightly breaking the pure verb-noun convention compared to others like 'list-issues'.
With only 4 tools, the set feels thin for a GitHub server, lacking common operations like updating/deleting issues, managing pull requests, or accessing repository contents. While the tools cover basic functions, the count is borderline low for the broad scope of GitHub interactions.
There are significant gaps in the tool surface for a GitHub domain. Missing operations include update_issue, delete_issue, create_pull_request, get_pull_request, and repository management actions (e.g., create_repo, update_repo). This incomplete coverage will likely cause agent failures when trying to perform common GitHub workflows.