github-pr-control-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | Alias for GITHUB_READ_TOKEN. | |
| GITHUB_APP_ID | No | GitHub App ID for GitHub App authentication. | |
| GITHUB_READ_TOKEN | No | GitHub personal access token for read operations. Also accepted as GITHUB_TOKEN. | |
| GITHUB_WRITE_TOKEN | No | GitHub personal access token with write permissions. Required for write tools unless GITHUB_WRITE_ENABLED is set. | |
| GITHUB_WRITE_ENABLED | No | Set to 'true' to enable write tools using the read token (single-token setup). | |
| GITHUB_APP_PRIVATE_KEY | No | Inline GitHub App private key (with escaped newlines). | |
| GITHUB_INSTALLATION_ID | No | GitHub App installation ID. | |
| GITHUB_APP_PRIVATE_KEY_PATH | No | Path to the GitHub App private key file. |
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
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_prsA | List pull requests with multi-page pagination and a compact triage-oriented response. |
| get_prA | Fetch pull request metadata, merge state, counts, labels, and branch SHAs. |
| get_pr_diffA | Fetch a raw unified diff. Use offset and limit to page through very large pull requests. |
| list_pr_commentsA | List both inline review comments and top-level PR conversation comments with pagination. |
| post_review_commentA | Post a single inline comment at a diff line. Write access must be explicitly enabled. |
| submit_reviewA | Submit an APPROVE, REQUEST_CHANGES, or COMMENT review. Write access must be explicitly enabled. |
| add_labelsA | Add one or more labels to a pull request. Existing labels are preserved. |
| request_changesA | Submit a REQUEST_CHANGES review with a required explanation. Write access must be explicitly enabled. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| triage_pull_request | Opt-in read-only workflow for summarizing a PR, its risk, and the next review actions. |
| review_pull_request | Opt-in evidence-first code-review workflow that drafts findings without publishing them. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Most tools are clearly distinct, but submit_review and request_changes overlap significantly since request_changes is just a specific review type. Similarly, post_review_comment vs. submit_review with COMMENT type could cause confusion. Descriptions help, but these boundary areas could lead to misselection.
All tools follow a consistent verb_noun pattern with snake_case (list_prs, get_pr_diff, submit_review, add_labels). No mixed conventions or stylistic deviations appear.
8 tools is well-scoped for a pull-request control server, covering list, get, diff, comments, reviews, and labels without unnecessary bloat.
The set thoroughly covers review workflows (comments, reviews, labels) and basic read operations, but lacks PR update, merge, or close operations, which are minor gaps for a 'control' server.