Skip to main content
This feature is available exclusively as part of the Pro plan. Please refer to our pricing page for more information about our plans and features.
Connect CodeRabbit to external tools and data sources through the Model Context Protocol (MCP) integration. This allows CodeRabbit to serve as the MCP client and provides richer contextual understanding for enhanced code reviews.

What MCP integration enables

Code reviews

Enhanced analysis with external context and documentation

Code suggestions

Improved validation using your organization’s knowledge

PR chat

Access to relevant documentation and project information

Supported integrations

Access your documentation, project management tools, knowledge bases, Figma designs, and more through MCP servers.

Considerations

CodeRabbit as MCP client: CodeRabbit acts as the MCP client, not the server. It ingests data from your connected MCP servers.
Data relevance: Consider what MCP data will be helpful for code reviews. CodeRabbit uses this data for analysis, validation, and chat interactions.
Faster integrations: This approach unlocks integrations without waiting for formal CodeRabbit support. If a tool has an MCP server, CodeRabbit can connect to it.

Setup

1

Navigate to integrations

Go to the Integrations page within your CodeRabbit app settings: app.coderabbit.ai/integrations
2

Add MCP integration

Click New MCP Server and provide your server connection details along with a descriptive name.It’s also recommended to fill the User guidance field. See User guidance for details.
3

Complete authentication

Complete the authentication process for your MCP server following the prompts.
4

Configure tools

Enable or disable individual MCP tools for each server based on your needs.

How it works

CodeRabbit automatically calls relevant MCP tools during analysis to:

Gather context

Collects additional review context from your connected data sources

Enhance comments

Validates and enriches suggested review comments with relevant information
Enhanced review comments will include enriched insights while maintaining your existing workflow. Tools used during analysis are listed under “Additional context used.”

User guidance

The User guidance field is free-text instructions that CodeRabbit’s AI agent reads before using your MCP server. Use it to tell the agent what information is available, what to look for, and why it matters for code reviews. Some MCP servers need no additional guidance—the agent can figure out how to use their tools on its own. But many servers benefit from explicit context, especially when:
  • The server stores a wide variety of content (for example, a Notion workspace covering engineering specs, meeting notes, HR policies, and runbooks)
  • The server uses internal naming conventions or project keys that the agent can’t guess
  • The server is a custom in-house tool whose purpose isn’t obvious from its tool names alone
  • Resources are organized in non-standard hierarchies that the agent can’t automatically navigate

What to include in user guidance

Good user guidance answers three questions for the agent:
  1. What is stored here? Describe the kind of information available on this MCP server.
  2. What should CodeRabbit look for? Narrow the scope to what’s relevant for code reviews.
  3. How is it organized? Provide naming conventions, key formats, or URL patterns the agent needs to find the right resources.

Example configurations

Notion workspaces can contain many different types of content. Tell the agent which pages or databases are relevant to code reviews:
This Notion workspace contains our engineering documentation.
For code reviews, look in the "Engineering" space—specifically:
- "Architecture Decisions" for design rationale
- "API Contracts" for interface specifications
- "Service Runbooks" for operational context

Do not pull content from HR, Finance, or Company-wide spaces.

URL template placeholders

When guidance includes URLs that change per pull request, use placeholders that CodeRabbit automatically expands with values from the current PR:
https://jenkins.company.com/job/{workspace}/job/{repo}/job/PR-{pr}/

Available placeholders

PlaceholderDescriptionExample value
{repo}, {repo name}, {repository}Repository namemy-backend
{pr}, {pr number}Pull request number42
{mr}, {mr number}Merge request number (GitLab)42
{workspace}, {owner}, {org}Organization or workspaceacme-corp
{project}Project name (Azure DevOps)MyProject
Placeholders are case-insensitive. {repo}, {REPO}, and {Repo} all work the same way.