GitLab MCP Server
Owner verifiedOCI · GHCR.IO/JMRPLENS/GITLAB-MCP-SERVER · 9 COMPONENTS
Go MCP server for GitLab: 2 dynamic tools reach ~876 actions on Free/CE, up to ~1103 on Ultimate.
Available components
Last scanned (21 hours ago)
Scores higher than 99% of OCI 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 Security8
- 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
- CVE check failed: a known advisory affects this package; its severity couldn't be graded. See how to fix → View diagnostics → Fail
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this image's dependency list comes from an SBOM its publisher attached. It names packages and versions but not whether each is deprecated, still maintained or linked to its source, so there is nothing we can fairly grade.Unverified
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to jmrplens/gitlab-mcp-server). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1289 tokens (~128/item across 10 items; 2 tools + 8 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 Management70
- Stability observed for 21 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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 4 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
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.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
- CVE-2026-111943 affects this package: none ▼ security
- 20 Oct 26 +38
- Injection markers: unverified → pass ▲ security
- Schema quality: unverified → 100 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.57 ▲ functional
- Package version: 3.2.0@sha256:054f99756efb1182aff73effb2a8861ddde8c90146d2e2b3efafd459647d69f8 → 3.3.0@sha256:88784f176a65d934c4a181eb832a525e94f106f49189cb9c6fde907dd00cf19c functional
- Package version: 3.1.0@sha256:87e483299a2663a7a5d4d28679859b0c7fba2b1a421b7de2652441a569d4a2fc → 3.2.0@sha256:054f99756efb1182aff73effb2a8861ddde8c90146d2e2b3efafd459647d69f8 functional
- 19 Oct 26 0
- Package version: 3.1.0@sha256:87e483299a2663a7a5d4d28679859b0c7fba2b1a421b7de2652441a569d4a2fc → 3.2.0@sha256:054f99756efb1182aff73effb2a8861ddde8c90146d2e2b3efafd459647d69f8 functional
- 18 Oct 26 0
- Package version: 3.1.0@sha256:87e483299a2663a7a5d4d28679859b0c7fba2b1a421b7de2652441a569d4a2fc → 3.2.0@sha256:054f99756efb1182aff73effb2a8861ddde8c90146d2e2b3efafd459647d69f8 functional
- 17 Oct 26 0
- Package version: 3.1.0@sha256:87e483299a2663a7a5d4d28679859b0c7fba2b1a421b7de2652441a569d4a2fc → 3.2.0@sha256:054f99756efb1182aff73effb2a8861ddde8c90146d2e2b3efafd459647d69f8 functional
- 16 Oct 26 0
- Package version: 3.1.0@sha256:87e483299a2663a7a5d4d28679859b0c7fba2b1a421b7de2652441a569d4a2fc → 3.2.0@sha256:054f99756efb1182aff73effb2a8861ddde8c90146d2e2b3efafd459647d69f8 functional
- 14 Oct 26 +4
- Tool safety: Tool safety not yet verified: our sandbox run could not list this package's tools (it declared tools, or its tool listing failed outright). security
- Stability: Stability not yet verified: one of the two schema captures we compare could not list the server's tools (the server declared tools, or its tool listing failed outright). Comparing them would report every tool as removed, or find nothing to compare at all. security
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: Tool coverage not yet verified: our sandbox run could not list this package's tools (it declared tools, or its tool listing failed outright). functional
- Schema quality: Schema quality not yet verified: our sandbox run could not list this package's tools (it declared tools, or its tool listing failed outright), so the captured schema is incomplete. functional
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 24 Oct 2026 · Analysed oci/ghcr.io/jmrplens/gitlab-mcp-server@3.3.0@sha256:88784f176a65d934c4a181eb832a525e94f106f49189cb9c6fde907dd00cf19c
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 | oci |
| Reason | Verified |
| Discovered via | OCI referrers API |
| Source repo | jmrplens/gitlab-mcp-server |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/jmrplens/gitlab-mcp-server/.github/workflows/release.yml@refs/tags/v3.3.0 |
| Rekor log index | 3332358810 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha256:88784f176a65d934c4a181eb832a525e94f106f49189cb9c6fde907dd00cf19c |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 2 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GO-2026-6809 | CVE-2026-111943 | none | yes | |
| ALPINE-CVE-2026-85091 | CVE-2026-85091 | none | yes |
Background: What a vulnerability scan can and cannot prove →
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 →
gitlab_execute_action GitLab Execute Action ~158
Execute one GitLab catalog action by canonical ID or alias. Always pass params as an object. Destructive actions require top-level confirm=true. Use find first only when action or params are unclear. Example: {"action":"issue.list","params":{"project_id":"group/project"}}
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Canonical action ID returned by gitlab_find_action, or a supported compatibility alias, such as project.list, issue.update, or issue.close. |
| confirm | boolean | – | Set top-level confirm=true to explicitly approve destructive actions. Do not put confirm inside params for gitlab_execute_action. |
| params | object | yes | Required action-specific parameters object validated by the selected action schema. Use an empty object for actions with no parameters. |
| Name | Type | Req | Description |
|---|---|---|---|
| next_steps | array | – | Optional. Suggested follow-up actions or tool calls for the LLM, contextual to the result. |
| pagination | object | – | Present on list actions. A REST list carries the fields below: while `has_more` is true, call again with `page` set to `next_page`, or on a keyset page with `page_token` set to `next_page_token`. A G… |
No examples provided.
gitlab_find_action GitLab Find Action ~166
Search the local GitLab action catalog. Read-only and no GitLab API call. Use when the action ID or params are unclear. Returns schemas, hints, destructive flags, and execute examples. Example: {"query":"issue list"}
| Name | Type | Req | Description |
|---|---|---|---|
| explain | boolean | – | When true, include deterministic scoring reasons for each returned action. Defaults to false to keep responses compact. |
| limit | integer | – | Maximum number of matches to return. Defaults to 20 and is capped at 50. |
| query | string | yes | Search terms combining a GitLab domain or resource with a verb, filter, or object name, such as project create, merge request approve, pipeline retry, issue delete, or ci variable. At most 256 charac… |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | Number of returned matches. |
| query | string | yes | Original search query. |
| results | null|array | yes | Matching GitLab catalog actions with schemas and execute examples. |
No examples provided.
How do I install the GitLab MCP Server server?
GitLab MCP Server runs locally as a container image, launched with docker run --rm -i -e GITLAB_URL -e GITLAB_TOKEN -e GITLAB_MCP_SKIP_TLS_VERIFY -e GITLAB_MCP_TOOL_SURFACE -e GITLAB_MCP_CAPABILITY_SURFACE -e GITLAB_MCP_META_PARAM_SCHEMA -e GITLAB_MCP_TIER -e GITLAB_MCP_READ_ONLY -e GITLAB_MCP_SAFE_MODE -e GITLAB_MCP_EMBEDDED_RESOURCES -e GITLAB_MCP_EXCLUDE_TOOLS -e GITLAB_MCP_IGNORE_SCOPES -e GITLAB_MCP_UPLOAD_MAX_FILE_SIZE -e GITLAB_MCP_ALLOWED_UPLOAD_DIRS -e GITLAB_MCP_ALLOWED_DOWNLOAD_DIRS -e GITLAB_MCP_ALLOWED_IMPORT_DIRS -e GITLAB_MCP_RATE_LIMIT_RPS -e GITLAB_MCP_RATE_LIMIT_BURST -e GITLAB_MCP_LOG_LEVEL ghcr.io/jmrplens/gitlab-mcp-server:3.3.0@sha256:88784f176a65d934c4a181eb832a525e94f106f49189cb9c6fde907dd00cf19c. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/jmrplens/gitlab-mcp-server
claude mcp add jmrplens-gitlab-mcp-server -- docker run --rm -i -e GITLAB_URL -e GITLAB_TOKEN -e GITLAB_MCP_SKIP_TLS_VERIFY -e GITLAB_MCP_TOOL_SURFACE -e GITLAB_MCP_CAPABILITY_SURFACE -e GITLAB_MCP_META_PARAM_SCHEMA -e GITLAB_MCP_TIER -e GITLAB_MCP_READ_ONLY -e GITLAB_MCP_SAFE_MODE -e GITLAB_MCP_EMBEDDED_RESOURCES -e GITLAB_MCP_EXCLUDE_TOOLS -e GITLAB_MCP_IGNORE_SCOPES -e GITLAB_MCP_UPLOAD_MAX_FILE_SIZE -e GITLAB_MCP_ALLOWED_UPLOAD_DIRS -e GITLAB_MCP_ALLOWED_DOWNLOAD_DIRS -e GITLAB_MCP_ALLOWED_IMPORT_DIRS -e GITLAB_MCP_RATE_LIMIT_RPS -e GITLAB_MCP_RATE_LIMIT_BURST -e GITLAB_MCP_LOG_LEVEL ghcr.io/jmrplens/gitlab-mcp-server:3.3.0@sha256:88784f176a65d934c4a181eb832a525e94f106f49189cb9c6fde907dd00cf19c
This image reads GITLAB_URL, GITLAB_TOKEN, GITLAB_MCP_SKIP_TLS_VERIFY, GITLAB_MCP_TOOL_SURFACE, GITLAB_MCP_CAPABILITY_SURFACE, GITLAB_MCP_META_PARAM_SCHEMA, GITLAB_MCP_TIER, GITLAB_MCP_READ_ONLY, GITLAB_MCP_SAFE_MODE, GITLAB_MCP_EMBEDDED_RESOURCES, GITLAB_MCP_EXCLUDE_TOOLS, GITLAB_MCP_IGNORE_SCOPES, GITLAB_MCP_UPLOAD_MAX_FILE_SIZE, GITLAB_MCP_ALLOWED_UPLOAD_DIRS, GITLAB_MCP_ALLOWED_DOWNLOAD_DIRS, GITLAB_MCP_ALLOWED_IMPORT_DIRS, GITLAB_MCP_RATE_LIMIT_RPS, GITLAB_MCP_RATE_LIMIT_BURST and GITLAB_MCP_LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.
What is the GitLab MCP Server server?
GitLab MCP Server is listed in the public MCP registry as io.github.jmrplens/gitlab-mcp-server. Go MCP server for GitLab: 2 dynamic tools reach ~876 actions on Free/CE, up to ~1103 on Ultimate. This page covers its container image (ghcr.io/jmrplens/gitlab-mcp-server). Its publisher has verified ownership with us.
Is the GitLab MCP Server server safe to use?
GitLab MCP Server scores 66 out of 100 on VerifyMCP. We recorded 2 known advisories against it as of 24 October 2026. 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 GitLab MCP Server server expose?
GitLab MCP Server exposes 2 tools: gitlab_execute_action, gitlab_find_action. Their descriptions and schemas cost roughly 324 tokens of context every time the server is loaded.
Is the GitLab MCP Server server still maintained?
GitLab MCP Server is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the GitLab MCP Server server under?
GitLab MCP Server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.