mcp-gitlab-server
by yoda-digital·★ 49·Score 47
Production-ready GitLab MCP server with 86 tools, full API coverage, multiple auth modes and transports.
Overview
GitLab MCP Server provides a comprehensive interface between AI agents and GitLab instances, exposing 86 tools covering repositories, files, branches, issues, merge requests, CI/CD pipelines, wikis, groups, and more. It supports stdio, SSE, and Streamable HTTP transports with both PAT and OAuth authentication modes. The server is actively maintained with enterprise-ready features including read-only mode, Docker image, Kubernetes Helm chart, and comprehensive security measures.
Try asking AI
After installing, here are 6 things you can ask your AI assistant:
When to choose this
Choose this for comprehensive GitLab integration with AI agents when you need extensive coverage of GitLab features (86 tools) and production-ready deployments with proper authentication.
When NOT to choose this
Don't choose if you only need basic GitLab operations or if you're already using GitLab's built-in MCP server which provides 15 tools with native GitLab authentication.
Tools this server exposes
12 tools extracted from the READMEsearch_repositoriesSearch for GitLab repositories using various criteria
create_repositoryCreate a new GitLab repository
read_fileRead a file from a GitLab repository
update_fileUpdate a file in a GitLab repository
create_issueCreate a new issue in a GitLab project
create_merge_requestCreate a new merge request in a GitLab project
list_pipelinesList CI/CD pipelines for a project
trigger_pipelineTrigger a new CI/CD pipeline
create_tagCreate a new tag in a GitLab repository
create_releaseCreate a new release in GitLab
list_membersList members of a GitLab project or group
create_groupCreate a new GitLab group
Comparable tools
Installation
Installation
Using npm (for Claude Desktop, Cursor, Zed)
Add to your client's MCP configuration (e.g., claude_desktop_config.json):
{
"mcpServers": {
"gitlab": {
"command": "npx",
"args": ["-y", "@yoda.digital/gitlab-mcp-server"],
"env": {
"GITLAB_PERSONAL_ACCESS_TOKEN": "glpat-…",
"GITLAB_API_URL": "https://gitlab.com/api/v4"
}
}
}
}Using Docker (remote deployment)
docker run --rm -p 3000:3000 \
-e HOST=0.0.0.0 \
-e AUTH_MODE=oauth \
-e USE_STREAMABLE_HTTP=true \
ghcr.io/yoda-digital/mcp-gitlab-server:latestUsing Helm (Kubernetes)
helm install gitlab-mcp oci://ghcr.io/yoda-digital/charts/gitlab-mcpFAQ
- Does this work with self-hosted GitLab instances?
- Yes, set the GITLAB_API_URL environment variable to your instance's API endpoint, e.g., 'https://gitlab.example.com/api/v4'
- Can I use this in read-only mode?
- Yes, set GITLAB_READ_ONLY_MODE=true to hide all write tools and prevent mutations
- What authentication methods are supported?
- Personal Access Token (PAT) for local use and OAuth Bearer tokens for remote deployments
Compare mcp-gitlab-server with
Last updated · Auto-generated from public README + GitHub signals.