Skip to main content
| 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.
The number of MCP server connections you can configure depends on your plan. See Plans and pricing — MCP servers for current limits.

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.

Suggested MCP servers

The Integrations page includes nine suggested MCP servers: Notion, Context7, Linear, GitHub Copilot, Sentry, Asana, Monday.com, ClickUp and DeepWiki. An MCP integration supplies the server name, hosted endpoint, and authentication method. To connect another MCP server, choose New MCP Server and enter its connection details manually.

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

Open integrations

2

Choose an MCP server

Select a suggested server and click Add, or choose New MCP Server for a custom setup.Add Usage guidance when CodeRabbit needs help finding the right information on the server. See User guidance for details.
3

Choose a connection mode (optional)

This choice appears only when your workspace has an active CodeRabbit Reverse Tunnel route for MCP.Choose Direct when CodeRabbit can reach the server at a public HTTPS URL, or Reverse tunnel when the server runs on a private network. See Connect through a reverse tunnel.
4

Complete authentication

Enter the required API token, complete OAuth, or continue without authentication according to the server’s configuration.
5

Configure tools

Discover the tools exposed by the server and choose which tools CodeRabbit may use, then save the connection.

Connect through a reverse tunnel

CodeRabbit can reach an MCP server that has no public address and no inbound firewall rule, using the CodeRabbit Reverse Tunnel. A connector running inside your network dials out to CodeRabbit, and reviews call your internal MCP tools over that outbound connection. Set Connection mode when you add or edit an MCP server: You do not pick a route. Enter the server URL and CodeRabbit matches it against the active routes in your workspace. If no route covers that URL, saving fails with No active workspace connector route matches this MCP server. Requirements and limits for reverse tunnel mode:
  • The server URL must use HTTPS, and its origin must fall within a route your workspace already has.
  • Streamable HTTP and SSE transports both work. WebSocket transport is not supported over the tunnel.
  • The route must be active. CodeRabbit provisions routes; they are not self-service.
The Connection mode control is hidden until your workspace has at least one active MCP route. To set one up, see Reverse Tunnel connector configuration.

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 Usage guidance field contains instructions that CodeRabbit reads before using your MCP server. Use it to describe 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:

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

Placeholders are case-insensitive. {repo}, {REPO}, and {Repo} all work the same way.

What’s next

Plans and pricing

Check how many MCP server connections your plan includes.

Reverse Tunnel connector configuration

Configure a connector so CodeRabbit can reach an MCP server on your private network.