GitHub PR Review MCP

A Model Context Protocol (MCP) server that provides GitHub PR review capabilities to LLMs in VSCode/Cursor and other compatible AI clients.

Features

🔍 MVP Feature 1: Review PRs in GitHub

• Get PR Reviews - Fetch all existing reviews for analysis

• Get PR Comments - Retrieve all comments and discussions

• Analyze PR Code - AI-powered code analysis with security checks and suggestions

• Get PR Files - List all changed files with additions/deletions

• Get PR Details - Comprehensive PR information including status, author, metrics

✍️ MVP Feature 2: Implement Feedback & Reply to Reviews

• Submit PR Review - Submit complete reviews with approval/changes/comments

• Add Comments - Add general or line-specific comments to PRs

• Reply to Reviews - Respond to existing review comments

• Update PRs - Modify PR title, description, or state

🎯 MVP Feature 3: Diff-Aware Inline Comments & Pending Reviews

• Get Diff Hunks - Retrieve diff hunks with precise line mapping for inline comments

• Validate Comment Targets - Verify if a line/path is valid in the PR diff before commenting

• Pending Review Management - Create, retrieve, and manage draft reviews

• List Draft Comments - View all pending comments before submitting a review

• No HTML Scraping - All operations use GitHub REST APIs for reliability

Related MCP server: GitHub MCP Agent Server

Quick Start

Prerequisites

• Node.js 20.19.0 or higher

• GitHub Personal Access Token with repo and read:user scopes

Installation

Option 1: Global Installation (Recommended)

npm install -g github-pr-review-mcp

Option 2: Development Setup

git clone https://github.com/jamesjfoong/github-pr-review-mcp.git
cd github-pr-review-mcp
npm install
npm run build

Setup

1. Get GitHub Token: Generate a Personal Access Token with scopes:

   • repo (full repository access)

   • read:user (read user profile data)

2. Configure Environment:

   cp .env.example .env
   # Edit .env and add your token:
   GITHUB_TOKEN=your_github_token_here

3. Configure in Cursor/VSCode: Add to your MCP settings (usually in ~/Library/Application Support/Cursor/User/globalStorage/rooveterinaryinc.cursor-small/settings/cline_mcp_settings.json):

   {
     "mcpServers": {
       "github-pr-review": {
         "command": "npx",
         "args": ["github-pr-review-mcp"]
       }
     }
   }

Available Tools

Usage Examples

Example 1: Review a PR

🤖: Please review PR #123 in microsoft/vscode

1. Get PR details: get_pr_details(owner: "microsoft", repo: "vscode", prNumber: 123)
2. Get changed files: get_pr_files(owner: "microsoft", repo: "vscode", prNumber: 123)
3. Analyze code: analyze_pr_code(owner: "microsoft", repo: "vscode", prNumber: 123)
4. Submit review: submit_pr_review(owner: "microsoft", repo: "vscode", prNumber: 123, body: "LGTM! Great work on...", event: "APPROVE")

Example 2: Implement Feedback

🤖: The reviewer asked me to fix the error handling in line 45 of src/utils.ts

1. Add line comment: add_pr_comment(owner: "owner", repo: "repo", prNumber: 123, body: "Fixed error handling as requested", path: "src/utils.ts", line: 45)
2. Update PR description: update_pr(owner: "owner", repo: "repo", prNumber: 123, body: "Updated PR description with changes made...")

Example 3: Draft Review with Inline Comments (New!)

🤖: Create a draft review with inline comments on PR #123

1. Ensure pending review exists: ensure_pending_review(owner: "owner", repo: "repo", prNumber: 123, body: "Draft review comments")
2. Get diff hunks to find valid lines: get_pr_diff_hunks(owner: "owner", repo: "repo", prNumber: 123)
3. Validate comment target: validate_pr_comment_target(owner: "owner", repo: "repo", prNumber: 123, path: "src/main.ts", line: 45, side: "RIGHT")
4. Add inline comment if valid: add_pr_comment(owner: "owner", repo: "repo", prNumber: 123, body: "Consider refactoring this method", path: "src/main.ts", line: 45)
5. List pending comments to verify: list_pending_review_comments(owner: "owner", repo: "repo", prNumber: 123)
6. Submit the review when ready: submit_pr_review(owner: "owner", repo: "repo", prNumber: 123, body: "Overall looks good!", event: "COMMENT")

