GitHub PR MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-pull-request-dataC | Get detailed information about a GitHub Pull Request including files, diff, comments, and reviews |
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 possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as retrieving detailed pull request data, making it distinct by default.
The single tool name follows a clear verb_noun pattern ('get-pull-request-data'), which is consistent within this minimal set. There are no other tools to compare against, so no inconsistency can arise.
A server named 'GitHub PR MCP Server' implies a focus on pull requests, but having only one tool is too few for this domain. It lacks essential operations like creating, updating, merging, or listing pull requests, making it severely limited in scope.
The tool surface is severely incomplete for a GitHub PR server. It only provides read access to pull request data, missing core functionalities such as creating, updating, commenting on, or merging pull requests, which are critical for typical workflows.