
October 5, 2026 · 5 min read
How to connect GitHits to CodeRabbit for dependency reviews
Give CodeRabbit access to dependency source, release changes, and package data through GitHits. Follow the setup and try a review.
A pull request can look correct in your repository and still use a library incorrectly. A retry might repeat a write, or an upgrade might change a default your application relies on. To review that change, the agent needs to inspect the library version your application uses.
CodeRabbit is an AI code reviewer. Connecting it to GitHits lets it look up public dependency source, release changes, and package data during a review. For example, it can read a library’s retry code and check whether your error handling matches it.
The connection uses Model Context Protocol (MCP), a standard that lets AI tools call external services. You create an access token in GitHits, add the connection in CodeRabbit, and make it available to reviews. The steps below walk through that setup.
Before you start
You need a GitHits account and admin access to your CodeRabbit organization.
Part A: Create a GitHits token
1. Open Account settings
In the GitHits dashboard, click your profile in the top-right corner, then click Account settings.

2. Create a personal token
Click Personal tokens and create a new token:
- Name:
coderabbit - Expires: Pick an expiry. It can’t be changed later.
Click Create token.

3. Copy the token
The token lets CodeRabbit access GitHits through your account. Copy it and store it somewhere safe. You can’t view it again after you close the dialog.

Part B: Connect GitHits MCP in CodeRabbit
4. Add a custom connection
In CodeRabbit, click Settings, then Connections, then Add connection. Under Custom, choose Custom.

5. Configure the MCP connection
Select the MCP tab and fill in the form:
| Field | Value |
|---|---|
| Access mode | Read-only |
| Server name | GitHits |
| Server URL | https://mcp.githits.com |
| Transport | Streamable HTTP |
| Authentication | API token |
| Auth header | Authorization |
| API token | Bearer YOUR_GITHITS_TOKEN |
In API token, type the word Bearer, a space, and then your token. Without the Bearer prefix and space, the connection fails.
Click Discover tools to check the connection, then click Save. Leave Add this to the Base Scope unchecked if your organization has no Base Scope yet. You will add GitHits to one in the next step.

6. Add GitHits to the Base Scope
The Base Scope makes GitHits available to reviews by default.
Go to Settings, then Scopes, and click Set up Base Scope. Under Connections, check GitHits in MCP servers. Leave Environment set to Standard CodeRabbit environment and click Save Base Scope.

Troubleshooting
- Add this to the Base Scope shows an error. No Base Scope exists yet. Save the connection without it, then follow step 6.
- Discover tools fails. Check that the token starts with
Bearerand a space. Use the eye icon to reveal the field. - It worked before and stopped. The token may have expired. Create a new one in GitHits and update the connection.
- GitHits is not used on a public repo. CodeRabbit’s default MCP setting,
auto, turns MCP off for public repositories. See the.coderabbit.yamlexample below.
Try it on a pull request
Open a pull request (PR) that uses or upgrades a dependency. CodeRabbit can call the connected tools during its review or when you ask a question in the PR comments. Check “Additional context used” in the review walkthrough to see which tools it called. The prompts below ask for specific checks.
Check how a library API behaves
@coderabbitai Use GitHits to check how pRetry in p-retry handles AbortError in the version this PR installs. Does our error handling match the source?
Review a dependency upgrade
@coderabbitai Use GitHits to review the upgrade from express 4.21.2 to 5.1.0. Summarize breaking changes from the changelog and any known vulnerabilities.
Vet a new dependency
@coderabbitai This PR adds drizzle-orm. Use GitHits to check its license, runtime dependencies, and known vulnerabilities.
Compare against how other projects do it
@coderabbitai Use GitHits to find how other open-source projects configure Hono middleware for auth, and tell me if our approach differs.
Ask for GitHits checks on every review
Path instructions in .coderabbit.yaml tell CodeRabbit what to check in matching files. This example applies to package.json, the file that lists a JavaScript project’s dependencies:
reviews:
path_instructions:
- path: "**/package.json"
instructions: |
When dependencies are added or upgraded, use GitHits to check the
changelog between versions, known vulnerabilities, and license.
knowledge_base:
mcp:
usage: enabled
usage: enabled turns on MCP for all repositories, including public ones.