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.140 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.137,300 npm91,120MIT
- AlicenseAqualityCmaintenanceA lightweight MCP server that exposes GitHub tools for searching repositories, listing issues, and reading file contents.3494 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 18 tools
Each tool targets a clearly distinct resource and action. The potential overlap between search_issues_tool and list_issues_tool is resolved by their descriptions (global search vs. per-repo listing that excludes PRs). Workflow and PR inspection tools are also well separated by specific purposes.
All 18 tool names follow a consistent snake_case verb_noun pattern with a uniform _tool suffix. Examples include get_issue_tool, list_pull_requests_tool, and trigger_workflow_tool, with no mixing of conventions.
With 18 tools, the set is slightly above the ideal 3–15 range but still reasonable for covering multiple GitHub subdomains: issues, PRs, Actions, code search, and repository files. No tool appears redundant or trivial.
The surface has significant gaps for a GitHub workflow: there is no create_pull_request_tool and no merge_pull_request_tool, making it impossible to open or merge a PR through this server. Other gaps include repository creation and branch operations, which will cause agent failures for common tasks.