github-review-queue-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for the remote server. Default is 3000. | 3000 |
| PUBLIC_URL | No | Public origin for the remote server. The MCP endpoint is $PUBLIC_URL/mcp. | |
| TRUST_PROXY | No | Number of proxies in front of the server, used for per-IP rate limiting. | |
| GITHUB_SCOPE | No | GitHub OAuth scope. Default is repo; public_repo limits access to public repositories. | repo |
| GITHUB_TOKEN | No | Fine-grained GitHub token for local stdio use with Pull requests: read and write, Commit statuses: read, and Checks: read. | |
| GITHUB_API_URL | No | GitHub API URL for GitHub Enterprise Server. | |
| GITHUB_CLIENT_ID | No | GitHub OAuth App client ID for the remote server. | |
| GITHUB_OAUTH_URL | No | GitHub OAuth URL for GitHub Enterprise Server. | |
| GITHUB_CLIENT_SECRET | No | GitHub OAuth App client secret for the remote server. | |
| TOKEN_ENCRYPTION_KEY | No | 32 random bytes, base64 encoded; encrypts stored GitHub tokens. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_review_requestsA | Lists open pull requests where your review is requested, most recently updated first. Optionally limited to one repository. |
| get_pull_requestB | Returns a pull request's summary: title, author, branches, size, mergeability, requested reviewers, each reviewer's latest review, and the description (first 4,000 characters). |
| list_pull_request_filesA | Lists the files a pull request changes, with additions and deletions per file. Set include_patch to also get each file's diff (first 3,000 characters per file). |
| get_pull_request_checksA | Returns the CI result for a pull request's latest commit: an overall state, counts per outcome, and every failing check with its link and summary. |
| comment_on_pull_requestA | Posts a comment on a pull request's conversation, as you. Everyone with access to the repository can see it. |
| submit_pull_request_reviewA | Submits a review on a pull request, as you: APPROVE, REQUEST_CHANGES, or COMMENT. REQUEST_CHANGES and COMMENT need a body. |
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 6 tools
Each tool targets a distinct resource and action: listing the review queue, fetching one PR, its files, its CI checks, posting a comment, and submitting a review. There is no overlap or confusingly similar pair.
All six tools follow a consistent snake_case verb_noun pattern (list_*, get_*, comment_on_*, submit_*). The repeated pull_request stem reinforces the domain without creating ambiguity.
Six tools is well-scoped for a focused PR review-queue workflow. Every tool earns its place with no redundancy or filler.
Covers the full review loop: find requests, inspect PR metadata/files/checks, comment, and submit a verdict. Minor gaps remain, such as reading existing conversation/thread replies or dismissing/updating a prior review, but no core workflow dead-ends.