MCP GitHub CrunchTools
Related Servers
Alternatives to MCP GitHub CrunchTools
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceMCP server for GitHub operations, providing tools for repository management, issues, pull requests, and code search.-
- AlicenseNot gradedqualityDmaintenanceMCP server for the GitHub API, enabling file operations, repository management, search functionality, issues, pull requests, and more.221 npmMIT
- AlicenseCqualityDmaintenanceA production-ready MCP server for GitHub operations, providing tools for repository management, issues, pull requests, and more via both MCP stdio and REST API.27MIT
- -licenseNot gradedqualityAmaintenanceMCP Server for the GitHub API, enabling file operations, repository management, search functionality, and more.124,024 npm91,671MIT
- AlicenseAqualityDmaintenanceA lightweight MCP server that exposes GitHub tools for searching repositories, listing issues, and reading file contents.3811 npmISC
- AlicenseNot gradedqualityCmaintenanceA Model Context Protocol (MCP) server that exposes GitHub tools for repository management, code search, issue creation, and pull request operations.1MIT
TDQS
Scored across 26 tools
Most tools have clearly distinct resource/action targets, and the descriptions specifically clarify tricky adjacent cases such as issue comments versus pull request comments and workflow rerun variants. The main mild overlap is around comment handling across issues and pull requests, but it is not severe enough to cause frequent misselection.
Tool names consistently use snake_case verb_noun phrasing with a uniform _tool suffix, such as list_issues_tool, create_pull_request_tool, and get_failed_job_logs_tool. The pattern is predictable throughout the entire set.
At 26 tools this server is heavy for a single MCP surface and sits at the upper boundary of what is comfortably scannable. The breadth of GitHub operations explains many of the tools, but the set could still benefit from grouping or trimming.
Core issue, pull request, Actions, repository search, and file-reading workflows are covered. However, notable gaps remain around PR review creation/approval, release listing or updates, and branch/commit operations, so agents may hit dead ends in common GitHub workflows.