"How to review merge requests in GitLab" matching MCP servers:

An MCP server that enables AI agents to perform automated code reviews on GitLab merge requests, including fetching details, reading diffs, posting inline comments, managing labels, and approving or unapproving MRs.

MCP server that acts as a thin proxy over GitLab REST API v4, enabling users to list merge requests, view diffs, and leave inline comments without leaving their MCP client.

Guards PR merge decisions by validating CI, approvals, conflicts, and branch freshness.

An MCP server that enables Claude agents to interactively merge security audit findings by grouping duplicates, selecting canonicals, preserving authorship, and generating edit instructions, all against a GitHub issues repository.

Provides lightweight Git merge analysis with quick overviews of changes, file lists, and branch status without complex conflict checks.

Connects AI assistants to GitLab, allowing users to manage merge requests, view reviews, and interact with discussions through natural language queries.

Enables natural language interactions with GitLab via Claude Code, supporting MR reviews, issue management, pipeline monitoring, and branch comparisons.

Enables secure interaction with GitLab instances through MCP, supporting projects, merge requests, issues, pipelines, and search.

PDF Merge AI - MCP server providing AI-powered tools and automation by MEOK AI Labs

Enables an assistant to work inside gitlab.com projects as the signed-in user: issues, merge requests, code reviews, repositories, CI pipelines and job logs, plus optional gated toolsets for wiki, snippets, releases, planning, deployments and activity. It authenticates through a user-supplied OAuth application with the token kept in the OS keyring, and registers only the tools that are switched on.

Enables Codex to rank available tools and skills, rerank code and documentation search results, and triage saved output artifacts using Jev-based relevance scoring while leaving final decisions to Codex.

Call OpenAI Codex from Claude Code for independent second opinions, structured code review, and delegated coding tasks through a FastMCP plugin that drives the codex CLI safely.

Enables AI agents to browse, read, search, blame, and diff files from any branch, tag, or commit in a self-managed GitLab instance without checking anything out or modifying the working tree. Content is served read-only from locally cached git mirrors or your own clones, so no GitLab REST API access is needed.

Enables AI agents and MCP clients to drive real Chrome, Edge, Brave, and Firefox browsers through native automation protocols. It exposes tools for navigation, page snapshots, form filling, clicks, screenshots, console/network inspection, and tab management.

Wraps GitLab Duo CLI as an MCP tool for code review, enabling agents to get structured Duo reviews via duo_review.

Wraps Claude Code's code-review skill so any MCP client can run reviews over a PR, branch, working directory, or last commit, with five parallel reviewer subagents, low-to-max effort levels, and optional fix mode that edits files in place. Also supports follow-up questions on a previous review session and a free environment self-check.

Enables MCP clients to open websites, capture screenshots at multiple breakpoints, and run automated design audits for issues like overflow, small tap targets, low contrast, missing alt text, tiny text, and clipped content.

Enables multiple AI coding tools to collaboratively review code by sharing a SQLite-backed board, allowing them to create threads, post and reply to comments, list threads, and update statuses through MCP.

An MCP relay that adds a use_jev tool to every connected server, letting the Jev model autonomously select and execute tool calls while the calling model supplies any required text values. It enables agents to delegate multi-step tool use across all configured MCP servers through a single unified interface.

Enables an MCP-capable assistant to review GitLab merge requests, GitHub pull requests, and pre-push local branches against ticket requirements, domain rubrics, compiler/lint pre-passes, blast-radius analysis, and SonarQube findings, and to draft inline comments or follow-up tasks in the user's chosen language. Nothing reaches a remote host until a human approves the exact content in an interactive terminal.