GitLab MRSAFE
Interact seamlessly with GitLab repositories to manage merge requests and issues. Fetch details, add comments, and streamline your code review process with ease.
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
[](https://mseep.ai/app/kopfrechner-gitlab-mr-mcp)
[](https://github.com/kopfrechner/gitlab-mr-mcp/stargazers) [](LICENSE) [](https://smithery.ai/server/@kopfrechner/gitlab-mr-mcp)
A Model Context Protocol (MCP) server for interacting with GitLab merge requests and issues.
📌 Overview
This project implements a server using the Model Context Protocol (MCP) that allows AI agents to interact with GitLab repositories. It provides tools for:
- Listing available GitLab projects
- Fetching merge request details and comments
- Getting merge request diffs
- Adding comments to merge requests
- Adding line-specific comments to code in merge request diffs
- Fetching issue details
- Setting merge request title and description
📦 Installation
⚡ Using Smithery
To install GitLab MR MCP for Claude Desktop automatically via Smithery:
npx -y @smithery/cli@latest install @kopfrechner/gitlab-mr-mcp --client claude --config '"{\"gitlabMrMcpToken\":\"YOUR_GITLAB_TOKEN\", \"gitlabMrMcpHost\": \"YOUR_GITLAB_HOST\"}"'🛠️ Manual Installation
🔧 Prerequisites
- Node.js
- GitLab access token with API access
- GitLab project ID(s)
📖 Setup
- Clone this repository
- Install dependencies:
npm install
- Add the following to your MCP client configuration:
{
"mcpServers": {
"gitlab-mr-mcp": {
"command": "node",
"args": ["/path/to/gitlab-mr-mcp/index.js"],
"env": {
"MR_MCP_GITLAB_TOKEN": "your_gitlab_token",
"MR_MCP_GITLAB_HOST": "your_gitlab_host"
}
}
}
}🛠️ Available Tools
get_projects
Gets a list of GitLab projects acces
0e1d267b2d59OBSERVED · 2026-10-07Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.
claude mcp add gitlab-mr-mcp --env MR_MCP_GITLAB_TOKEN=${MR_MCP_GITLAB_TOKEN} -- npx -y [email protected]{
"mcpServers": {
"gitlab-mr-mcp": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"MR_MCP_GITLAB_TOKEN": "${MR_MCP_GITLAB_TOKEN}"
}
}
}
}Exposed tools (10)
2 read · 8 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
add_merge_request_comment | write | Add a general comment to a merge request |
add_merge_request_diff_comment | write | Add a comment of a merge request at a specific line in a file diff |
get_issue_details | read | Get details of an issue within a certain project |
get_merge_request_comments | write | Get general and file diff comments of a certain merge request |
get_merge_request_details | write | Get details about a specific merge request of a project like title, source-branch, target-branch, web_url, ... |
get_merge_request_diff | write | Get the file diffs of a certain merge request |
get_projects | read | Get a list of projects with id, name, description, web_url and other useful information. |
list_open_merge_requests | write | Lists all open merge requests in the project |
set_merge_request_description | write | Set the description of a merge request |
set_merge_request_title | write | Set the title of a merge request |
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (1)
@gitbeaker/rest, @modelcontextprotocol/sdk, lodash, zod, jest
Gates applied: no_behavioural_pass.
0e1d267b2d59full audit observations/trust-audit/mcp-server/kopfrechner__gitlab-mr.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-07 | 0e1d267b2d59 | SAFE | B | 89 | first audit |
Questions
What is the GitLab MR MCP server?
Interact seamlessly with GitLab repositories to manage merge requests and issues. Fetch details, add comments, and streamline your code review process with ease.
What tools does GitLab MR expose?
10 in total: 2 read-only, 8 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is GitLab MR safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does GitLab MR need?
It reads MR_MCP_GITLAB_TOKEN from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How does GitLab MR run?
It speaks stdio, so it runs as a local process your client starts. It is published on npm as gitlab-mr-mcp at 0.1.0.
How current is this page?
The grade is for one exact copy of the source (0e1d267b2d59), read on 2026-10-07. The repository is watched and re-audited when it changes.