GitHub PR Review MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | Yes | GitHub Personal Access Token with repo scope | |
| GITHUB_API_BASE_URL | No | Base URL for GitHub API (e.g., for GitHub Enterprise) | https://api.github.com |
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 |
|---|---|
| collect_pr_feedbackB | Collect PR review comments, issue comments, and review summaries for a PR. |
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 1 tool
With only one tool, there is no potential for confusion between tools. The tool's purpose is clearly described.
Single tool name follows a consistent verb_noun pattern ('collect_pr_feedback'), so no inconsistency exists.
A single tool for a PR review server is severely inadequate. Expected tools for PR listing, diff viewing, commenting, etc., are missing.
The tool surface is extremely incomplete. It only provides feedback collection, with no tools for creating, updating, or managing PRs or reviews.