MCP Catalogs
Home

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.

developer-toolsops-infraproductivity
19
Forks
17
Open issues
this month
Last commit
2d ago
Indexed

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:

you:Enable AI assistants to manage GitLab repositories, create issues and merge requests
you:Automate CI/CD pipeline management through AI agents
you:Provide GitLab access to team members through MCP-compatible clients without direct API access
you:Does this work with self-hosted GitLab instances?
you:Can I use this in read-only mode?
you:What authentication methods are supported?

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 README
  • search_repositories

    Search for GitLab repositories using various criteria

  • create_repository

    Create a new GitLab repository

  • read_file

    Read a file from a GitLab repository

  • update_file

    Update a file in a GitLab repository

  • create_issue

    Create a new issue in a GitLab project

  • create_merge_request

    Create a new merge request in a GitLab project

  • list_pipelines

    List CI/CD pipelines for a project

  • trigger_pipeline

    Trigger a new CI/CD pipeline

  • create_tag

    Create a new tag in a GitLab repository

  • create_release

    Create a new release in GitLab

  • list_members

    List members of a GitLab project or group

  • create_group

    Create a new GitLab group

Comparable tools

gitlab-mcpgitlab-api-integrationsgithub-mcp-servercli-gitlab

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:latest

Using Helm (Kubernetes)

helm install gitlab-mcp oci://ghcr.io/yoda-digital/charts/gitlab-mcp

FAQ

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

GitHub →

Last updated · Auto-generated from public README + GitHub signals.