add_merge_request_diff_comment is what separates this from a read-only GitLab connector: feedback lands on the line it is about, where the author will see it. Title and description writes mean the same session can tidy up the merge request it just reviewed.
An MCP server for GitLab merge requests and issues. It lists what is open, reads a merge request with its diff and discussion, comments generally or on a specific line, and edits the title and description.
- The projects your token can reach, and the open merge requests in one of them (get_projects, list_open_merge_requests)
- A merge request's details, its diff, and its comments including discussion notes and diff notes (get_merge_request_details, get_merge_request_diff, get_merge_request_comments)
- A general comment, or one attached to a specific line of a specific file in the diff (add_merge_request_comment, add_merge_request_diff_comment)
- The merge request's title and description set from the client (set_merge_request_title, set_merge_request_description)
- The details of a linked issue (get_issue_details)
Node, a GitLab access token with API access in MR_MCP_GITLAB_TOKEN, and your GitLab host in MR_MCP_GITLAB_HOST.
One command plus a key — npx -y @smithery/cli@latest install @kopfrechner/gitlab-mr-mcp --client claude --config '"{\"gitlabMrMcpToken\":\"YOUR_GITLAB_TOKEN\", \"gitlabMrMcpHost\": \"YOUR_GITLAB_HOST\"}"', then supply credentials