GitLab

MCP Server for the GitLab API, enabling project management, file operations, and more. Forked fromhttps://github.com/modelcontextprotocol

- Installation

- NPX (Recommended)
- Global Installation

- List Group Milestones
- Create Group Milestone
- Advanced Group Milestone Search

- 1. Search for Groups
- 2. List Existing Group Milestones
- 3. Create a Group Milestone

- File Operations
- Repository Management
- Issue Management
- Merge Request Management
- Label Management
- Milestone Management
- Group Operations

- Personal Access Token
- Usage with Claude Desktop
- Usage with Cursor/VSCode/Winsurf

npx @therealchristhomas/gitlab-mcp-server

npm install -g @therealchristhomas/gitlab-mcp-server gitlab-mcp

{ "group_id": "my-organization", "state": "active", "include_descendants": true }

{ "group_id": "my-organization", "title": "Q1 2025 Release", "description": "Major feature release including new tools and performance improvements", "due_date": "2025-03-31", "start_date": "2025-01-01" }

{ "group_id": "my-organization/core", "search": "release", "include_ancestors": true, "updated_after": "2024-01-01T00:00:00Z" }

Based on theGitLab Group Milestones API, group milestones are ideal for coordinating releases and features across multiple projects in your organization.

{ "search": "my-organization", "owned": true }

{ "group_id": "my-organization", "state": "active" }

{ "group_id": "my-organization", "title": "Q1 2025 Release", "description": "Cross-project release including webapp, API, and admin features", "due_date": "2025-03-31" }

- project_id(string): Project ID or URL-encoded path
- title(string): Issue title
- description(optional string): Issue description
- assignee_ids(optional number[]): User IDs to assign
- labels(optional string[]): Labels to add
- milestone_id(optional number): Milestone ID

- List all issues in a GitLab project
- Inputs:

- project_id(string): Project ID or URL-encoded path
- state(optional string): 'opened', 'closed', or 'all'
- labels(optional string): Comma-separated list of label names
- milestone(optional string): Milestone title
- assignee_id(optional number): User ID of assignee
- author_id(optional number): User ID of author
- search(optional string): Search against title and description
- created_after(optional string): Return issues created after date (ISO 8601)
- created_before(optional string): Return issues created before date (ISO 8601)
- updated_after(optional string): Return issues updated after date (ISO 8601)
- updated_before(optional string): Return issues updated before date (ISO 8601)
- sort(optional string): Sort issues by various criteria
- order_by(optional string): 'asc' or 'desc'
- page(optional number): Page number for pagination
- per_page(optional number): Results per page (default 20)
- with_labels_details(optional boolean): If true, returns more details for each label. Default is false.

- Update an existing issue in a GitLab project
- Inputs:

- project_id(string): Project ID or URL-encoded path
- issue_iid(number): Issue internal ID
- title(optional string): New issue title
- description(optional string): New issue description
- state_event(optional string): 'close' or 'reopen'
- labels(optional string[]): Array of label names
- assignee_ids(optional number[]): Array of user IDs to assign
- milestone_id(optional number): Milestone ID to assign

- Search for issues in a GitLab project
- Inputs:

- project_id(string): Project ID or URL-encoded path
- search(string): Search term for title and description
- state(optional string): 'opened', 'closed', or 'all'
- labels(optional string): Comma-separated list of label names
- page(optional number): Page number for pagination
- per_page(optional number): Results per page (default 20)

- Add a comment to an issue in a GitLab project
- Inputs:

- project_id(string): Project ID or URL-encoded path
- issue_iid(number): Issue internal ID
- body(string): Content of the comment

- Create a new merge request
- Inputs:

- project_id(string): Project ID or URL-encoded path
- title(string): MR title
- description(optional string): MR description
- source_branch(string): Branch containing changes
- target_branch(string): Branch to merge into
- draft(optional boolean): Create as draft MR
- allow_collaboration(optional boolean): Allow commits from upstream members

- List all merge requests in a GitLab project
- Inputs:

- project_id(string): Project ID or URL-encoded path
- state(optional string): 'opened', 'closed', 'locked', 'merged', or 'all'
- target_branch(optional string): Filter by target branch
- source_branch(optional string): Filter by source branch
- labels(optional string): Comma-separated list of label names
- milestone(optional string): Milestone title
- assignee_id(optional number): User ID of assignee
- author_id(optional number): User ID of author
- search(optional string): Search against title and description
- created_after(optional string): Return MRs created after date (ISO 8601)
- created_before(optional string): Return MRs created before date (ISO 8601)
- updated_after(optional string): Return MRs updated after date (ISO 8601)
- updated_before(optional string): Return MRs updated before date (ISO 8601)
- sort(optional string): Sort merge requests
- order_by(optional string): 'asc' or 'desc'
- page(optional number): Page number for pagination
- per_page(optional number): Results per page (default 20)

- Update an existing merge request in a GitLab project
- Inputs:

- project_id(string): Project ID or URL-encoded path
- merge_request_iid(number): Merge request internal ID
- title(optional string): New merge request title
- description(optional string): New merge request description
- state_event(optional string): 'close' or 'reopen'
- target_branch(optional string): New target branch
- labels(optional string[]): Array of label names
- assignee_ids(optional number[]): Array of user IDs to assign
- milestone_id(optional number): Milestone ID to assign
- remove_source_branch(optional boolean): Remove source branch when merged

- Merge a merge request in a GitLab project
- Inputs:

- project_id(string): Project ID or URL-encoded path
- merge_request_iid(number): Merge request internal ID
- merge_commit_message(optional string): Custom merge commit message
- should_remove_source_branch(optional boolean): Remove source branch after merge
- merge_when_pipeline_succeeds(optional boolean): Merge when pipeline succeeds
- sha(optional string): SHA that must match the source branch HEAD

