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.
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.
Setup
Navigate to integrations
Go to the Integrations page within your CodeRabbit app settings: app.coderabbit.ai/integrations
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.Complete authentication
Complete the authentication process for your MCP server following the
prompts.
How it works
- During code reviews
- In chat interactions
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:- What is stored here? Describe the kind of information available on this MCP server.
- What should CodeRabbit look for? Narrow the scope to whatâs relevant for code reviews.
- How is it organized? Provide naming conventions, key formats, or URL patterns the agent needs to find the right resources.
Example configurations
- Notion
- Custom in-house MCP server
- Jenkins
- SonarQube
- Azure DevOps
Notion workspaces can contain many different types of content. Tell the agent which pages or databases are relevant to code reviews:
URL template placeholders
When guidance includes URLs that change per pull request, use placeholders that CodeRabbit automatically expands with values from the current PR:Available placeholders
| Placeholder | Description | Example value |
|---|---|---|
{repo}, {repo name}, {repository} | Repository name | my-backend |
{pr}, {pr number} | Pull request number | 42 |
{mr}, {mr number} | Merge request number (GitLab) | 42 |
{workspace}, {owner}, {org} | Organization or workspace | acme-corp |
{project} | Project name (Azure DevOps) | MyProject |
Placeholders are case-insensitive.
{repo}, {REPO}, and {Repo} all work the same way.