F
licenseNot graded
qualityB
maintenanceEnables AI agents to interact with GitHub repositories and issues through MCP tools, supporting listing repositories, listing and searching issues, and retrieving specific issues via the GitHub REST API.
-
@sumirati/mcp-github
by sumirati
Related Servers
Alternatives to @sumirati/mcp-github
No user-submitted related servers found.
Related Servers
- AlicenseAqualityNot gradedmaintenanceEnables AI agents to interact with GitHub repositories through the GitHub REST API for managing files, issues, and repository metadata. It supports both read operations like searching code and write operations such as creating repositories and updating issue comments.9-
- FlicenseNot gradedqualityCmaintenanceEnables large language models to explore, inspect, and analyze GitHub repositories through natural-language queries, using MCP tools to retrieve repository data, file structures, file contents, and code search results from the GitHub REST API.-
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to interact with GitHub via MCP, managing repositories, issues, PRs, and analyzing repository health through tools like list_repositories, read_issues, create_issue, comment_on_pr, and analyze_repo_health.-
- FlicenseNot gradedqualityCmaintenanceEnables read-only browsing and querying of GitHub repositories, including listing repos, reading files, fetching READMEs, searching code, and viewing commit history via MCP.-
- FlicenseNot gradedqualityBmaintenanceEnables AI applications to retrieve GitHub repository information, manage issues, and monitor workflow statuses through the GitHub REST API.-
TDQS
A3.8/5.0
Scored across 5 tools
Disambiguation3/5
The discover/execute pair is clearly distinct from each other, and the three get_* tools are distinct among themselves. However, github_execute_action can perform any of the 75 catalog actions, which likely includes the read operations covered by get_file_contents, get_repository, and get_commit, creating overlap. The 'eager daily driver' framing helps, but an agent must still decide between the direct tool and the generic executor.
Naming Consistency3/5
All names use snake_case, but two conventions coexist: the meta tools use a github_ namespace prefix (github_find_actions, github_execute_action) while the direct tools use bare get_* verbs (get_file_contents, get_repository, get_commit). The get_* trio is internally consistent, but the mixed prefixing and differing verb styles make the set only partially predictable.
Tool Count4/5
Five tools is a compact, well-scoped surface for what is effectively a 75-action GitHub catalog, avoiding the bloat of exposing every action individually. The three eager tools are somewhat redundant given execute_action, but they justify themselves as high-frequency shortcuts. The count is reasonable and no tool feels extraneous.
Completeness4/5
The catalog-plus-executor design claims coverage of PRs, issues, releases, workflows, collaborators, webhooks, variables, and security alerts, which is broad lifecycle coverage for a GitHub server. Discovery via github_find_actions fills the gap of not knowing action names. Minor gaps exist in that nothing is eager for write operations and catalog completeness depends entirely on the advertised 75 actions being real and correct.
Maintenance
ActivityMaintained
ResponsivenessNo issues