F
licenseNot graded
qualityC
maintenanceEnables MCP-connected AI agents to review GitHub pull requests and post meaningful inline review comments directly on them through natural language prompts.
-
github-pr-review-mcp
by jamesjfoong
Related Servers
Alternatives to github-pr-review-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to fetch GitHub pull request diffs and metadata, and post review comments directly through the MCP protocol.1MIT
- FlicenseNot gradedqualityCmaintenanceEnables automated GitHub pull request review through a multi-agent system using LangGraph and MCP tools, analyzing PR metadata, files, patches, comments, and policies with RAG, guardrails, HITL approval, and Langfuse observability.-
- FlicenseAqualityDmaintenanceEnables LLM clients to list, read, review, and comment on GitHub pull requests, turning an AI assistant into a fully capable code reviewer.61-
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to autonomously review GitHub Pull Requests by listing PRs, retrieving diffs, and submitting structured reviews.-
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to run security and code review on pull requests and diffs, exposing review_pr and review_diff capabilities with local-first analyzers and LLM explanations.2MIT
TDQS
A3.5/5.0
Scored across 14 tools
Disambiguation4/5
Each tool has a clear primary target—PR metadata, files, diff hunks, comments, reviews, pending review state, or submission—and the specialized helpers like validate_pr_comment_target and ensure_pending_review are distinct. Minor ambiguity remains between get_pr_files and get_pr_diff_hunks, and between get_pr_comments and get_pr_reviews/list_pending_review_comments, but descriptions generally disambiguate granularity.
Naming Consistency5/5
Tool names follow a consistent verb_noun pattern throughout: get_, add_, submit_, update_, ensure_, list_, analyze_, validate_, and review_. The naming style is uniform and the PR object is always clearly identified, making selection predictable.
Tool Count5/5
14 tools is well within the ideal scope for a PR review server. Each tool covers a distinct step of the workflow—from reading PR data and diff hunks to managing pending reviews and submitting—without meaningful redundancy.
Completeness4/5
The tool surface covers the core PR review lifecycle: fetching PR details, files, diff hunks, reviews/comments, analyzing code, creating/managing pending reviews, adding comments, validating targets, and submitting reviews. Notable minor gaps are the absence of explicit editing/deleting for pending review comments and no dismissal or revision-handling tools, but these do not dead-end the primary workflow.
Maintenance
ActivityInactive
ResponsivenessNo issues