GitHub MCP Agent 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 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 | {
"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 |
|---|---|
| search_codeC | Search for code in GitHub repositories. |
| list_issuesC | List issues in a GitHub repository. |
| get_pr_diffC | Get the diff for a pull request. |
| review_pr_diffB | Review a PR diff using ruff + legacy regex rules. Returns structured findings. |
| comment_pr_reviewB | Fetch PR diff, run code review, and post findings as review comments. |
| get_file_contentsB | Read a file from a GitHub repository. |
| create_issueA | Create a new issue in a GitHub repository. |
| create_prC | Create a new pull request. |
| create_or_update_fileB | Create or update a single file in a GitHub repository. |
| push_filesC | Push multiple files as a single commit. |
| add_issue_commentB | Add a comment to a GitHub issue or pull request. |
| merge_pull_requestC | Merge a pull request. |
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 12 tools
Most tools have distinct purposes, but `review_pr_diff` and `comment_pr_review` both involve PR review, which could cause slight ambiguity. However, their descriptions clarify the different outputs.
All tool names follow a consistent verb_noun pattern in snake_case, making them predictable and easy to understand. No mixing of conventions.
With 12 tools, the server covers core GitHub operations without being bloated or sparse. Each tool serves a clear purpose.
The tool set covers most common GitHub workflows (issues, PRs, files, code search) but lacks update/delete operations for issues and files, which may require workarounds.