# kopfrechner/gitlab-mr-mcp [Health: Active]

**Category:** 🔄 Version Control  
**Repository:** https://github.com/kopfrechner/gitlab-mr-mcp  
**GitHub Stars:** 94  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/kopfrechner-gitlab-mr-mcp

## Description
Interact seamlessly with issues and merge requests of your GitLab projects.

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What kopfrechner/gitlab-mr-mcp MCP server does

kopfrechner/gitlab-mr-mcp MCP server gives an AI agent access to selected GitLab project data and merge request actions. It can discover projects available to the configured token, list open merge requests in a project, and retrieve details for a particular merge request or issue.

For code review workflows, the server can return merge request diffs and comments, including discussion notes and comments attached to changed lines. Agents can also add a general merge request comment or post a comment against a specific line in a file from the diff. Two mutation tools update a merge request’s title and description.

## How it works

The project runs as a Node.js MCP process. An MCP client starts `index.js` with the server’s configured environment, and the server uses the supplied GitLab host and access token to perform GitLab operations. Project IDs are used when addressing project-specific merge requests and issues.

The `get_projects` tool can optionally narrow its results by minimum project access level or by a search term matching a project name or path. These filters are useful when the token can access many projects and the agent should work within a smaller set.

The available operations are exposed as separate MCP tools:

- `get_projects` and `list_open_merge_requests` discover accessible projects and active reviews.
- `get_merge_request_details`, `get_merge_request_comments`, and `get_merge_request_diff` provide review context.
- `get_issue_details` retrieves issue information.
- `add_merge_request_comment` and `add_merge_request_diff_comment` write review comments.
- `set_merge_request_title` and `set_merge_request_description` edit merge request metadata.

## Setup and configuration

To run kopfrechner/gitlab-mr-mcp MCP server manually, install Node.js, clone the repository, and run `npm install`. Configure the MCP client to launch `node` with the path to `index.js`. The required environment variables are `MR_MCP_GITLAB_TOKEN` and `MR_MCP_GITLAB_HOST`.

The token needs GitLab API access. The project documentation specifically calls out `api` and `read_api` scopes when troubleshooting authorization failures. The token’s user must also have access to the target projects, and the project IDs supplied to tools must be valid.

Smithery provides an installation path for Claude Desktop, using configuration fields for the GitLab token and host. For local inspection, the repository documents running the server through the MCP Inspector with `npm start`.

Optional filtering uses `MR_MCP_MIN_ACCESS_LEVEL` and `MR_MCP_PROJECT_SEARCH_TERM`. The first limits projects by access level; the second filters by a matching project path or name.

## Limitations and notes

It does not describe tools for creating issues, merging merge requests, changing labels or assignees, or modifying repository files directly.

Permission errors generally indicate an insufficient token scope, missing project access, or an incorrect project ID. Review those three areas before treating a failed request as a server defect. The repository is licensed under MIT.

_Full upstream README: https://allmcps.com/mcp/kopfrechner-gitlab-mr-mcp/readme_