MCP server for GitLab Code Review
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"iflow-mcp-mehmetakinn-gitlab-mcp-code-review","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# GitLab MCP for Code Review [](https://www.python.org/downloads/) [](https://opensource.org/licenses/MIT) > This project is forked from [cayirtepeomer/gerrit-code-review-mcp](https://github.com/cayirtepeomer/gerrit-code-review-mcp) and adapted for GitLab integration. An MCP (Model Context Protocol) server for integrating AI assistants like Claude with GitLab's merge requests. This allows AI assistants to review code changes directly through the GitLab API. ## Features - **Complete Merge Request Analysis**: Fetch full details about merge requests including diffs, commits, and comments - **File-Specific Diffs**: Analyze changes to specific files within merge requests - **Version Comparison**: Compare different branches, tags, or commits - **Review Management**: Add comments, approve, or unapprove merge requests - **Project Overview**: Get lists of all merge requests in a project ## Installation ### Prerequisites - Python 3.10+ - GitLab personal access token with API scope (read_api, api) - [Cursor IDE](https://cursor.sh/) or [Claude Desktop App](https://claude.ai/desktop) for MCP integration ### Quick Start 1. Clone this repository: ```bash git clone https://github.com/mehmetakinn/gitlab-mcp-code-review.git cd gitlab-mcp-code-review ``` 2. Create and activate a virtual environment: ```bash python -m venv .venv source .venv/bin/activate # On Windows: .venv\Scripts\activate ``` 3. Install dependencies: ```bash pip install -r requirements.txt ``` 4. Create a `.env` file with your GitLab configuration (see `.env.example` for all options): ``` # Required GITLAB_TOKEN=your_personal_access_token_here # Optional settings GITLAB_HOST=gitlab.com GITLAB_API_VERSION=v4 LOG_LEVEL=INFO ``` ## Configuration Options The following environment variables can be configured in your `.env` file: | Variable | Required | Default | Des…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.