GitLab MCP server
Commit Nov 6, 2026Allows an AI client to interact with GitLab projects, issues, epics, and CI/CD pipelines directly.
Also known as sgaunet/gitlab-mcp
- Stars
- 4
- Tools
- 16
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Nov 6, 2026
- License
- MIT
What is GitLab MCP?
GitLab allows an AI client to interact with GitLab projects, issues, epics, and CI/CD pipelines directly. It exposes 16 tools, such as list_issues, create_issues, update_issues.
Summary generated from the project's README
About GitLab MCP server
Managing GitLab repositories and development workflows directly from Claude Code is what this MCP server enables. It provides a bridge for developers to interact with their GitLab instances using natural language, allowing for the management of issues, epics, and project metadata. Users can perform complex tasks like discovering all projects within a group and its subgroups or updating project descriptions and topics without leaving their terminal environment.
This tool connects to GitLab via a personal access token with api, read_api, and write_api scopes. It supports both GitLab.com and self-hosted instances through a configurable URI. The server communicates with Claude Code via stdio and can be installed using Homebrew or Docker. To optimize performance and token usage, users can disable specific tool categories such as pipelines, epics, or labels using command line flags during registration.
Written from the project's README. Every use case is checked against a quote from it.
GitLab MCP tools 16
Detected from the READMElist_issuescreate_issuesupdate_issuesadd_issue_notelist_labelslist_group_projectsget_project_descriptionupdate_project_descriptionget_project_topicsupdate_project_topicslist_epicscreate_epic
Show all 16 toolsShow fewer tools
get_latest_pipelinelist_pipeline_jobsget_job_logdownload_job_trace
Configuration
GITLAB_TOKENGITLAB_URI
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablesgaunet/gitlab-mcp is public and reachablegithub.com/sgaunet/gitlab-mcp ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-06github.com/sgaunet/gitlab-mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model16 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubGitLab MCP Server
A Model Context Protocol (MCP) server that provides GitLab integration tools for Claude Code. Interact with GitLab projects, issues, epics, and CI/CD pipelines directly from Claude.
Features
- Issue Management: List, create, update issues, and add comments
- Label Management: List and manage project labels with filtering
- Project Management: View and update project descriptions and topics
- Project Discovery: List all projects of a group recursively, including every subgroup
- Epic Management: List and create epics (Premium/Ultimate tier)
- CI/CD Integration: Monitor pipelines, view job logs, and download traces
- Direct Project Access: Use project paths (namespace/project-name) without ID resolution
- MCP Architecture: Seamless integration with Claude Code via stdio communication
Quick Start
Prerequisites
- GitLab personal access token with
api,read_api, andwrite_apiscopes - Claude Code CLI installed
- Docker (optional, for containerized deployment)
Installation
# Install via Homebrew (Recommended for macOS/Linux)
brew tap sgaunet/homebrew-tools
brew install sgaunet/tools/gitlab-mcp
Configuration
# Set your GitLab token
export GITLAB_TOKEN=your_personal_access_token
# Optional: For self-hosted GitLab
export GITLAB_URI=https://your.gitlab.instance
Add to Claude Code
Register the server once for all your projects (-s user):
claude mcp add gitlab-mcp -s user -- gitlab-mcp
This assumes gitlab-mcp is in your PATH (the case after a Homebrew install). If Claude Code
cannot find the binary, pass the absolute path instead:
# Apple Silicon Mac
claude mcp add gitlab-mcp -s user -- /opt/homebrew/bin/gitlab-mcp
# Intel Mac / Linux
claude mcp add gitlab-mcp -s user -- /usr/local/bin/gitlab-mcp
Pass the token explicitly with -e if it isn't exported in the environment Claude Code inherits:
claude mcp add gitlab-mcp -s user \
-e GITLAB_TOKEN=your_personal_access_token \
-e GITLAB_URI=https://your.gitlab.instance \
-- gitlab-mcp
Verify the server is connected:
claude mcp list
Other scopes: -s local (current project only, default) or -s project (shared via the project's
.mcp.json). See the setup guide for Docker-based
registration and manual mcp.json configuration.
CLI Flags (Optional)
Optimize token usage by disabling tool categories you don't need:
# Example: CI/CD debugging only
gitlab-mcp --no-issues --no-labels --no-project-metadata --no-epics
# Example: Issue management only
gitlab-mcp --no-project-metadata --no-epics --no-pipelines
Append the flags after the -- separator when registering the server:
claude mcp add gitlab-mcp -s user -- gitlab-mcp --no-epics --no-pipelines
Available flags: --no-issues, --no-labels, --no-project-metadata, --no-epics, --no-pipelines, --no-merge-requests, --no-projects
First Usage
List all open issues for project myorg/myproject
Create an issue with title "Bug fix needed" for project myorg/myproject
Get the latest pipeline for myorg/myproject
List all projects of the myorg group
Documentation
- Setup Guide - Installation, configuration, and Claude Code integration
- Docker Deployment - Container-based deployment and Docker Compose
- Tool Reference - Complete documentation for all available tools
- Development Guide - Contributing, testing, and development workflow
- Troubleshooting - Common issues and solutions
- Contributing - How to contribute to the project
Available Tools
| Tool | Description |
|---|---|
list_issues |
List project and group issues with filtering |
create_issues |
Create new issues with labels and assignees |
update_issues |
Update issue title, description, state, labels |
add_issue_note |
Add comments to issues |
list_labels |
List project labels with optional filtering |
list_group_projects |
List all projects of a group, subgroups included |
get_project_description |
Get project description |
update_project_description |
Update project description |
get_project_topics |
Get project topics/tags |
update_project_topics |
Update project topics/tags |
list_epics |
List epics for a group (Premium/Ultimate) |
create_epic |
Create epics (Premium/Ultimate) |
get_latest_pipeline |
Get latest CI/CD pipeline |
list_pipeline_jobs |
List pipeline jobs with filtering |
get_job_log |
Get complete job log output |
download_job_trace |
Download job logs to files |
License
MIT License. See LICENSE for details.
Support
For issues, questions, or feature requests, please create an issue in the repository.
GitLab MCP questions
What tools does GitLab MCP provide?
It exposes 16 tools, including list_issues, create_issues, update_issues, add_issue_note, list_labels.
What permissions are required for the GitLab token?
You need a GitLab personal access token with api, read_api, and write_api scopes.
Can I use this with a self-hosted GitLab instance?
Yes, you can specify your own instance by setting the GITLAB_URI environment variable.
Can I disable specific tool categories to optimize token usage?
Yes, you can use various --no flags such as --no-issues or --no-pipelines to disable specific tool categories.