Gitlab Accept MR Tool
Accept and merge merge requests.
LABSCO SUMMARY
This is a review-queue tool, not a repository browser.
The named tools cover merge requests, project search and user search; files, branches, pipelines and issues are reachable only through Gitlab Raw API Tool, which takes an endpoint, a method, params and a body and returns whatever GitLab answers. The fields parameter runs through the lookup and MR tools alike, which matters more than it sounds: a GitLab project payload is large, and naming the fields keeps it out of the context window.
What it is
A GitLab REST client built around merge requests, with project and user lookup beside them and a raw API tool for endpoints the named tools do not cover.
What you get
- The merge-request lifecycle: Gitlab Create MR Tool opens one with source and target branch, title, description, labels, assignee and reviewers; Gitlab Update MR Tool changes those afterwards; Gitlab Create MR Comment Tool adds a comment; Gitlab Accept MR Tool merges it with custom merge options.
- Gitlab Get User Tasks Tool returns the current user's to-do items, filtered by task type.
- Lookup that stays small: Gitlab Search Project Details Tool finds a project by name and Gitlab Search User Projects Tool finds a user and their active projects — both take a fields filter so only the fields you name come back.
- Gitlab Raw API Tool calls any GitLab REST endpoint with your own method, params and body, for debugging and for the calls the named tools do not make.
Requirements
A GitLab instance and an access token for an account that can reach the projects and merge requests you name. The token goes in GITLAB_TOKEN and the instance's API base URL in GITLAB_API_URL.
Setup effort
One command plus a key — npx -y @zephyr-mcp/gitlab, then supply credentials
USE CASES
01
Opening the merge request without switching to the browser
Resolve the project by name, then open the MR with its branches, labels, assignee and reviewers already set.
02
Clearing what is sitting in your review queue
Pull the to-do list, leave the comment on the one that needs a change, and merge the one that is ready with the merge options you want.
03
Getting a stalled merge request back onto someone's desk
Find who is actually active on the project, then reassign the MR and update its description in the same pass.
04
Reaching a GitLab endpoint the named tools do not cover
Call the REST API directly when the job needs pipelines, files or anything else outside the merge-request tools.
8 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
Gitlab Create MR Comment Tool
Add comments to merge requests.
Gitlab Create MR Tool
Create a new merge request with assignee and reviewers.
Gitlab Get User Tasks Tool
Get the current user's pending tasks.
Gitlab Raw API Tool
Call any GitLab API with custom parameters.
Gitlab Search Project Details Tool
Search projects and their details.
Gitlab Search User Projects Tool
Search users and their active projects by username.
Gitlab Update MR Tool
Update a merge request's assignee, reviewers, title, description and labels.
BEFORE YOU INSTALL
What to know first
Tools you get
8 tools when we connected. Call tools by their spaced names, such as Gitlab Get User Tasks Tool, not class names like GitlabAcceptMRTool. Writes include creating, commenting on, updating and merging merge requests.
Requires
- npx on PATH
- GITLAB_TOKEN (a GitLab access token)
- GITLAB_API_URL (your GitLab instance's base URL)
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 8 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @zephyr-mcp/gitlabMCP Clients
Claude Desktop — stdio
CLAUDE DESKTOP — STDIO · JSON
{
"mcpServers": {
"@zephyr-mcp/gitlab": {
"command": "npx",
"args": [
"-y",
"@zephyr-mcp/gitlab"
],
"env": {
"GITLAB_API_URL": "<YOUR_GITLAB_API_URL>",
"GITLAB_TOKEN": "<YOUR_GITLAB_TOKEN>"
}
}
}
}
