G

GitLab MCP

Manage GitLab repositories, issues, and pipelines

Official
Version Control
Install Command
npx -y @gitlaborg/mcp-server
Claude Desktop Config
{
  "mcpServers": {
    "gitlab": {
      "command": "npx",
      "args": ["-y", "@gitlaborg/mcp-server"],
      "env": { "GITLAB_PERSONAL_ACCESS_TOKEN": "<TOKEN>", "GITLAB_API_URL": "https://gitlab.com/api/v4" }
    }
  }
}

GitLab MCP is an officially maintained MCP server in the Version Control category, developed by GitLab / Community. It runs locally on your machine, keeping your data private and giving you full control over the connection. Adding it to your setup expands what Claude can do without any extra coding.

About GitLab MCP

GitLab MCP server integrates AI assistants with GitLab for comprehensive DevOps workflows.

Features

  • Manage repositories and branches
  • Create and update issues and merge requests
  • Trigger and monitor CI/CD pipelines
  • Search code across projects
  • Manage users and groups
  • Support for GitLab.com and self-hosted

Who Should Use GitLab MCP?

  • 1Manage repositories, issues, and pull requests through Claude
  • 2Extend Claude and other AI assistants with new capabilities
  • 3Automate tasks that previously required manual steps
  • 4Connect your existing tools to an AI workflow

How to Install GitLab MCP

Before you start

You will need Node.js (v18 or later) installed on your machine — download it from nodejs.org if you haven't already.

  1. 1Open a terminal (Terminal on Mac, Command Prompt or PowerShell on Windows).
  2. 2Paste the install command above and press Enter — Node.js will download and run the server automatically.
  3. 3Add the server to your Claude Desktop config file (see the JSON snippet above) and restart Claude.

The Claude Desktop config snippet above can be copied and pasted directly into your claude_desktop_config.json file — no editing required.

How GitLab MCP Compares

It is an officially maintained server — unlike community alternatives, it is built and supported by the original project team, ensuring compatibility with upstream changes.
It runs entirely on your local machine, so no data leaves your environment — important for teams with privacy or compliance requirements.
Authentication uses API keys, giving you fine-grained control over access without requiring a full OAuth setup.

Tags

gitlabgitcicddevopsrepositories