MCP GitHub CrunchTools
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | Yes | GitHub Personal Access Token | |
| GITHUB_API_URL | No | API base URL (set for GHES) | https://api.github.com |
| GITHUB_DEFAULT_ORG | No | Default owner when a tool omits owner |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_issues_toolA | List issues for a GitHub repository (pull requests excluded). |
| get_issue_toolB | Get a single GitHub issue by number. |
| create_issue_toolB | Create a new issue in a GitHub repository. |
| create_issue_comment_toolA | Create a comment on a GitHub issue or pull request. |
| update_issue_toolA | Update a GitHub issue, including closing or reopening it. Set state="closed" to close an issue. Set state="open" with state_reason="reopened" to reopen. |
| list_pull_requests_toolB | List pull requests for a GitHub repository. |
| get_pull_request_toolA | Get a single GitHub pull request by number. |
| get_pull_request_diff_toolB | Get the unified diff for a GitHub pull request. |
| get_pull_request_checks_toolA | Get a CI verdict for a PR that distinguishes skipped from failed. Classifies every check-run and commit-status context into passed,
failing, pending, or skipped. SKIPPED checks are NOT failures. Use the
returned |
| update_pull_request_toolA | Update a GitHub pull request, including closing or reopening it. This does NOT merge. Set state="closed" to close a PR without merging. |
| get_file_content_toolA | Get the decoded text content of a file in a GitHub repository. |
| list_repo_tree_toolB | List the git tree (files and directories) of a GitHub repository. |
| search_code_toolB | Search for code across GitHub. Uses GitHub code search syntax (e.g., "addClass repo:jquery/jquery"). |
| search_issues_toolA | Search for issues and pull requests across GitHub. Uses GitHub issue search syntax (e.g., "is:open is:pr author:octocat"). |
| list_workflow_runs_toolA | List GitHub Actions workflow runs for a repository. |
| trigger_workflow_toolA | Trigger a fresh GitHub Actions run via the workflow_dispatch event. Use this to force a new build. Unlike rerun_workflow_run_tool (which
re-runs an existing run and is rejected by GitHub for runs older than 30
days), this starts a brand-new run regardless of when the workflow last
ran. The target workflow must declare an |
| rerun_workflow_run_toolB | Re-run all jobs in a GitHub Actions workflow run. |
| rerun_failed_jobs_toolA | Re-run only the failed jobs in a GitHub Actions workflow run. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 18 tools
Tools are mostly distinct, but there is potential confusion between rerun_workflow_run_tool and rerun_failed_jobs_tool, and between list_issues_tool and search_issues_tool, though the descriptions help differentiate them. The diff tool and get_pull_request_tool are clearly distinct. Overall, agents should select correctly with careful reading.
Most tool names follow a consistent verb_noun pattern (e.g., list_issues, create_issue, update_issue, get_pull_request). Minor deviations exist such as get_pull_request_diff_tool and get_pull_request_checks_tool, which are more specific but still follow the pattern. No mixed conventions or chaotic naming.
With 18 tools, the server is on the higher end of the recommended range but still reasonable for a GitHub MCP server covering issues, PRs, workflows, code search, and file access. Each tool has a distinct purpose, though some consolidation could be possible without losing functionality.
The server covers core workflows for issues, PRs, workflow runs, and code search, including create, read, update, and search operations. Missing operations include deleting issues/PRs, listing comments, and managing repositories, but these are not critical for typical agent tasks. The coverage is solid for the stated domain.