Example 4: AI-Powered PR Review with Custom Prompt

🤖: Review PR #123 using AI with custom guidelines

1. Get review prompt: review_pr_with_prompt(owner: "owner", repo: "repo", prNumber: 123, customPrompt: "Focus on security vulnerabilities and performance issues")
2. Use the returned reviewPrompt with your LLM to generate a review
3. Format the LLM response into review comments
4. Submit review: submit_pr_review(owner: "owner", repo: "repo", prNumber: 123, body: "AI-generated review...", event: "COMMENT")

Example 5: Automated Code Analysis

The analyze_pr_code tool automatically detects:

• 🔒 Security issues: API key exposure, hardcoded passwords, XSS vulnerabilities

• 🧹 Code smells: Console statements, debugger statements, TypeScript any types

• 📊 Quality metrics: Large file changes, missing tests, complexity analysis

• ✅ Suggestions: Breaking large PRs, adding tests, security improvements

Development

AI Code Editors: If you're using Cursor, GitHub Copilot, or other AI code editors, this repository includes automatic configuration files:

• .cursor/rules/ - Project rules (always applied)

• .cursor/agents/ - Custom subagents for specialized tasks

• .cursor/skills/ - Agent skills for procedural workflows

• .github/copilot-instructions.md - GitHub Copilot instructions

• AGENTS.md - General AI agent instructions

Project Structure

github-pr-review-mcp/
├── src/
│   ├── index.ts          # Main MCP server entry point
│   ├── github-service.ts # GitHub API integration
│   ├── code-analyzer.ts  # Code analysis engine
│   └── types.ts          # TypeScript type definitions
├── dist/                 # Compiled JavaScript output
├── scripts/
│   └── setup.sh          # Automated setup script
└── package.json

Scripts

• npm run build - Compile TypeScript

• npm run dev - Development mode with auto-reload

• npm start - Run compiled server

• npm run prepublishOnly - Build before publishing

Contributing

1. Fork the repository

2. Create a feature branch: git checkout -b feature/amazing-feature

3. Make your changes

4. Add tests if applicable

5. Run npm run build to ensure it compiles

6. Submit a pull request

API Requirements

Your GitHub token needs these permissions:

• Repository access: repo scope for private repos, or public_repo for public repos only

• User data: read:user for accessing user profile information

• Optional: write:discussion for advanced discussion features

Troubleshooting

Common Issues

1. "GITHUB_TOKEN environment variable is required"

• Solution: Copy .env.example to .env and add your GitHub token

2. "Cannot find module" errors

• Solution: Run npm install to install dependencies

3. Rate limiting

• The server includes automatic rate limiting and retry logic

• GitHub API has limits: 5,000 requests/hour for authenticated requests

4. Permission errors

• Ensure your GitHub token has repo scope for the repositories you want to access

• For organization repos, you may need additional permissions

Debug Mode

Enable debug logging by setting in your .env:

DEBUG=true

Roadmap

Future Features

• 🔄 Auto-merge capabilities

• 🧪 Test execution integration

• 📈 PR metrics and analytics

• 🤖 Automated code fixes based on review comments

• 🔍 Advanced search and filtering

• 📊 Reporting and dashboards

License

MIT License - see LICENSE file for details.

Support

• 📚 Documentation: GitHub Wiki

• 💬 Discussions: GitHub Discussions

• 🐛 Issues: Report bugs

• 🔒 Security: See SECURITY.md

Author

James Jeremy Foong - @jamesjfoong

⭐ Star this repo if you find it useful!

🐛 Report issues on GitHub Issues

🤝 Contributing is welcome! See our contributing guidelines above.