
The Connections page, listing saved connections with their connector, authentication type, and assigned scopes
How Connections works
A connector is a supported service or connection method, such as Linear, Notion, Google Drive, or a custom MCP server. A connection is a configured instance of a connector, including its credentials and settings. Your organization can save multiple connections for the same connector. For example, you might save one Linear connection for Engineering and another for Product. Give each connection a recognizable name so administrators can select the right account when configuring scopes.
Two saved PagerDuty connections. The read-only (RO) connection is assigned to specific scopes
Find and understand connections
Use the search field to find a connection by its name, connector, or assigned scope. Use the available filters to narrow the table by the attributes shown in your organization, such as connector, authentication type, or product availability. The Connections table and detail view use these labels:Add a connection
Open Connections
Select Add connection
Choose a connector

The connector catalog, grouped by category such as Observability & incidents, Analytics & data, and Project & issue tracking
Select a connection method

Connection method selection for Datadog, showing the API and Application Keys tab with a setup guide for finding the required credentials
Name the connection
Authenticate
Review provider access
Choose initial scopes
Save the connection
Confirm the connection
Direct connections and MCP connections
A direct connection uses a guided integration provided by CodeRabbit. An MCP connection connects CodeRabbit to an MCP-compatible server. Both are saved connections that administrators can name, manage, and assign to supported scopes. The connection form displays the authentication fields required by the selected method. Depending on the connector, this might be an OAuth flow, an API key, server credentials, or other service-specific settings. Product availability can differ between connection methods. When a method supports only one product area, the interface displays Currently available in Review only or Currently available in Slack and Discord only. Check this message while choosing a method; being a direct or MCP connection does not by itself determine which products can use it. When an existing connection is available only in Review, the interface may offer an option to enable it for CodeRabbit Agent without entering the credentials again. Repeating this action reuses the existing Agent connection instead of creating a duplicate. For requirements that apply to MCP-compatible servers, see MCP servers.GitLab token-defined repository access
For a GitLab-connected SSO workspace, the selected GitLab token defines the access boundary for each Slack scope. CodeRabbit Agent discovers every visible, non-archived top-level group and the repositories in those groups and their subgroups. Projects in personal namespaces are excluded because discovery starts at the GitLab groups endpoint. GitLab groups and repositories appear as included, read-only context without checkboxes. This differs from GitHub, where administrators select individual repositories. A project visible to the GitLab token can enter CodeRabbit Agentâs repository context even when CodeRabbit Review is not installed for that project. During setup, choose whether to inherit the GitLab token used by CodeRabbit Review or define a separate GitLab token for CodeRabbit Agent. After a separate GitLab token is configured, you can keep it or replace it.Manage a saved connection
Open a saved connection to review its settings and the scopes that use it. Depending on the connector and your permissions, you can:- Edit its name or connection settings.
- Reconnect it when OAuth expires, provider authorization changes, or CodeRabbit asks you to authorize it again.
- Remove it from a scope to prevent use in that context without deleting the saved connection.
- Delete the connection when the organization no longer needs it.