GitLab MCP Server

Name: GitLab MCP Server
Author: pci-frontend

@pci-frontend

Repository

About GitLab MCP Server

No overview available yet

#gitlab #mcp-server #project-management

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "mcp-server-gitlab-pci-frontend": {
      "command": "docker",
      "args": [
        "build",
        "-t",
        "vonwig/gitlab:mcp",
        "-f",
        "src/gitlab/Dockerfile",
        "."
      ]
    }
  }
}

Tools

`project_id` (string): Project ID or URL-encoded path

File content and commit details

`project_id` (string): Project ID or URL-encoded path

Updated branch reference

`search` (string): Search query

Project search results

`name` (string): Project name

Created project details

`project_id` (string): Project ID or URL-encoded path

File/directory contents

`project_id` (string): Project ID or URL-encoded path

Created issue details

`project_id` (string): Project ID or URL-encoded path

Created merge request details

`project_id` (string): Project ID or URL-encoded path

Forked project details

`project_id` (string): Project ID or URL-encoded path

Created branch reference

Overview

What is GitLab MCP Server?

A Model Context Protocol server that integrates with the GitLab API, enabling AI assistants to perform project management, file operations, and repository tasks directly within GitLab. It is designed for developers and teams using GitLab who want to automate workflows via an MCP client like Claude Desktop.

How to use GitLab MCP Server?

Obtain a GitLab Personal Access Token with the required scopes (api, read_api, read_repository, write_repository). Then configure your MCP client by adding the server to claude_desktop_config.json using either a Docker container or npx. Set the environment variables GITLAB_PERSONAL_ACCESS_TOKEN and optionally GITLAB_API_URL for self-hosted instances.

Key features of GitLab MCP Server

Automatic branch creation when performing file operations
Comprehensive error handling with clear messages
Git history preservation without force pushing
Support for both single-file and batch file operations
Tools for issues, merge requests, and repository management

Use cases of GitLab MCP Server

Create, update, or rename files in a GitLab project automatically
Push multiple files in a single commit to streamline workflows
Search for GitLab projects and retrieve file or directory contents
Create issues, merge requests, and branches programmatically
Fork repositories and create new projects with specified visibility

FAQ from GitLab MCP Server

What GitLab Personal Access Token scopes are required?

The api scope is needed for full API access. For read‑only operations, use read_api, read_repository, and write_repository for repository operations.

Can I use this server with a self-hosted GitLab instance?

Yes, set the GITLAB_API_URL environment variable to your self-hosted GitLab API base URL (e.g., https://gitlab.example.com/api/v4).

Does the server require any runtime dependencies?

It can be run via Docker (no local runtime needed) or via npx, which requires Node.js to be installed.

Where does data reside when using this server?

All operations interact with the GitLab API; no local storage is used. Data lives on your GitLab instance (cloud or self-hosted).

How does the server authenticate with GitLab?

Authentication is handled via a GitLab Personal Access Token provided through the GITLAB_PERSONAL_ACCESS_TOKEN environment variable.

Comments

More Version Control MCP servers

Integrate MCP with GitHub Copilot

skills

Learn how to use MCP Servers with GitHub Copilot

225

MCP Linear

tacticlaunch

MCP server that enables AI assistants to interact with Linear project management system through natural language, allowing users to retrieve, create, and update issues, projects, and teams.

141