// MCP TOOL REFERENCE

GITLAB MERGE REQUEST INTEGRATION TOOLS

10 tools from the GitLab Merge Request Integration MCP Server, categorised by risk level.

View the GitLab Merge Request Integration policy →

READ TOOLS

get_issue_details Get details of an issue within a certain project get_merge_request_comments Get general and file diff comments of a certain merge request get_merge_request_details Get details about a specific merge request of a project like title, source-branch, target-branch, web_url, ... get_merge_request_diff Get the file diffs of a certain merge request get_projects Get a list of projects with id, name, description, web_url and other useful information. list_open_merge_requests Lists all open merge requests in the project

WRITE TOOLS

add_merge_request_comment Add a general comment to a merge request add_merge_request_diff_comment Add a comment of a merge request at a specific line in a file diff set_merge_request_description Set the description of a merge request set_merge_request_title Set the title of a merge request

// FAQ

How many tools does the GitLab Merge Request Integration MCP server have? +

The GitLab Merge Request Integration MCP server exposes 10 tools across 2 categories: Read, Write.

How do I enforce policies on GitLab Merge Request Integration tools? +

Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the GitLab Merge Request Integration server.

What risk categories do GitLab Merge Request Integration tools fall into? +

GitLab Merge Request Integration tools are categorised as Read (6), Write (4). Each category has a recommended default policy.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

GET STARTED →