CodeRabbit MCP Server

A Model Context Protocol (MCP) server for interacting with CodeRabbit AI reviews on GitHub pull requests. This server enables Large Language Models (LLMs) to analyze, understand, and implement CodeRabbit suggestions programmatically.

Features

• Get CodeRabbit Reviews: Retrieve all CodeRabbit reviews for a specific pull request
• Review Details: Get detailed information about specific reviews including configuration and files reviewed
• Extract Comments: Get individual line comments with AI prompts and suggestions
• Comment Details: Deep dive into specific comments with context and fix examples
• Resolve Comments: Mark comments as addressed, won’t fix, or not applicable
• Automated Workflow Prompt: Use /coderabbit-review slash command for complete review processing

Quick Start

Installation (NPX - Recommended)

No installation required! Run directly with npx:

# Install the latest stable version explicitly
npx coderabbitai-mcp@latest

Prerequisites

1. GitHub Personal Access Token: Create at
   • Required scopes: repo (for private repos) or public_repo (for public only)
2. Node.js 18+: Required for running the server

Configuration

Claude Desktop Configuration

To use the CodeRabbit MCP server in Claude Desktop, add it to your configuration file:

Configuration file locations:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%/Claude/claude_desktop_config.json
• Linux: ~/.config/Claude/claude_desktop_config.json

Step-by-step setup:

1. Open your Claude Desktop configuration file (create it if it doesn’t exist)
2. Add the CodeRabbit MCP server configuration:

{
  "mcpServers": {
    "coderabbitai": {
      "command": "npx",
      "args": ["coderabbitai-mcp@latest"],
      "env": {
        "GITHUB_PAT": "ghp_your_token_here"
      }
    }
  }
}

3. Replace ghp_your_token_here with your actual GitHub Personal Access Token
4. Save the file and restart Claude Desktop

Claude Code Configuration

To use the CodeRabbit MCP server in Claude Code, configure it in your project:

Step-by-step setup:

1. Create a .claude directory in your project root (if it doesn’t exist):

   mkdir .claude
   

2. Create or edit .claude/config.json:

{
  "mcpServers": {
    "coderabbitai": {
      "command": "npx",
      "args": ["coderabbitai-mcp@latest"],
      "env": {
        "GITHUB_PAT": "ghp_your_token_here"
      }
    }
  }
}

3. Replace ghp_your_token_here with your actual GitHub Personal Access Token
4. The server will be available next time you start Claude Code in this project

Pro tip: For security, you can use environment variables instead of hardcoding the token:

{
  "mcpServers": {
    "coderabbitai": {
      "command": "npx",
      "args": ["coderabbitai-mcp@latest"],
      "env": {
        "GITHUB_PAT": "${GITHUB_PAT}"
      }
    }
  }
}

Then set the GITHUB_PAT environment variable in your shell before starting Claude Code.

Usage

Automated Review Processing (Recommended)

Use the built-in MCP prompt for complete workflow automation:

/coderabbit-review owner:bradthebeeble repo:wiseguys pullNumber:15

This prompt automatically:

• Finds and analyzes CodeRabbit reviews
• Classifies issues by priority (high/medium/low)
• Gets your approval before making changes
• Systematically implements fixes
• Marks resolved comments in CodeRabbit
• Provides a completion summary

Manual Tool Usage

Integration Requirements

Supported AI Clients

• Claude Desktop: Full support with configuration
• Claude Code: Project-level MCP integration with /coderabbit-review prompt
• Other MCP Clients: Any client supporting the Model Context Protocol

Authentication

The GitHub Personal Access Token needs these permissions:

• repo (for private repositories) or public_repo (for public only)
• read:org (if accessing organization repositories)

Architecture

• TypeScript: Fully typed implementation with Zod validation
• MCP SDK: Built on the official Model Context Protocol SDK
• Modular Design: Each tool is implemented in its own module
• MCP Prompts: Automated workflows available as slash commands

API Rate Limits

The server respects GitHub’s API rate limits:

• 5,000 requests/hour for authenticated requests
• Automatically handles rate limit responses

Contributing

1. Fork the repository
2. Create a feature branch: git checkout -b feature-name
3. Make your changes and add tests
4. Run the build: npm run build
5. Submit a pull request

License

MIT

Support

• Issues: GitHub Issues
• Discussions: GitHub Discussions
• Documentation: Full examples available in EXAMPLES.md