github-pr-review
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_REPO | Yes | Your repository name | |
| GITHUB_OWNER | Yes | Your GitHub username or organization name | |
| GITHUB_TOKEN | Yes | Your 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 |
|---|---|
| list_open_prsA | List all open pull requests in the configured repository. |
| get_pr_diffB | Get the file changes and diff for a specific pull request. |
| get_pr_commentsA | Get all review comments on a specific pull request. |
| post_review_commentA | Post an inline comment on a specific file and line via a review submission. |
| approve_prC | Approve a pull request, optionally with a review message. |
| request_changesB | Request changes on a pull request with a review message. |
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 has a clearly distinct purpose: listing PRs, getting diffs, getting comments, posting inline comments, approving, and requesting changes. No overlap in functionality.
All tool names follow a consistent verb_noun pattern with underscores (e.g., approve_pr, get_pr_diff), making them predictable and easy to distinguish.
Six tools is an ideal size for a focused PR review server, covering the essential actions without being overwhelming or sparse.
The set covers the core PR review workflow (list, diff, comments, approve, request changes) but lacks features like merging or dismissing reviews, which are minor gaps given the server's specific scope.