pr-reviewer-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | Yes | Fine-grained PAT with Pull requests (read/write) and Contents (read) permissions | |
| GOOGLE_API_KEY | Yes | API key from Google AI Studio |
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_open_prsA | List open pull requests for a GitHub repo, so you can decide which to review. |
| get_pr_diffA | Fetch the raw file-by-file diff for a pull request, with no AI review applied. |
| review_fileB | Run an AI code review on a single file within a pull request. |
| review_prA | Run a full AI code review on a pull request: fetches the diff, reviews every changed file in parallel, and returns a synthesized markdown review. |
| post_review_commentA | Post a review (typically the output of review_pr) as a comment on the 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 operation: listing PRs, fetching diffs, reviewing individual files, reviewing full PRs, and posting comments. No functional overlap.
All tool names follow a consistent verb_noun pattern in snake_case (list_open_prs, get_pr_diff, review_file, review_pr, post_review_comment), making them predictable.
Five tools is appropriate for a focused PR review server—enough to cover core functionality without being excessive or thin.
Covers the full review workflow (list, diff, review file, review PR, post comment). Lacks tools for approval or dismissal, but those are outside the stated scope.