GitLab MCP server tools

Tier: Premium, Ultimate
Add-on: GitLab Duo Core, Pro, or Enterprise
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Status: Beta

To provide feedback on this feature, leave a comment on issue 561564.

The GitLab MCP server provides a set of tools that integrate with your existing GitLab workflows. You can use these tools to interact directly with GitLab and perform common GitLab operations.

`get_mcp_server_version`

Returns the current version of the GitLab MCP server.

Example:

What version of the GitLab MCP server am I connected to?

`create_issue`

Creates a new issue in a GitLab project.

Parameter	Type	Required	Description
`id`	string	Yes	ID or URL-encoded path of the project.
`title`	string	Yes	Title of the issue.
`description`	string	No	Description of the issue.
`assignee_ids`	array of integers	No	Array of IDs of assigned users.
`milestone_id`	integer	No	ID of the milestone.
`labels`	array of strings	No	Array of label names.
`confidential`	boolean	No	Sets the issue to confidential. Default is `false`.
`epic_id`	integer	No	ID of the linked epic.

Example:

Create a new issue titled "Fix login bug" in project 123 with description
"Users cannot log in with special characters in password"

`get_issue`

Retrieves detailed information about a specific GitLab issue.

Parameter	Type	Required	Description
`id`	string	Yes	ID or URL-encoded path of the project.
`issue_iid`	integer	Yes	Internal ID of the issue.

Example:

Get details for issue 42 in project 123

`create_merge_request`

Creates a merge request in a project.

Parameter	Type	Required	Description
`id`	string	Yes	ID or URL-encoded path of the project.
`title`	string	Yes	Title of the merge request.
`source_branch`	string	Yes	Name of the source branch.
`target_branch`	string	Yes	Name of the target branch.
`target_project_id`	integer	No	ID of the target project.

Example:

Create a merge request in project gitlab-org/gitlab titled "Bug fix broken specs"
from branch "fix/specs-broken" into "master" and enable squash

`get_merge_request`

Retrieves detailed information about a specific GitLab merge request.

Parameter	Type	Required	Description
`id`	string	Yes	ID or URL-encoded path of the project.
`merge_request_iid`	integer	Yes	Internal ID of the merge request.

Example:

Get details for merge request 15 in project gitlab-org/gitlab

`get_merge_request_commits`

Retrieves the list of commits in a specific merge request.

Parameter	Type	Required	Description
`id`	string	Yes	ID or URL-encoded path of the project.
`merge_request_iid`	integer	Yes	Internal ID of the merge request.
`per_page`	integer	No	Number of commits per page.
`page`	integer	No	Current page number.

Example:

Show me all commits in merge request 42 from project 123

`get_merge_request_diffs`

Retrieves the diffs for a specific merge request.

Parameter	Type	Required	Description
`id`	string	Yes	ID or URL-encoded path of the project.
`merge_request_iid`	integer	Yes	Internal ID of the merge request.
`per_page`	integer	No	Number of diffs per page.
`page`	integer	No	Current page number.

Example:

What files were changed in merge request 25 in the gitlab project?

`get_merge_request_pipelines`

Retrieves the pipelines for a specific merge request.

Parameter	Type	Required	Description
`id`	string	Yes	ID or URL-encoded path of the project.
`merge_request_iid`	integer	Yes	Internal ID of the merge request.

Example:

Show me all pipelines for merge request 42 in project gitlab-org/gitlab

`get_pipeline_jobs`

Retrieves the jobs for a specific CI/CD pipeline.

Parameter	Type	Required	Description
`id`	string	Yes	ID or URL-encoded path of the project.
`pipeline_id`	integer	Yes	ID of the pipeline.
`per_page`	integer	No	Number of jobs per page.
`page`	integer	No	Current page number.

Example:

Show me all jobs in pipeline 12345 for project gitlab-org/gitlab

`create_workitem_note`

Creates a new note (comment) on a GitLab work item.

Parameter	Type	Required	Description
`body`	string	Yes	Content of the note.
`url`	string	No	GitLab URL for the work item (for example, `https://gitlab.com/namespace/project/-/work_items/42`). Required if `group_id` or `project_id` and `work_item_iid` are missing.
`group_id`	string	No	ID or path of the group. Required if `url` and `project_id` are missing.
`project_id`	string	No	ID or path of the project. Required if `url` and `group_id` are missing.
`work_item_iid`	integer	No	Internal ID of the work item. Required if `url` is missing.
`internal`	boolean	No	Marks the note as internal (visible only to users with at least the Reporter role for the project). Default is `false`.
`discussion_id`	string	No	Global ID of the discussion to reply to (in the format `gid://gitlab/Discussion/<id>`).

Example:

Add a comment "This looks good to me" to work item 42 in project gitlab-org/gitlab

`gitlab_search`

Searches for a term across the entire GitLab instance with the search API. This tool is available for global, group, and project search. Available scopes depend on the search type.

Parameter	Type	Required	Description
`scope`	string	Yes	Search scope (for example, `issues`, `merge_requests`, or `projects`).
`search`	string	Yes	Search term.
`group_id`	string	No	ID or URL-encoded path of the group you want to search.
`project_id`	string	No	ID or URL-encoded path of the project you want to search.
`state`	string	No	State of search results (for `issues` and `merge_requests`).
`confidential`	boolean	No	Filters results by confidentiality (for `issues`). Default is `false`.
`fields`	array of strings	No	Array of fields you want to search (for `issues` and `merge_requests`).
`order_by`	string	No	Attribute to order results by. Default is `created_at` for basic search and relevance for advanced search.
`sort`	string	No	Sort direction for results. Default is `desc`.
`per_page`	integer	No	Number of results per page. Default is `20`.
`page`	integer	No	Current page number. Default is `1`.

Example:

Search issues for "flaky test" across GitLab

`semantic_code_search`

Offering: GitLab.com

Searches for relevant code snippets in a project.

This tool is available only for projects with GitLab Duo turned on. Project files must be indexed into vector embeddings.

If this tool is invoked for a project without vector embeddings, indexing is triggered ad-hoc and the agent uses a different tool. This tool then becomes available after a few minutes.

Parameter	Type	Required	Description
`semantic_query`	string	Yes	Search query for the code.
`project_id`	string	Yes	ID or path of the project.
`directory_path`	string	No	Path of the directory (for example, `app/services/`).
`knn`	integer	No	Number of nearest neighbors used to find similar code snippets. Default is `64`.
`limit`	integer	No	Maximum number of results to return. Default is `20`.

Example:

How are authorizations managed in this project?