mcp-gitlab

GitLab MCP Server

A Model Context Protocol (MCP) server that enables you to interact with your GitLab account. Get diffs, analyze merge requests, review code, cherry-pick changes, and more.

Features

This MCP server provides comprehensive tools for interacting with GitLab repositories, including:

Core Repository Features

• Listing projects and retrieving details
• Managing branches and repositories
• Working with merge requests and diffs
• Adding comments and internal notes to merge requests
• Updating merge request attributes
• Listing and working with issues
• Getting and comparing repository file contents

Project Settings & Integrations

• Managing project integrations and services
• Configuring and controlling Slack integration
• Setting up, updating, and testing webhooks

CI/CD Management

• Working with pipeline trigger tokens
• Managing CI/CD variables
• Triggering and controlling pipelines

User & Group Administration

• Listing and managing users
• Working with groups and group memberships
• Managing project members and access levels

Installation

Option 1: Using Pre-built Docker Image (Recommended)

The easiest way to run the GitLab MCP Server is using the pre-built Docker image:

The server will be available at http://localhost:3001/mcp

Option 2: Using Docker Compose

Create a docker-compose.yml file:

Then run:

Option 3: Building from Source

If you want to build from source or contribute to the project:

Prerequisites

• Node.js (v16 or higher)
• npm
• A GitLab account with an API token

Setup

1. Clone the repository:

2. Install dependencies:

3. Build the server:

4. Install git hooks (optional, but recommended for contributors):

This installs a pre-commit hook that automatically regenerates TOOLS.md when src/utils/tools-data.ts changes.

5. Deploy the server:

The server will be available at http://localhost:3001/mcp

Configuration

This server implements Streamable HTTP as the primary MCP transport, which is now natively supported by Claude Code.

For Claude Code/Desktop (Recommended)

The easiest way to add the GitLab MCP server is using the Claude CLI:

Manual Configuration (Alternative)

Alternatively, you can manually add the following to your MCP settings file (~/.claude.json):

Configuration Details

• X-GitLab-Token: Your GitLab API token (required)
• X-GitLab-URL: Your GitLab instance URL (optional, defaults to https://gitlab.com)

Important Notes:

• The server automatically appends /api/v4 to the GitLab URL if not present
• Only GitLab API v4 is supported
• You can generate a token in your GitLab account under Settings > Access Tokens

Example GitLab URLs:

Updating to Latest Version

To update to the latest version when using the pre-built Docker image:

Or if using Docker Compose:

Available Tools

For a complete list of available tools and their parameters, see TOOLS.md.

Example Usage

Here are examples of how to use these tools with AI assistants that support MCP:

List your projects

Get information about a specific merge request

Add a comment to a merge request

Add an internal note to a merge request

Update a merge request title and description

Compare branches

Practical Workflows

Reviewing a Merge Request

Project Exploration

Available Resources

gitlab://projects

List of GitLab projects accessible with your API token.

Integration with AI Assistants

The GitLab MCP Server integrates with AI assistants that support the Model Context Protocol (MCP).

Capabilities

When connected to an AI assistant, this server enables the assistant to:

1. View and analyze code: The assistant can fetch file contents, view branch differences, and examine merge request changes for better code understanding.
2. Provide code reviews: The assistant can analyze merge requests and provide feedback through comments or internal notes.
3. Manage project workflows: The assistant can update merge request attributes, add comments, and help with repository management tasks.
4. Explore project structure: The assistant can browse projects, branches, and files to understand the codebase structure.
5. Configure CI/CD and integrations: The assistant can help set up webhooks, manage CI/CD variables, and configure project integrations.

Getting the Most from AI Assistant Integration

• Be specific when asking about projects, merge requests, or files
• Provide project IDs or paths when possible
• Use the assistant for code review by asking it to analyze specific merge requests
• Have the assistant help with repository configuration and management tasks
• Use internal notes for team-only feedback on merge requests

License

MIT