GitLab MCP Server
Owner verifiedMCPB · GITLAB-MCP-SERVER-LINUX.MCPB · 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 (18 hours ago)
Scores higher than 94% 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 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 Management33
- Stability observed for 10 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
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.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +2
- Maintenance: unverified → pass ▲ functional
- 20 Oct 26 +2
- Maintenance: pass → unverified ▼ functional
- Stability: unverified → 0.20 ▲ functional
- Package version: 3.2.0 → 3.3.0 functional
- 14 Oct 26 +33
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: 100 functional
- First check of Tool coverage: 100 functional
- First check of Tool coverage: 100 functional
- 11 Oct 26 20
First indexed and scored.
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 mcpb/https://github.com/jmrplens/gitlab-mcp-server/releases/download/v3.3.0/gitlab-mcp-server-linux.mcpb@3.3.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 | 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 | 3332446356 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha256:d47b1be9a37bd5d76f862aeab77b036e25e142de13847d31f0342921fb7ae60f |
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 →
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 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, d47b1be9a37bd5d76f862aeab77b036e25e142de13847d31f0342921fb7ae60f; the commands to do that are on this page. If it does not match, do not open it.
mcpb · gitlab-mcp-server-linux.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
d47b1be9a37bd5d76f862aeab77b036e25e142de13847d31f0342921fb7ae60f
macOS / Linux
echo "d47b1be9a37bd5d76f862aeab77b036e25e142de13847d31f0342921fb7ae60f gitlab-mcp-server-linux.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\gitlab-mcp-server-linux.mcpb).Hash -eq "d47b1be9a37bd5d76f862aeab77b036e25e142de13847d31f0342921fb7ae60f"
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 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 MCPB bundle (https://github.com/jmrplens/gitlab-mcp-server/releases/download/v3.3.0/gitlab-mcp-server-linux.mcpb). Its publisher has verified ownership with us.
Is the GitLab MCP Server server safe to use?
GitLab MCP Server scores 58 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 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.
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.