GitHub MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | Yes | GitHub personal access token with repo or public_repo scope |
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| github_set_tokenA | Set the GitHub personal access token for authentication |
| github_list_pull_requestsB | List all pull requests in a repository with full details including creator, labels, and optionally comments and pipeline status |
| github_get_pr_commentsA | Get all comments (issue comments and review comments) for a specific pull request |
| github_get_pr_checksA | Get CI/CD check runs and status for a specific pull request |
| github_get_pr_detailsA | Get detailed information about a specific pull request including files changed, commits, and optionally the full diff |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| GitHub Pull Requests | Access GitHub pull requests for repositories |
| GitHub Repository | Access GitHub repository information |
TDQS
Scored across 5 tools
Each tool targets a distinct aspect of GitHub PR workflows: authentication, listing, comments, checks, and detailed info. There is no functional overlap, so an agent can easily select the appropriate tool based on the task.
All tools follow a consistent github_verb_noun pattern (set_token, list_pull_requests, get_pr_details, etc.). The naming is uniform and predictable, making the tool set easy to navigate.
With five tools, the server is well-scoped around pull request operations. Each tool serves a clear purpose without redundancy, falling comfortably within the ideal range for a focused server.
The tool set is read-only for pull requests, lacking create, update, or delete operations. Despite the server name suggesting broad GitHub coverage, no issues or repository management are included, leaving significant gaps for typical workflows.