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 repository access and administration, contents, and pull requests permissions. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_prB | Create a pull request |
| comment_on_prB | Add a comment to a pull request |
| get_prB | Get details about a pull request |
| list_prsB | List pull requests for a repository |
| merge_prC | 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 5 tools
Each tool targets a distinct PR operation: create, comment, get, list, and merge. There is no overlap or ambiguity between the actions.
The naming follows a predictable verb_noun/reference pattern (create_pr, get_pr, list_prs, merge_pr), with the only minor deviation being comment_on_pr using an extra preposition. Overall, the convention is consistent and readable.
With 5 tools focused entirely on pull request management, the count is well-scoped for a single-purpose server. Each tool serves a clear need without redundancy.
The core PR lifecycle is covered: create, read, list, comment, and merge. Missing operations like updating a PR or closing without merging are minor gaps that agents can work around, but the surface is mostly complete.