Skip to main content
Glama
Sign In
GitLab MCP Server

GitLab MCP Server

by ProstoyVadila
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

GitLab MCP Server

An MCP (Model Context Protocol) server that allows LLMs to interact with GitLab. Access issues, merge requests, pipelines, and repository files directly from Claude Code or other MCP-compatible clients.

Features

  • Browse and search projects

  • View issues and merge requests (including your own and team-labeled)

  • Read MR diffs and comments

  • Check pipeline status and job logs

  • Browse repository files

Related MCP server: gitlab-mcp-server

Setup

1. Install dependencies

make install
# or
uv sync

2. Create GitLab Personal Access Token

  1. Go to GitLab → Avatar (top-right) → Edit profile

  2. Left sidebar → Access Tokens

  3. Click Add new token

  4. Configure:

    • Token name: e.g., "MCP Server"

    • Expiration date: choose as needed

    • Scopes:

      • read_api (required)

      • read_repository (for file content access)

  5. Click Create personal access token

  6. Copy the token (won't be shown again)

Direct URL: https://gitlab.com/-/user_settings/personal_access_tokens

3. Configure environment

cp .env.example .env

Edit .env with your values:

GITLAB_URL=https://gitlab.com
GITLAB_TOKEN=your-private-token-here
DEFAULT_ASSIGNEE=me

Configuration

Variable

Description

Default

GITLAB_URL

Your GitLab instance URL

https://gitlab.com

GITLAB_TOKEN

Personal access token

(required)

DEFAULT_ASSIGNEE

Username for "my_*" tools filters

me

Usage

Run directly

uv run python main.py

Run in background

make start    # Start server
make stop     # Stop server
make restart  # Restart server
make status   # Check if running
make logs     # Tail server logs

Add to Claude Code

Create .mcp.json in your project root:

{
  "mcpServers": {
    "gitlab": {
      "command": "uv",
      "args": ["run", "python", "main.py"],
      "cwd": "/path/to/gitlab-mcp-server"
    }
  }
}

Or use the CLI:

claude mcp add gitlab -- uv run python main.py

Verify with /mcp command inside Claude Code.

Test the server

# Test with MCP Inspector
npx @modelcontextprotocol/inspector uv run python main.py

# Test API connection
uv run python -c "
from tools.projects import get_client
with get_client() as client:
    r = client.get('/user')
    print('Authenticated as:', r.json().get('username'))
"

Available Tools

Projects

Tool

Description

list_projects

List accessible projects (search, filter by ownership/membership)

get_project

Get project details by path

Issues

Tool

Description

list_issues

List issues in a project (filter by state, labels, search)

my_issues

List issues assigned to you (uses DEFAULT_ASSIGNEE)

team_issues

List issues with a team label (default: "RE")

get_issue

Get issue details including description

get_issue_comments

Get comments/notes on an issue

Merge Requests

Tool

Description

list_merge_requests

List MRs in a project (filter by state, branches, search)

my_merge_requests

List MRs assigned to you

my_merge_requests_to_review

List MRs where you are a reviewer

team_merge_requests

List MRs with a team label (default: "RE")

get_merge_request

Get MR details including description

get_merge_request_changes

Get MR file diffs

get_merge_request_comments

Get MR comments/discussions

Pipelines

Tool

Description

list_pipelines

List pipelines in a project (filter by status, branch)

get_pipeline_jobs

Get jobs for a pipeline

get_job_log

Get job log output

Repository

Tool

Description

list_repository_tree

List files/directories in a repo

get_file_content

Get file content from a repo

Project Structure

gitlab-mcp-server/
├── main.py           # Entry point
├── client.py         # HTTP client & settings
├── models.py         # Pydantic models
├── tools/
│   ├── projects.py   # Project tools
│   ├── issues.py     # Issue tools
│   ├── merge_requests.py  # MR tools
│   ├── pipelines.py  # Pipeline tools
│   └── repository.py # Repository tools
├── .env.example      # Environment template
└── Makefile          # Run commands

License

MIT

Available Tools

19 tools
get_file_contentA

Get the content of a file from the repository.

Args: project_path: Full path of the project (e.g., 'group/project') file_path: Path to the file within the repository ref: Branch name, tag, or commit SHA (defaults to 'main')

Inputs: file_path (required), project_path (required), ref. Returns: ref, size, content, file_name, +1 more

get_issueA

Get details of a specific issue.

Args: project_path: Full path of the project (e.g., 'group/project') issue_iid: The internal ID of the issue within the project

Inputs: issue_iid (required), project_path (required). Returns: iid, state, title, author, +9 more

get_issue_commentsA

Get comments/notes on a specific issue.

Args: project_path: Full path of the project (e.g., 'group/project') issue_iid: The internal ID of the issue within the project per_page: Number of results per page (max 100)

Inputs: issue_iid (required), project_path (required), per_page. Returns: result

get_job_logA

Get the log/trace output of a specific job.

Args: project_path: Full path of the project (e.g., 'group/project') job_id: The ID of the job

Inputs: job_id (required), project_path (required). Returns: result

get_merge_requestA

Get details of a specific merge request.

Args: project_path: Full path of the project (e.g., 'group/project') mr_iid: The internal ID of the merge request within the project

Inputs: mr_iid (required), project_path (required). Returns: iid, draft, state, title, +15 more

get_merge_request_changesA

Get the file changes (diff) of a merge request.

Args: project_path: Full path of the project (e.g., 'group/project') mr_iid: The internal ID of the merge request within the project

Inputs: mr_iid (required), project_path (required). Returns: iid, title, changes, changes_count

get_merge_request_commentsA

Get comments/notes on a specific merge request.

Args: project_path: Full path of the project (e.g., 'group/project') mr_iid: The internal ID of the merge request within the project per_page: Number of results per page (max 100)

Inputs: mr_iid (required), project_path (required), per_page. Returns: result

get_pipeline_jobsB

Get jobs for a specific pipeline.

Args: project_path: Full path of the project (e.g., 'group/project') pipeline_id: The ID of the pipeline per_page: Number of results per page (max 100)

Inputs: pipeline_id (required), project_path (required), per_page. Returns: result

get_projectA

Get details of a specific GitLab project.

Args: project_path: Full path of the project (e.g., 'group/project' or 'user/project')

Inputs: project_path (required). Returns: id, name, topics, web_url, +6 more

list_issuesB

List issues in a GitLab project.

Args: project_path: Full path of the project (e.g., 'group/project') state: Filter by state: 'opened', 'closed', or 'all' labels: Comma-separated list of label names to filter by search: Search term to filter issues per_page: Number of results per page (max 100)

Inputs: project_path (required), state, labels, search, +1 more. Returns: result

list_merge_requestsA

List merge requests in a GitLab project.

Args: project_path: Full path of the project (e.g., 'group/project') state: Filter by state: 'opened', 'closed', 'merged', or 'all' target_branch: Filter by target branch name source_branch: Filter by source branch name search: Search term to filter merge requests per_page: Number of results per page (max 100)

Inputs: project_path (required), state, search, per_page, +2 more. Returns: result

list_pipelinesA

List pipelines in a GitLab project.

Args: project_path: Full path of the project (e.g., 'group/project') status: Filter by status: 'running', 'pending', 'success', 'failed', 'canceled', 'skipped' ref: Filter by branch or tag name per_page: Number of results per page (max 100)

Inputs: project_path (required), ref, status, per_page. Returns: result

list_projectsA

List GitLab projects accessible to the authenticated user.

Args: search: Search term to filter projects by name owned: If true, only return projects owned by the user membership: If true, only return projects the user is a member of per_page: Number of results per page (max 100)

Inputs: owned, search, per_page, membership. Returns: result

list_repository_treeA

List files and directories in a repository.

Args: project_path: Full path of the project (e.g., 'group/project') path: Path inside the repository to list (empty for root) ref: Branch name, tag, or commit SHA (defaults to 'main') recursive: If true, list files recursively per_page: Number of results per page (max 100)

Inputs: project_path (required), ref, path, per_page, +1 more. Returns: result

my_issuesA

List issues assigned to the current authenticated user across all projects or a specific project.

Args: state: Filter by state: 'opened', 'closed', or 'all' project_path: Optional - filter to a specific project (e.g., 'group/project') per_page: Number of results per page (max 100)

Inputs: state, per_page, project_path. Returns: result

my_merge_requestsA

List merge requests assigned to the current authenticated user across all projects or a specific project.

Args: state: Filter by state: 'opened', 'closed', 'merged', or 'all' project_path: Optional - filter to a specific project (e.g., 'group/project') per_page: Number of results per page (max 100)

Inputs: state, per_page, project_path. Returns: result

my_merge_requests_to_reviewA

List merge requests where the current user is a reviewer across all projects or a specific project.

Args: state: Filter by state: 'opened', 'closed', 'merged', or 'all' project_path: Optional - filter to a specific project (e.g., 'group/project') per_page: Number of results per page (max 100)

Inputs: state, per_page, project_path. Returns: result

team_issuesA

List issues with a specific team label across all projects or a specific project.

Args: label: Team label to filter by (defaults to 'RE') state: Filter by state: 'opened', 'closed', or 'all' project_path: Optional - filter to a specific project (e.g., 'group/project') per_page: Number of results per page (max 100)

Inputs: label, state, per_page, project_path. Returns: result

team_merge_requestsA

List merge requests with a specific team label across all projects or a specific project.

Args: label: Team label to filter by (defaults to 'RE') state: Filter by state: 'opened', 'closed', 'merged', or 'all' project_path: Optional - filter to a specific project (e.g., 'group/project') per_page: Number of results per page (max 100)

Inputs: label, state, per_page, project_path. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A3.7/5.0

    Scored across 19 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose. Retrieval tools for files, issues, merge requests, pipelines, and projects are separate, and specialized filters (my_*, team_*) are well-differentiated with explicit descriptions.

    Naming Consistency5/5

    Tool names follow a consistent verb_noun pattern (e.g., get_*, list_*, my_*). The use of 'get' for single items and 'list' for multiple is conventional and predictable.

    Tool Count4/5

    19 tools is on the higher side but still reasonable for a GitLab MCP server covering file, issue, merge request, pipeline, and project operations. The count reflects the breadth of GitLab's features without being excessive.

    Completeness2/5

    The tool set is entirely read-only, lacking any create, update, or delete operations for issues, merge requests, projects, or pipelines. This is a significant gap that prevents agents from performing common management tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers

    • GitLab MCP Server

      CarmeloRicarte
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with GitLab for managing projects, branches, issues, and merge requests. It provides tools for searching code and performing file operations like reading and writing directly within repositories.
      7 npm
      MIT

    • gitlab-mcp-server

      kopiloto
      A
      license
      A
      quality
      D
      maintenance
      Enables interacting with GitLab repositories, merge requests, and code through natural language using MCP. Supports authentication with personal access tokens or OAuth2, and provides tools for listing projects, reading repository code, and analyzing merge request lifetimes.
      10
      3
      MIT