MCP.so
Sign In

MCP Gitlab Server

@kopiloto

Basic information

Category

Version Control

License

MIT

Transports

stdio

Author

kopiloto

About MCP Gitlab Server

No overview available yet

#mcp-gitlab#gitlab-server#python-gitlab

MCP Gitlab Server config

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

{
  "mcpServers": {
    "GitLab": {
      "command": "uvx",
      "args": [
        "gitlab-mcp-server"
      ],
      "env": {
        "GITLAB_TOKEN": "<your GitLab personal access token>",
        "GITLAB_URL": "https://gitlab.com"
      }
    }
  }
}

MCP Gitlab Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

Fetch the live tool list by running this server in a temporary sandbox using the button above.

Overview

What is mcp-gitlab-server?

mcp-gitlab-server is a GitLab integration server for the Model Context Protocol (MCP). Built on python-gitlab, it provides tools for repository and project management, code reading, and merge request analytics. It is intended for developers and teams using GitLab who want to interact with their projects through MCP clients like Claude Desktop.

How to use mcp-gitlab-server?

Install by adding a configuration entry to your MCP client using the command uvx with the package gitlab-mcp-server. Set the environment variables GITLAB_TOKEN (or GITLAB_OAUTH_TOKEN) and optionally GITLAB_URL (defaults to https://gitlab.com). You can authenticate with a personal access token or an OAuth2 token.

Key features of mcp-gitlab-server

  • List, search, and get details for GitLab projects and groups
  • Read repository code and files with glob filtering and size limits
  • Analyze merge request lifetime statistics (average, percentiles, distribution)
  • Support for GitLab.com and self-hosted GitLab instances
  • Authentication via personal access token or OAuth2 token

Use cases of mcp-gitlab-server

  • Automatically index all projects accessible to a user
  • Read code contents from a repository without cloning it locally
  • Calculate and report merge request turnaround times for a team
  • Search across repositories by name, description, or keywords

Frequently asked questions

1

What authentication methods are supported?

Two methods: Personal Access Token (set `GITLAB_TOKEN`) or OAuth2 Token (set `GITLAB_OAUTH_TOKEN`). The server checks for `GITLAB_OAUTH_TOKEN` first, then falls back to `GITLAB_TOKEN`. You only need to set one.

2

Can I use a self‑hosted GitLab instance?

Yes. Set the `GITLAB_URL` environment variable to your GitLab instance URL (e.g., `https://gitlab.example.com`). If not set, it defaults to `https://gitlab.com`.

3

What environment variables are required?

You must set either `GITLAB_TOKEN` or `GITLAB_OAUTH_TOKEN`. Optionally set `GITLAB_URL` for a non‑default instance. The server will use the OAuth2 token if present; otherwise it uses the personal access token.

4

What tools does mcp-gitlab-server provide?

It offers tools for project/group listing, repository code reading, file reading, search, merge request listing, and merge request analytics (lifetime statistics with percentiles). See the README for the complete list and example usage.

5

Is mcp-gitlab-server ready for production?

No. This project is in **development stage**. Features and APIs may change without notice. Use with caution in production environments.

Comments

More Version Control MCP servers