io.github.mmedum/gitlab-mcp
MCPB · GITLAB-MCP_2.4.0.MCPB
GitLab over MCP from your own account: issues, merge requests, reviews, the repository and CI.
Available components
Last scanned (1 hour ago)
Scores higher than 95% of MCPB servers
Category Version Control
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to mmedum/gitlab-mcp). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 6 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 18362 tokens (~291/item across 63 items; 63 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety94
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 6 of 8 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "get_merge_request" implies "merge" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
- An AI judge read all 64 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +37
- Injection markers: unverified → pass ▲ security
- Stability: unverified → 0.57 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Package version: 2.2.1 → 2.4.0 functional
- 13 Oct 26 +12
- Provenance: unverified → pass ▲ security
- The attested source repository moved: mmedum/gitlab-mcp security
- Maintenance: unverified → pass ▲ functional
- Package version: 2.2.1 → 2.4.0 functional
- 12 Oct 26 0
- Package version: 2.2.1 → 2.4.0 functional
- 11 Oct 26 −46
- Provenance: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.33 → unverified ▼ security
- The attested source repository moved: mmedum/gitlab-mcp security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Maintenance: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 2.2.1 → 2.4.0 functional
- 7 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 33. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Analysed mcpb/https://github.com/mmedum/gitlab-mcp/releases/download/v2.4.0/gitlab-mcp_2.4.0.mcpb@2.4.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | mcpb |
| Reason | Verified |
| Discovered via | GitHub artifact attestations |
| Source repo | mmedum/gitlab-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/mmedum/gitlab-mcp/.github/workflows/release.yml@refs/tags/v2.4.0 |
| Rekor log index | 3182686024 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha256:57fb41d1cbfc831e16650d3d338a59dbb42b0af840a84775f75a76d83fcbdce7 |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
update_merge_request ~638
Change a merge request. Only the fields given change; labels, assignees and reviewers are added and removed, never replaced by a list. updated_at from your latest read is required, and the call is refused [stale] if the merge request changed since. The result reports the fields that changed as GitLab read them back, and says so when nothing did. Merging and approving are not done here. A quick-action line in the description refuses the call unless escape_commands is true. The result names the project's visibility: in a public project, what is written is public.
| Name | Type | Req | Description |
|---|---|---|---|
| add_assignees | null|array | – | Usernames to assign, beside those already assigned |
| add_labels | null|array | – | Label names to add, exactly as they exist; other labels stay |
| add_reviewers | null|array | – | Usernames to request a review from, beside those already asked |
| clear_milestone | boolean | – | Remove the milestone |
| description | null|string | – | A new description, replacing the old one whole; the result counts what it removed |
| draft | null|boolean | – | true marks it a draft, false marks it ready; GitLab keeps this as the title's Draft: prefix |
| dry_run | boolean | – | Return what would be sent, and what the quick-action guard would do to the text, without writing anything |
| escape_commands | boolean | – | GitLab runs a line starting with a slash, such as /close or /merge, as a command. By default such a line refuses the call; true sends each one as plain text instead, with a leading backslash that ren… |
| iid | integer | yes | The merge request's number in its project: the number shown as #12 for issues and !12 for merge requests; not the global id |
| milestone | null|string | – | A milestone's exact title, in the project or its groups |
| project | integer|string | yes | The project: its numeric id, its full path such as group/sub/project, or its web URL |
| remove_assignees | null|array | – | Usernames to unassign |
| remove_labels | null|array | – | Label names to remove; other labels stay |
| remove_reviewers | null|array | – | Usernames to remove as reviewers |
| remove_source_branch | null|boolean | – | Delete the source branch when it is merged, or not |
| squash | null|boolean | – | Squash the commits when it is merged, or not |
| state | string | – | close or reopen |
| target_branch | null|string | – | A new branch to merge into |
| title | null|string | – | A new title |
| updated_at | string | yes | The updated_at of your latest read of it, as get_issue or get_merge_request returned it. The write is refused [stale] if it changed since. A [stale] refusal is NOT a retry signal: read it again and d… |
| Name | Type | Req | Description |
|---|---|---|---|
| assignees | null|array | yes | Usernames |
| changed | null|array | yes | The fields whose value differs after the write, as GitLab reported it |
| description_removed | null|object | yes | What replacing the description took out; null when it was not replaced |
| draft | boolean | yes | – |
| dry_run | boolean | yes | True when nothing was written; the result describes what would have been |
| escaped_commands | null|array | yes | Lines GitLab would have run as quick actions, sent with a leading backslash so they show as text |
| iid | integer | yes | – |
| labels | null|array | yes | – |
| labels_before | null|array | yes | The labels before an update; empty for a create |
| milestone | null|object | yes | – |
| notes | null|array | yes | – |
| outcome | string | yes | created, updated, unchanged or dry_run |
| remove_source_branch | boolean | yes | – |
| reviewers | null|array | yes | Usernames |
| source_branch | string | yes | – |
| squash | boolean | yes | – |
| state | string | yes | – |
| target | object | yes | – |
| target_branch | string | yes | – |
| updated_at | null|string | yes | Pass as updated_at to the next update_merge_request. Null after a create: GitLab moves a new merge request's updated_at within seconds, so read it again first |
| web_url | string | yes | – |
| would_send | null|object | yes | The request a dry run did not send; null when something was written |
No examples provided.
update_review_comment ~402
Replace the text of one of your own draft review comments, keeping it where it is: in its thread or on its line of the diff. Only your drafts can be edited; nobody else sees them until they are published. note_sha256 from your read is required, and the call is refused [stale] if the draft changed since. The result counts what the old text lost and gives the new note_sha256. A quick-action line in the body refuses the call unless escape_commands is true, because GitLab runs it when the draft is published.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | The draft's new text, in Markdown, replacing the old one whole; the result counts what it removed |
| draft_id | integer | yes | The draft's id, as list_review_comments or add_review_comment gave it |
| dry_run | boolean | – | Check the draft and return what would be sent, and what the quick-action guard would do to the text, without writing anything |
| escape_commands | boolean | – | GitLab runs a line starting with a slash, such as /close or /merge, as a command when the draft is published. By default such a line refuses the call; true sends each one as plain text instead, with… |
| iid | integer | yes | The merge request's number in its project: the number shown as #12 for issues and !12 for merge requests; not the global id |
| note_sha256 | string | yes | The draft's note_sha256 as list_review_comments, add_review_comment or the last update_review_comment gave it. The edit is refused [stale] if the draft changed since. A [stale] refusal is NOT a retry… |
| project | integer|string | yes | The project: its numeric id, its full path such as group/sub/project, or its web URL |
| Name | Type | Req | Description |
|---|---|---|---|
| body_removed | null|object | yes | What replacing the text took out; null when it was not replaced |
| discussion_id | string | yes | The thread the draft replies to; empty for one that starts a thread |
| draft_id | integer | yes | – |
| dry_run | boolean | yes | True when nothing was written; the result describes what would have been |
| escaped_commands | null|array | yes | Lines GitLab would have run as quick actions, sent with a leading backslash so they show as text |
| iid | integer | yes | – |
| line_range | null|object | yes | The lines a multi-line draft covers; null for one line |
| note_sha256 | string | yes | The SHA-256 of the draft's text as GitLab holds it now; pass it to the next update_review_comment |
| notes | null|array | yes | – |
| outcome | string | yes | updated, unchanged or dry_run |
| position | null|object | yes | Where on the diff the draft sits, as read back; null for one not on a line |
| target | object | yes | – |
| would_send | null|object | yes | The request a dry run did not send; null when something was written |
No examples provided.
upload_file ~391
Upload an image from this machine to a project and get the Markdown that shows it, to put in a comment (add_comment), a review comment (add_review_comment) or a description (create_issue, update_issue, create_merge_request, update_merge_request) in the same project. The image is read only from the directories GITLAB_MCP_UPLOAD_DIRS names, and must be a PNG, JPEG, GIF or WebP of at most 10 MiB, judged from its bytes; it is sent under its file name with the extension of its type, and nothing else on this machine is read. The result says who can open the image by its link: in a public project anyone, and in a private or internal one anyone too unless the project requires sign-in to view media files; the project's Maintainers can also download any upload by its id. GitLab removes a JPEG's metadata; other images' metadata goes as it is. GitLab keeps the upload even if nothing links to it, and this server cannot delete it. Never repeated after a lost answer. The result names the project's visibility: in a public project, what is written is public. When the client can ask, the server also asks the person before it uploads the image; a call they do not confirm is [blocked], changes nothing, and is not to be made again unless they ask.
| Name | Type | Req | Description |
|---|---|---|---|
| dry_run | boolean | – | Read and check the image and the project, and return what would be sent, without uploading anything |
| path | string | yes | The image's absolute path on this machine, inside a directory GITLAB_MCP_UPLOAD_DIRS names. A PNG, JPEG, GIF or WebP of at most 10 MiB; a symbolic link is refused |
| project | integer|string | yes | The project: its numeric id, its full path such as group/sub/project, or its web URL |
| Name | Type | Req | Description |
|---|---|---|---|
| alt | string | yes | The Markdown's link text, as GitLab chose it |
| content_type | string | yes | image/png, image/jpeg, image/gif or image/webp, read from the file's bytes |
| dry_run | boolean | yes | True when nothing was written; the result describes what would have been |
| escaped_commands | null|array | yes | Lines GitLab would have run as quick actions, sent with a leading backslash so they show as text |
| filename | string | yes | The name the image was sent under: the file's base name, made safe, with the extension of its type |
| full_path | string | yes | The upload's path on gitlab.com, /-/project/<id>/uploads/..., which links it from any project; empty in a dry run |
| link_opens_for | string | yes | Who can open the image by its link: anyone_with_link, project_readers or unknown |
| markdown | string | yes | GitLab's Markdown for the image, to put in a comment, a review comment or a description in the same project; empty in a dry run |
| media_requires_sign_in | null|boolean | yes | The project's setting Require authentication to view media files, as GitLab reported it; null when GitLab did not say |
| notes | null|array | yes | – |
| outcome | string | yes | uploaded or dry_run |
| size | integer | yes | The image's size in bytes |
| target | object | yes | – |
| upload_id | integer | yes | GitLab's id for the upload; 0 in a dry run |
| url | string | yes | The upload's path relative to the project, as the Markdown links it; empty in a dry run |
| would_send | null|object | yes | The request a dry run did not send; null when something was written |
No examples provided.
How do I install the io.github.mmedum/gitlab-mcp server?
io.github.mmedum/gitlab-mcp ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 57fb41d1cbfc831e16650d3d338a59dbb42b0af840a84775f75a76d83fcbdce7; the commands to do that are on this page. If it does not match, do not open it.
mcpb · gitlab-mcp_2.4.0.mcpb
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
57fb41d1cbfc831e16650d3d338a59dbb42b0af840a84775f75a76d83fcbdce7
macOS / Linux
echo "57fb41d1cbfc831e16650d3d338a59dbb42b0af840a84775f75a76d83fcbdce7 gitlab-mcp_2.4.0.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\gitlab-mcp_2.4.0.mcpb).Hash -eq "57fb41d1cbfc831e16650d3d338a59dbb42b0af840a84775f75a76d83fcbdce7"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
What is the io.github.mmedum/gitlab-mcp server?
io.github.mmedum/gitlab-mcp is listed in the public MCP registry as io.github.mmedum/gitlab-mcp. GitLab over MCP from your own account: issues, merge requests, reviews, the repository and CI. This page covers its MCPB bundle (https://github.com/mmedum/gitlab-mcp/releases/download/v2.4.0/gitlab-mcp_2.4.0.mcpb).
Is the io.github.mmedum/gitlab-mcp server safe to use?
io.github.mmedum/gitlab-mcp scores 59 out of 100 on VerifyMCP. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.mmedum/gitlab-mcp server expose?
io.github.mmedum/gitlab-mcp exposes 63 tools: add_comment, add_review_comment, add_todo, cherry_pick_commit, compare_mr_versions, and 58 more. Their descriptions and schemas cost roughly 17,469 tokens of context every time the server is loaded.
What licence is the io.github.mmedum/gitlab-mcp server under?
io.github.mmedum/gitlab-mcp declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.