- Add a comment to a merge request in a GitLab project
- Inputs:

- project_id(string): Project ID or URL-encoded path
- merge_request_iid(number): Merge request internal ID
- body(string): Content of the comment

- List all labels in a project
- Inputs:

- project_id(string): Project ID or URL-encoded path
- page(optional number): Page number for pagination
- per_page(optional number): Results per page (default 20)

- Create a new label
- Inputs:

- project_id(string): Project ID or URL-encoded path
- name(string): Label name
- color(string): Label color (hex code)
- description(optional string): Label description
- priority(optional number): Label priority

- Update an existing label
- Inputs:

- project_id(string): Project ID or URL-encoded path
- name(string): Current label name
- new_name(optional string): New label name
- color(optional string): New label color
- description(optional string): New label description
- priority(optional number): New label priority

- Delete a label
- Inputs:

- project_id(string): Project ID or URL-encoded path
- name(string): Label name to delete

- List all milestones in a project
- Inputs:

- project_id(string): Project ID or URL-encoded path
- state(optional string): 'active' or 'closed'
- page(optional number): Page number for pagination
- per_page(optional number): Results per page (default 20)

- Create a new milestone
- Inputs:

- project_id(string): Project ID or URL-encoded path
- title(string): Milestone title
- description(optional string): Milestone description
- due_date(optional string): Due date (YYYY-MM-DD)
- start_date(optional string): Start date (YYYY-MM-DD)

- Update an existing milestone
- Inputs:

- project_id(string): Project ID or URL-encoded path
- milestone_id(number): Milestone ID
- title(optional string): New title
- description(optional string): New description
- due_date(optional string): New due date
- start_date(optional string): New start date
- state_event(optional string): 'close' or 'activate'

- Delete a milestone
- Inputs:

- project_id(string): Project ID or URL-encoded path
- milestone_id(number): Milestone ID to delete

- List all milestones in a GitLab group
- Inputs:

- group_id(string): Group ID or URL-encoded path
- state(optional string): 'active' or 'closed'
- title(optional string): Filter by milestone title (case-sensitive)
- search(optional string): Search in title or description
- search_title(optional string): Search in title only
- include_ancestors(optional boolean): Include parent group milestones
- include_descendants(optional boolean): Include subgroup milestones
- updated_before(optional string): Filter by update date (ISO 8601)
- updated_after(optional string): Filter by update date (ISO 8601)
- containing_date(optional string): Milestones containing given date
- start_date(optional string): Filter where due_date >= start_date
- end_date(optional string): Filter where start_date <= end_date
- page(optional number): Page number for pagination
- per_page(optional number): Results per page (default 20)

- Create a new milestone in a GitLab group
- Inputs:

- group_id(string): Group ID or URL-encoded path
- title(string): Milestone title
- description(optional string): Milestone description
- due_date(optional string): Due date (YYYY-MM-DD)
- start_date(optional string): Start date (YYYY-MM-DD)

- Update an existing milestone in a GitLab group
- Inputs:

- group_id(string): Group ID or URL-encoded path
- milestone_id(number): Milestone ID
- title(optional string): New title
- description(optional string): New description
- due_date(optional string): New due date
- start_date(optional string): New start date
- state_event(optional string): 'close' or 'activate'

- Delete a milestone from a GitLab group
- Inputs:

- group_id(string): Group ID or URL-encoded path
- milestone_id(number): Milestone ID to delete

Create a GitLab Personal Access Tokenwith appropriate permissions:

{ "mcpServers": { "gitlab": { "command": "npx", "args": ["-y", "@therealchristhomas/gitlab-mcp-server"], "env": { "GITLAB_PERSONAL_ACCESS_TOKEN": "<YOUR_TOKEN>", "GITLAB_API_URL": "https://gitlab.com/api/v4" } } } }

Add the following to your MCP configuration:

{ "mcpServers": { "gitlab": { "command": "npx", "args": ["-y", "@therealchristhomas/gitlab-mcp-server"], "env": { "GITLAB_PERSONAL_ACCESS_TOKEN": "<YOUR_TOKEN>", "GITLAB_API_URL": "https://gitlab.com/api/v4" } } } }

Note: Replace<YOUR_TOKEN>with your actual GitLab Personal Access Token. Also, replace with your Gitlab API URL if you're not using gitlab.com

- GITLAB_PERSONAL_ACCESS_TOKEN: Your GitLab personal access token (required)
- GITLAB_API_URL: Base URL for GitLab API (optional, defaults tohttps://gitlab.com/api/v4)

For self-hosted GitLab instances, update theGITLAB_API_URLto point to your instance:

"GITLAB_API_URL": "https://your-gitlab-instance.com/api/v4"

This MCP server is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the LICENSE file in the project repository.

An improved GitLab MCP server with bug fixes, providing access to GitLab projects, issues, and merge requests.

An improved GitLab MCP server with bug fixes and enhancements for accessing GitLab resources.

A custom GitLab server for interacting with repositories, issues, and merge requests. Requires a GitLab Personal Access Token.

Integrates with the GitLab REST API to manage repositories, issues, and merge requests.

A GitLab integration server providing access to GitLab's RESTful API tools, built on the fastmcp framework.

Interact with Atlassian Bitbucket Cloud to manage repositories, pull requests, workspaces, and code.

Manage pull requests on Bitbucket Server.

Integrate with the GitHub Enterprise API to access repositories, issues, pull requests, and workflows.

Interact with GitLab repositories, issues, and merge requests through an MCP-compliant server.

Seamlessly integrate AI assistants with GitLab using the glab CLI tool.