GitLab MCP Server
Interacts with a GitLab server, providing tools for managing projects, issues, notes, searches, todos, and wiki pages.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@GitLab MCP Server list my projects"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
GitLab MCP Server
interact with a GitLab server.
This is a TypeScript-based MCP server that interacts with a self-hosted GitLab instance. The server provides tools to fetch and manage GitLab data, specifically projects, issues, and issue notes (comments). The available tools are: list_projects, get_issues, get_issue_notes, search, get_issue, get_todos, get_wiki_page, and list_wiki_pages.
Features
This GitLab MCP server provides the following tools:
list_projects: Lists all projects accessible to the user.get_issues: Gets issues for a specific project, with basic filtering.get_issue_notes: Gets notes (comments) for a specific issue.search: Searches for projects and issues based on a search term.get_issue: Retrieves a specific issue from a project using its ID and IID.get_todos: Retrieves a list of to-do items with optional filters.get_wiki_page: Retrieves a specific wiki page by project ID and slug.list_wiki_pages: Retrieves all wiki pages for a given project.
Related MCP server: gitlab-mcp
Development
Install dependencies:
npm installBuild the server:
npm run buildFor development with auto-rebuild:
npm run watchInstallation
To use with Claude Desktop, add the server config:
{
"mcpServers": {
"gitlab-server": {
"command": "/path/to/gitlab-server/build/index.js",
"env": {
"GITLAB_API_TOKEN": "<Gitlab API Token >",
"GITLAB_HOST": "<GitLab Host URL>"
}
}
}
}Debugging
Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the MCP Inspector, which is available as a package script:
npm run inspectorThe Inspector will provide a URL to access debugging tools in your browser.
GitLab API Documentation
https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/api https://gitlab.com/gitlab-org/gitlab/-/raw/master/doc/api/rest/_index.md https://gitlab.com/gitlab-org/gitlab/-/raw/master/doc/api/rest/authentication.md https://gitlab.com/gitlab-org/gitlab/-/raw/master/doc/api/projects.md https://gitlab.com/gitlab-org/gitlab/-/raw/master/doc/api/issues.md https://gitlab.com/gitlab-org/gitlab/-/raw/master/doc/api/notes.md https://gitlab.com/gitlab-org/gitlab/-/raw/master/doc/api/issue_links.md https://gitlab.com/gitlab-org/gitlab/-/raw/master/doc/api/search.md https://gitlab.com/gitlab-org/gitlab/-/raw/master/doc/api/wikis.md
Available Tools
16 toolsgitlab_create_branchCreate BranchC
Create a new branch in the project
Inputs: ref (required), branch (required), projectId (required).
gitlab_create_issueCreate IssueA
Create a new issue in a project
Inputs: title (required), projectId (required), labels, description, +3 more.
gitlab_create_issue_noteCreate Issue NoteB
Create a new note/comment on an issue
Inputs: body (required), issueIid (required), projectId (required), internal, +2 more.
gitlab_create_merge_requestCreate Merge RequestC
Create a new merge request
Inputs: title (required), projectId (required), source_branch (required), target_branch (required), +2 more.
gitlab_edit_issueEdit IssueB
Edit an existing issue in a project
Inputs: issueIid (required), projectId (required), title, labels, +4 more.
gitlab_edit_issue_noteEdit Issue NoteB
Edit an existing note/comment on an issue
Inputs: body (required), noteId (required), issueIid (required), projectId (required).
gitlab_edit_merge_requestEdit Merge RequestC
Update an existing merge request
Inputs: projectId (required), merge_request_iid (required), title, assignee_id, +3 more.
gitlab_get_issueGet IssueA
Get a specific issue from a project
Inputs: issueIid (required), projectId (required).
gitlab_get_issue_notesGet Issue NotesB
Get notes for an issue (paginated)
Inputs: issueIid (required), projectId (required), page.
gitlab_get_issuesGet IssuesA
Get issues for a project or globally (paginated)
Inputs: page, type, state, action, +3 more.
gitlab_get_todosGet TodosB
Get a list of to-do items (paginated)
Inputs: page, type, state, action, +3 more.
gitlab_get_wiki_pageGet Wiki PageC
Get a wiki page for a given project
Inputs: slug (required), projectId (required), version, render_html.
gitlab_list_milestonesList MilestonesA
Get a list of project milestones (paginated)
Inputs: projectId (required), page, state, search.
gitlab_list_projectsList ProjectsA
List all projects (paginated)
Inputs: page.
gitlab_list_wiki_pagesList Wiki PagesA
Get all wiki pages for a given project. (paginated)
Inputs: projectId (required), page, with_content.
gitlab_searchSearchB
Search for projects, issues, merge requests, and more. (paginated)
Inputs: scope (required), search (required), page, projectId.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 16 tools
Each tool targets a distinct resource-action pair. Even similar-looking list/get pairs are clarified by singular/plural naming and descriptions. The search tool is intentionally broader but not confusable with the specific list tools.
All tools use the gitlab_ prefix and snake_case, but collection endpoints are inconsistent: list_ is used for projects, wiki pages, and milestones, while get_ is used for issues, todos, and issue notes. This mixed convention is readable but not uniform.
At 16 tools the set is slightly above the typical well-scoped range, but each tool addresses a distinct operation. The cluster of issue-related tools is granular but reasonable for a GitLab-focused server.
The tool surface covers issue creation/editing and MR creation/editing, but lacks list/get merge requests, which creates a dead end for locating MRs to edit. There are also no delete operations, and project management is limited to listing.
Maintenance
Related MCP Connectors
Unofficial GitLab MCP — wraps the GitLab REST API v4 (BYO API key)
GitLab Public MCP — wraps the GitLab REST API v4 (public endpoints, no auth)
Go MCP server for GitLab: 2 dynamic tools reach 1000+ REST/GraphQL actions. Free/CE, no paid tier.
Related MCP Servers
- -licenseAqualityBmaintenanceMCP Server for the GitLab API, enabling project management, file operations, and more.95,950 npm92,096MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for interacting with GitLab API, supporting both self-hosted instances and gitlab.com. Provides tools for managing issues, merge requests, code review, pipelines, milestones, releases, search, and file access.MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for the GitLab REST API providing tools to manage projects, merge requests, pipelines, CI/CD variables, approvals, issues, and code reviews.3,759 PyPI7MIT
- AlicenseAqualityDmaintenanceEnables 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.103MIT