GitLab MCP Server

@owayo

Basic information

About GitLab MCP Server

No overview available yet

GitLab MCP Server config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "gitlab-mcp-server-owayo": {
      "command": "uv",
      "args": [
        "sync"
      ]
    }
  }
}

GitLab MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is GitLab-MCP-Server?

GitLab-MCP-Server is a Model Context Protocol (MCP) server that integrates with GitLab to fetch pipeline failure details, unresolved merge request review comments, and MR changes from a specific project. It provides this data to AI assistants (e.g., Claude) so they can help diagnose issues, address review feedback, and review code changes.

How to use GitLab-MCP-Server?

Install via uv (uv sync), obtain a GitLab API token with read_api scope, and set the environment variables GITLAB_URL, GITLAB_PROJECT_NAME, GITLAB_API_KEY, and GIT_REPO_PATH. Add the server configuration to Claude for Desktop (claude_desktop_config.json) or Cursor (.cursor/mcp.json) using the uv command and main.py script.

Key features of GitLab-MCP-Server

Fetches console output from failed pipeline jobs.
Retrieves unresolved, file‑linked MR review comments.
Obtains MR diff between base commit and local repository state.
Provides data directly to AI assistants via MCP tools.

Use cases of GitLab-MCP-Server

AI assistant analyzes pipeline failures and suggests fixes.
AI assistant reviews unresolved MR comments and helps address them.
AI assistant reviews MR changes against local working state for code review.
Integration with coding tools (Claude Desktop, Cursor) for automated assistance.