This GitLab MCP (Model Context Protocol) server allows AI assistants like Claude to interact with GitLab's merge requests for code review. It provides a seamless integration that enables AI assistants to analyze code changes, add comments, and manage approvals directly through the GitLab API.
git clone https://github.com/mehmetakinn/gitlab-mcp-code-review.git
cd gitlab-mcp-code-review
python -m venv .venv
source .venv/bin/activate # On Windows: .venv\Scripts\activate
pip install -r requirements.txt
.env file with your GitLab configuration:# Required
GITLAB_TOKEN=your_personal_access_token_here
# Optional settings
GITLAB_HOST=gitlab.com
GITLAB_API_VERSION=v4
LOG_LEVEL=INFO
You can customize the following environment variables in your .env file:
| Variable | Required | Default | Description |
|---|---|---|---|
| GITLAB_TOKEN | Yes | - | Your GitLab personal access token |
| GITLAB_HOST | No | gitlab.com | GitLab instance hostname |
| GITLAB_API_VERSION | No | v4 | GitLab API version to use |
| LOG_LEVEL | No | INFO | Logging level (DEBUG, INFO, WARNING, ERROR, CRITICAL) |
| DEBUG | No | false | Enable debug mode |
| REQUEST_TIMEOUT | No | 30 | API request timeout in seconds |
| MAX_RETRIES | No | 3 | Maximum retry attempts for failed requests |
Add this configuration to your ~/.cursor/mcp.json file:
{
"mcpServers": {
"gitlab-mcp-code-review": {
"command": "/path/to/your/gitlab-mcp-code-review/.venv/bin/python",
"args": [
"/path/to/your/gitlab-mcp-code-review/server.py",
"--transport",
"stdio"
],
"cwd": "/path/to/your/gitlab-mcp-code-review",
"env": {
"PYTHONPATH": "/path/to/your/gitlab-mcp-code-review",
"VIRTUAL_ENV": "/path/to/your/gitlab-mcp-code-review/.venv",
"PATH": "/path/to/your/gitlab-mcp-code-review/.venv/bin:/usr/local/bin:/usr/bin:/bin"
},
"stdio": true
}
}
}
Remember to replace /path/to/your/gitlab-mcp-code-review with the actual path to your cloned repository.
The MCP server offers these tools for GitLab interaction:
| Tool | Description |
|---|---|
fetch_merge_request |
Get complete information about a merge request |
fetch_merge_request_diff |
Get diffs for a specific merge request |
fetch_commit_diff |
Get diff information for a specific commit |
compare_versions |
Compare different branches, tags, or commits |
add_merge_request_comment |
Add a comment to a merge request |
approve_merge_request |
Approve a merge request |
unapprove_merge_request |
Unapprove a merge request |
get_project_merge_requests |
Get a list of merge requests for a project |
# Get details of merge request #5 in project with ID 123
mr = fetch_merge_request("123", "5")
# Get diff for a specific file in a merge request
file_diff = fetch_merge_request_diff("123", "5", "path/to/file.js")
# Compare develop branch with master branch
diff = compare_versions("123", "develop", "master")
# Add a comment to a merge request
comment = add_merge_request_comment("123", "5", "This code looks good!")
# Approve a merge request and set required approvals to 2
approval = approve_merge_request("123", "5", approvals_required=2)
If you encounter issues:
.env file settingscurl -H "Private-Token: your-token" https://gitlab.com/api/v4/projectsTo add this MCP server to Claude Code, run this command in your terminal:
claude mcp add-json "gitlab-mcp-code-review" '{"command":"/path/to/your/gitlab-mcp-code-review/.venv/bin/python","args":["/path/to/your/gitlab-mcp-code-review/server.py","--transport","stdio"],"cwd":"/path/to/your/gitlab-mcp-code-review","env":{"PYTHONPATH":"/path/to/your/gitlab-mcp-code-review","VIRTUAL_ENV":"/path/to/your/gitlab-mcp-code-review/.venv","PATH":"/path/to/your/gitlab-mcp-code-review/.venv/bin:/usr/local/bin:/usr/bin:/bin"},"stdio":true}'See the official Claude Code MCP documentation for more details.
There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json file so that it is available in all of your projects.
If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json file.
To add a global MCP server go to Cursor Settings > Tools & Integrations and click "New MCP Server".
When you click that button the ~/.cursor/mcp.json file will be opened and you can add your server like this:
{
"mcpServers": {
"gitlab-mcp-code-review": {
"command": "/path/to/your/gitlab-mcp-code-review/.venv/bin/python",
"args": [
"/path/to/your/gitlab-mcp-code-review/server.py",
"--transport",
"stdio"
],
"cwd": "/path/to/your/gitlab-mcp-code-review",
"env": {
"PYTHONPATH": "/path/to/your/gitlab-mcp-code-review",
"VIRTUAL_ENV": "/path/to/your/gitlab-mcp-code-review/.venv",
"PATH": "/path/to/your/gitlab-mcp-code-review/.venv/bin:/usr/local/bin:/usr/bin:/bin"
},
"stdio": true
}
}
}To add an MCP server to a project you can create a new .cursor/mcp.json file or add it to the existing one. This will look exactly the same as the global MCP server example above.
Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.
The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.
You can also explicitly ask the agent to use the tool by mentioning the tool name and describing what the function does.
To add this MCP server to Claude Desktop:
1. Find your configuration file:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.json~/.config/Claude/claude_desktop_config.json2. Add this to your configuration file:
{
"mcpServers": {
"gitlab-mcp-code-review": {
"command": "/path/to/your/gitlab-mcp-code-review/.venv/bin/python",
"args": [
"/path/to/your/gitlab-mcp-code-review/server.py",
"--transport",
"stdio"
],
"cwd": "/path/to/your/gitlab-mcp-code-review",
"env": {
"PYTHONPATH": "/path/to/your/gitlab-mcp-code-review",
"VIRTUAL_ENV": "/path/to/your/gitlab-mcp-code-review/.venv",
"PATH": "/path/to/your/gitlab-mcp-code-review/.venv/bin:/usr/local/bin:/usr/bin:/bin"
},
"stdio": true
}
}
}3. Restart Claude Desktop for the changes to take effect