Provides tools for interacting with gitlab.com projects, including managing issues, merge requests, code reviews, repository files, commits, branches, tags, CI pipelines and jobs, wiki pages, snippets, releases, labels, milestones, deployments, and activity/todos.
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 summarize the failing jobs in my latest pipeline"
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.
An MCP server for gitlab.com. One binary over stdio, signed in as you. It works inside projects: issues, merge requests, reviews, the repository and CI. Instance and group administration, runners, CI variables and tokens are out of scope.
Unofficial, and not affiliated with GitLab Inc. See NOTICE.
A small surface, gated by registration. About sixty tools rather than an API mirror, and a tool that is switched off is not registered, so it cannot be called at all.
Nothing it writes runs a quick action. /merge in a comment is
refused or escaped, never executed.
Content is marked as untrusted. Issues, reviews, files and job logs come back inside boundaries the content cannot close.
Signs in like a desktop app. Your own OAuth application, a browser tab, the token in the OS keyring.
Verifiable releases. Signed checksums, build provenance and SBOMs.
Related MCP server: Taskade MCP Server
Stable: the release badge above names the newest tag, and
CHANGELOG.md says what each one holds. The tool surface is a
contract: tools keep their names and output fields.
docs/architecture.md §16 is the plan.
Tool | What it does |
| Who is signed in, with which scopes, and what GitLab reports about itself |
| Turn a GitLab web URL into the arguments another tool takes, and name that tool |
| Find projects by name, or within a group |
| One project: default branch, visibility, what it has turned on |
| Who has access to a project, and with which role |
| Accounts by exact username or by name |
| Find issues across gitlab.com, a group or a project |
| One issue, its description marked as untrusted content, and its linked merge requests |
| Create an issue; labels, assignees and milestone checked first |
| Change an issue's fields, refused if it changed since you read it |
| The comment threads on an issue or a merge request |
| An issue's or a merge request's label, state, milestone and weight changes, newest first |
| Comment on an issue or merge request, reply in a thread, or start one, on a diff line or not |
| Edit one of your own comments in place, in its thread and on its diff line |
| Resolve or reopen a thread on a merge request or an issue |
| Link two issues, in one project or two |
| Remove the link between two issues |
| Make one merge request wait for another to merge, in one project or two |
| Remove a dependency between two merge requests |
| Find merge requests across gitlab.com or a project |
| One merge request with its approvals, reviewer states, linked issues and dependencies |
| The files a merge request changes, with line counts and GitLab's markers |
| A merge request's diffs, file by file, bounded |
| A merge request's commits |
| A merge request's diff versions, one per push |
| What changed between two versions of a merge request, or since one |
| Open a merge request from a branch |
| Change a merge request's fields, refused if it changed since you read it |
| Set or reset an issue's or a merge request's time estimate, and add or reset its time spent |
| A draft review comment, on the merge request or a diff line |
| Your unpublished review comments on a merge request |
| Delete one of your drafts |
| Change the text of one of your drafts, keeping its place |
| Publish one of your drafts on its own |
| Publish all your drafts at once, with a summary and reviewer state |
| Ask a reviewer for a new review once their requested changes are addressed |
| A file at a ref, bounded |
| A directory listing at a ref |
| A project's branches |
| Commits on a ref or a path |
| One commit and its diff, bounded, and the merge requests that contain it |
| The commits and diffs between two refs, bounded |
| A project's tags |
| Create a branch from a ref |
| Commit file changes to a branch; never the default or a protected one |
| Who last changed each line of a file, bounded |
| Apply a commit to a branch; never the default or a protected one |
| Undo a commit on a branch with a new one; never the default or a protected one |
| A project's CI pipelines |
| One pipeline with the jobs that failed, trigger jobs included |
| A pipeline's jobs |
| A window of a job's log, secrets masked; the failing section on request |
| A pipeline's test counts and failed cases, secrets masked, bounded |
| Check a project's CI configuration at a ref, or configuration you pass |
| The files a job kept as artifacts |
| One text file of a job's artifacts, secrets masked, bounded |
| The labels a project's issues and merge requests can carry |
| A project's or a group's milestones |
| A project's issue boards and their lists, each with the |
| Code, commits, comments and more, in a project, a group or everywhere |
| Your to-do items |
| Mark your to-do items done |
| Add a to-do for yourself on an issue or a merge request |
| Subscribe to an issue's or a merge request's notifications, or unsubscribe |
| Add or remove your emoji reaction on an issue, a merge request or a comment |
| Upload an image from a directory you allowed and get the Markdown that shows it in a comment or description |
| Merge at the head you reviewed, or when the pipeline succeeds (Ship) |
| Stop a merge request merging when its pipeline succeeds (Ship) |
| Approve at the head you reviewed (Ship) |
| Withdraw your approval (Ship) |
| Commit suggestions from a merge request's diff comments to its source branch; never a protected one (Ship) |
| Rebase a merge request's source branch, from the head you reviewed (Ship) |
| Move an issue to another project, never to one more people can see (Ship) |
| Run a pipeline for a ref, with variables whose values are never shown (Ship) |
| Run a merge request's pipeline, merged results or detached as GitLab picks; not for a fork's merge request (Ship) |
| Retry a pipeline's failed and canceled jobs (Ship) |
| Run a finished job again, with inputs (Ship) |
| Start a manual job, with variables and inputs (Ship) |
| Cancel a running pipeline (Ship) |
| Delete a branch; never the default, a protected or an unmerged one unless asked (Destructive) |
| Delete one of your own comments (Destructive) |
| Make a confidential issue public (Destructive) |
| A project wiki's pages ( |
| One wiki page, bounded ( |
| Create a wiki page, or change one unchanged since you read it ( |
| Delete a wiki page ( |
| A project's snippets, or your own ( |
| One snippet and a file of it, bounded ( |
| Create a snippet, always private ( |
| Change one of your own private snippets: title, description, files; refused if it changed since you read it ( |
| Delete one of your own snippets ( |
| A project's releases ( |
| One release and its notes ( |
| Create a release, and its tag at a ref, with asset links to the project's own pages ( |
| Create a tag at a ref; never a protected one ( |
| Delete a tag; never a protected one ( |
| Create a project label ( |
| Change a project label unchanged since you read it ( |
| Delete a project label ( |
| Create a project milestone ( |
| Change, close or reopen a milestone unchanged since you read it ( |
| Delete a project milestone ( |
| A project's environments and their last deployment ( |
| What was deployed where, and by which job ( |
| Recent activity, yours or a project's ( |
Ship and Destructive tools are registered only with the settings below,
and the six toolsets only when GITLAB_MCP_TOOLSETS names them.
Three resources carry the same text for clients that attach rather than call: an issue, a merge request and a job log.
Download an archive for your platform from the releases page, or:
go install github.com/mmedum/gitlab-mcp/v4/cmd/gitlab-mcp@latestClaude Desktop users can open the .mcpb bundle from the same release.
It does not log you in; do the steps below first.
You bring your own OAuth application. Nothing is shipped in the binary, and there are no personal access tokens.
Register an application, once. On gitlab.com: your avatar → Edit
profile → Applications (or a group's). Redirect URI
http://127.0.0.1/callback, Confidential unchecked, scope api
(read_api for read-only). docs/setup.md has the exact values.
Log in from a terminal:
gitlab-mcp login --client-id <application id>It prints the scopes it will ask for, opens your browser, and stores
the token in the OS keyring. On a machine without a browser,
--no-browser prints the URL and the ssh -L line to forward the
callback.
Check it:
gitlab-mcp doctordoctor walks the connection, TLS, the sign-in, the application, the
granted scopes and one call as you, and names what is missing.
status and logout do what they say; --profile keeps two
gitlab.com logins side by side.
Claude Code:
claude mcp add gitlab -- gitlab-mcpAny client that takes a JSON server list:
{
"mcpServers": {
"gitlab": { "command": "gitlab-mcp" }
}
}Claude Desktop can instead open the .mcpb bundle from a release. It
asks for the same settings: merging, approving, applying suggestions,
moving issues, CI and releases (enable_ship) and deleting
(enable_destructive) stay off unless you turn them on, and
write_namespaces confines writes to the groups and projects you name.
This server asks nobody before a call. Claude Desktop approves each
tool, and a tool you always allow then runs unasked, so
leave a switch off unless you need its tools.
Every setting is an environment variable with the GITLAB_MCP_ prefix
and a matching flag. docs/configuration.md lists them all.
GitLab content was written by someone other than you, and some of it is written to steer an agent. The server marks it as untrusted data, never fetches what it references, and nothing it adds tells the model to act on it.
What can be registered depends on the settings, because GitLab's api
scope cannot separate any of it:
Setting | Registers |
| Read tools only, with a |
default | Read and Write: issues, comments, reviews, branches, merge requests |
| adds merging, approving, running CI and releases |
| adds deletion and making an issue public, and each call must pass |
Your MCP client approves each call; the server does not ask you
itself. claude.ai and Codex prompt for the Ship and Destructive tools,
which are marked destructive, and VS Code prompts for every tool that
writes. In Claude Code, delete_label, delete_milestone and
make_issue_public ask on every call whatever your rules say, since
none can be undone and each reaches past the one item: a label or
milestone comes off every issue and merge request, and a public issue
is read by everyone. For the rest, list the
calls you want to approve one by one under permissions.ask in your
settings, with the name you gave the server in place of gitlab. For
example, the writes that ship, publish, upload or delete:
{
"permissions": {
"ask": [
"mcp__gitlab__merge_merge_request", "mcp__gitlab__approve_merge_request",
"mcp__gitlab__apply_suggestions", "mcp__gitlab__run_pipeline",
"mcp__gitlab__run_merge_request_pipeline", "mcp__gitlab__play_job",
"mcp__gitlab__create_release", "mcp__gitlab__create_tag", "mcp__gitlab__move_issue",
"mcp__gitlab__upload_file",
"mcp__gitlab__delete_branch", "mcp__gitlab__delete_comment",
"mcp__gitlab__delete_wiki_page", "mcp__gitlab__delete_label",
"mcp__gitlab__delete_milestone", "mcp__gitlab__delete_tag",
"mcp__gitlab__delete_snippet"
]
}
}No quick actions. GitLab runs /merge, /close and the rest from
a description or comment. Every body this server sends is checked, and
a quick-action line is refused, or escaped when you ask.
Protected branches. Code reaches the default branch or a protected branch only through a merge request; a direct commit there is refused.
No blind retries. A create that may or may not have happened is settled by reading, never by creating again.
Local files only from where you allow. upload_file reads an
image only from the directories GITLAB_MCP_UPLOAD_DIRS names, and
only a PNG, JPEG, GIF or WebP judged from its bytes, so a comment
asking for a key file to be "attached" gets nothing.
The default token can still merge and approve; leaving Ship off stops
this server doing so, not anything else holding the token.
docs/security.md says more.
Each release signs checksums.txt with a keyless Sigstore certificate
and attests every archive and the bundle:
sha256sum -c checksums.txt --ignore-missing
cosign verify-blob checksums.txt --bundle checksums.txt.bundle \
--certificate-identity "https://github.com/mmedum/gitlab-mcp/.github/workflows/release.yml@refs/tags/<tag>" \
--certificate-oidc-issuer https://token.actions.githubusercontent.com
gh attestation verify <archive> --repo mmedum/gitlab-mcpCONTRIBUTING.md. Security reports go through SECURITY.md, not an
issue.
Apache-2.0. See LICENSE and NOTICE.
This server cannot be deployed
Operate GitHub from your AI assistant: repos, PRs, issues, Actions. Previews and read-only mode.
Task management for people and AI agents, with scoped OAuth access to issues, projects, and docs.
Task management for people and AI agents, with scoped OAuth access to issues, projects, and docs.
GitLab MCP — wraps the GitLab REST API v4 (BYO API key)