List or search merge requests in a GitLab project with filters for state, labels, authors, assignees, and branches to triage and review code changes.
MIT
686,104 tools. Updated 2026-10-21 16:46
"How to review merge requests in GitLab" matching MCP tools:
- Retrieve GitLab merge requests visible to your token to review pending changes and monitor merge activity.MIT
- Retrieve pull requests where you are the author, assignee, or optionally a requested reviewer. Supports GitHub, GitLab, Bitbucket, and Azure DevOps.MIT
- List the merge requests of a spec with their status (open, inReview, approved, merged, rejected, closed) and how many of the assigned reviewers have approved. Requires project context.MIT
- Prioritizes open pull requests by status like ready to merge, conflicts, or awaiting review. Helps you decide what to work on next.MIT
- Post inline review comments to merge/pull requests, retrying transient failures and respecting rate limits.MIT
Matching MCP Servers
- AlicenseAqualityCmaintenanceEnables interaction with GitLab projects, merge requests, issues, and code reviews through Claude AI, providing tools for code review and project management.141MIT
- AlicenseBqualityCmaintenanceEnables code review operations on GitHub and GitLab, including fetching pull/merge requests, viewing diffs, adding comments, analyzing code quality, and creating merge requests directly from your MCP client.159 npm4MIT
Matching MCP Connectors
GitLab MCP — wraps the GitLab REST API v4 (BYO API key)
GitLab Public MCP — wraps the GitLab REST API v4 (public endpoints, no auth)
- List files changed in a GitLab merge request with stats and reviewability flags. Sort reviewable files first to prioritize high-value code review.MIT
- Search GitLab merge requests by username, author, assignee, or within a project. Filter by state, sort order, and paginate results for comprehensive MR discovery.MIT
- List merge requests from a GitLab project with optional state filter. Use to get an overview of open, merged, or all merge requests.MIT
- Merges a GitLab merge request by IID after verifying merge_status, handling conflicts or pipeline issues.MITDestructive
- Add a code-review comment to a specific line in a GitLab merge request diff. Provide the diff refs and target line to start a discussion on code changes.MIT
- List merge requests for a GitFlic project, returning ID, title, status, and source/target branches with pagination support.Apache 2.0
- Retrieve a merge request's review status in one consolidated snapshot, covering discussions, resolution state, and file changes. Simplifies orientation before examining the diff.MIT
- Retrieve and filter merge requests from a GitLab project to review active changes, track progress, or find specific submissions using state-based filtering and pagination.Apache 2.0
- Retrieve detailed merge request information including status, pipelines, approvals, and conflicts to review and assess merge readiness in GitLab projects.Apache 2.0
- Add comments to GitLab merge requests for code review feedback and discussions. Supports Markdown formatting, user mentions, and slash commands.Apache 2.0
- Approve merge requests after code review completion to enable merging. Use when changes are approved and ready for integration.Apache 2.0
- Retrieve merge commits performed by a specific user to track integrated contributions and analyze merge activity for release management.Apache 2.0
- Retrieve issue body, notes, related and closing merge requests, and linked issues in one call. Simplifies investigating an issue by avoiding multiple separate API calls.MIT
- Inspect merge request approval rules and approvers to determine merge readiness. Read-only check before merging.MIT
- Fetch flat merge request notes from GitLab by project ID and merge request IID. Get read-only note records with pagination, sorting, and JMESPath filtering options.MIT