Skip to main content
Glama
subhamyadav580

PR Reviewer MCP Server

by subhamyadav580
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GITHUB_ORGYesThe GitHub organization name.
GITHUB_TOKENYesA 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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_org_repositoriesA

List all repositories in the configured GitHub org.

list_open_pull_requestsA
List all open pull requests for a repository.

Args:
    repo_full_name: Full repo identifier in "owner/repo" format.
get_pull_request_detailsA
Get metadata for a specific pull request.

Returns title, description, author, changed file count, additions,
deletions, and commit count — useful for understanding PR scope before
reading the diff.

Args:
    repo_full_name: Full repo identifier in "owner/repo" format.
    pr_number: The pull request number.
get_pull_request_diffA
Get the file-by-file diff for a specific pull request.

Returns each changed file with its status (added/modified/removed),
line-level additions and deletions, and the raw unified diff patch.

Args:
    repo_full_name: Full repo identifier in "owner/repo" format.
    pr_number: The pull request number.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.2/5.0

Scored across 4 tools

Disambiguation5/5

Each tool serves a clear, non-overlapping purpose: listing repos, listing PRs, fetching PR metadata, and fetching PR diffs. No ambiguity in intent.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with snake_case (e.g., get_pull_request_details, list_open_pull_requests), making them predictable.

Tool Count5/5

4 tools is well-scoped for a PR review server, covering the essential read operations without bloat or insufficiency.

Completeness5/5

The tool set covers the full read-only PR review workflow: discover repositories, list PRs, and examine details and diffs. No obvious gaps for its intended purpose.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources