# GitLab MCP Server (mcpb · gitlab-mcp-server-linux.mcpb)

Go MCP server for GitLab: 2 dynamic tools reach ~876 actions on Free/CE, up to ~1103 on Ultimate.

- Trust score: 58/100 (low)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: yes
- Last scored: 2026-10-24

## Components

- remote · `mcp.jmrp.io`: 39/100, [markdown](https://verifymcp.io/servers/jmrplens-gitlab-mcp-server/gitlab.md), [page](https://verifymcp.io/servers/jmrplens-gitlab-mcp-server/gitlab)
- mcpb · `gitlab-mcp-server-darwin.mcpb`: 20/100, [markdown](https://verifymcp.io/servers/jmrplens-gitlab-mcp-server/gitlab-mcp-server-darwin.md), [page](https://verifymcp.io/servers/jmrplens-gitlab-mcp-server/gitlab-mcp-server-darwin)
- mcpb · `gitlab-mcp-server-linux.mcpb`: 58/100 (this document), [markdown](https://verifymcp.io/servers/jmrplens-gitlab-mcp-server/gitlab-mcp-server-linux.md), [page](https://verifymcp.io/servers/jmrplens-gitlab-mcp-server/gitlab-mcp-server-linux)
- mcpb · `gitlab-mcp-server-windows.mcpb`: 20/100, [markdown](https://verifymcp.io/servers/jmrplens-gitlab-mcp-server/gitlab-mcp-server-windows.md), [page](https://verifymcp.io/servers/jmrplens-gitlab-mcp-server/gitlab-mcp-server-windows)
- npm · `@jmrp.io/gitlab-mcp-server`: 93/100, [markdown](https://verifymcp.io/servers/jmrplens-gitlab-mcp-server/jmrp-io-gitlab-mcp-server.md), [page](https://verifymcp.io/servers/jmrplens-gitlab-mcp-server/jmrp-io-gitlab-mcp-server)
- nuget · `gitlab-mcp-server`: 93/100, [markdown](https://verifymcp.io/servers/jmrplens-gitlab-mcp-server/gitlab-mcp-server.md), [page](https://verifymcp.io/servers/jmrplens-gitlab-mcp-server/gitlab-mcp-server)
- oci · `docker.io/jmrplens/gitlab-mcp-server`: 66/100, [markdown](https://verifymcp.io/servers/jmrplens-gitlab-mcp-server/docker-io-jmrplens-gitlab-mcp-server.md), [page](https://verifymcp.io/servers/jmrplens-gitlab-mcp-server/docker-io-jmrplens-gitlab-mcp-server)
- oci · `ghcr.io/jmrplens/gitlab-mcp-server`: 66/100, [markdown](https://verifymcp.io/servers/jmrplens-gitlab-mcp-server/ghcr-io-jmrplens-gitlab-mcp-server.md), [page](https://verifymcp.io/servers/jmrplens-gitlab-mcp-server/ghcr-io-jmrplens-gitlab-mcp-server)
- pypi · `jmrplens-gitlab-mcp-server`: 50/100, [markdown](https://verifymcp.io/servers/jmrplens-gitlab-mcp-server/jmrplens-gitlab-mcp-server.md), [page](https://verifymcp.io/servers/jmrplens-gitlab-mcp-server/jmrplens-gitlab-mcp-server)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/jmrplens/gitlab-mcp-server/releases/download/v3.3.0/gitlab-mcp-server-linux.mcpb`
- Version: `3.3.0`
- Transport: `stdio`
- SHA-256: `d47b1be9a37bd5d76f862aeab77b036e25e142de13847d31f0342921fb7ae60f`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-24.

- **Supply Chain Security**: 0/100
  - 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.
  - 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).
  - Install-script risk not yet assessed.
  - 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).
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to jmrplens/gitlab-mcp-server).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 85/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**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.

## Install

### 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.

- Download bundle: `https://github.com/jmrplens/gitlab-mcp-server/releases/download/v3.3.0/gitlab-mcp-server-linux.mcpb`
- SHA-256: `d47b1be9a37bd5d76f862aeab77b036e25e142de13847d31f0342921fb7ae60f`

### Verify on macOS / Linux

```bash
echo "d47b1be9a37bd5d76f862aeab77b036e25e142de13847d31f0342921fb7ae60f  gitlab-mcp-server-linux.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\gitlab-mcp-server-linux.mcpb).Hash -eq "d47b1be9a37bd5d76f862aeab77b036e25e142de13847d31f0342921fb7ae60f"
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-23 (score 58, +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.

### 2026-10-22 (score 57, +2)

- [functional improvement] Maintenance: unverified → pass

### 2026-10-20 (score 55, +2)

- [functional regression] Maintenance: pass → unverified
- [functional improvement] Stability: unverified → 0.20
- [functional] Package version: 3.2.0 → 3.3.0

### 2026-10-14 (score 53, +33)

- [security improvement] 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).
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] 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

### 2026-10-11 (score 20)

First indexed and scored.

## MCP tools (2)

### `gitlab_execute_action` (~158 tokens)

GitLab Execute Action

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"}}

Input parameters:

- `action` (string, required): 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, required): Required action-specific parameters object validated by the selected action schema. Use an empty object for actions with no parameters.

Output parameters:

- `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…

### `gitlab_find_action` (~166 tokens)

GitLab Find Action

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"}

Input parameters:

- `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, required): 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…

Output parameters:

- `count` (integer): Number of returned matches.
- `query` (string): Original search query.
- `results` (null|array): Matching GitLab catalog actions with schemas and execute examples.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/jmrplens-gitlab-mcp-server/gitlab-mcp-server-linux#diagnostics

## Score history

- 2026-10-24: 58
- 2026-10-23: 58
- 2026-10-22: 57
- 2026-10-21: 55
- 2026-10-20: 55
- 2026-10-19: 53
- 2026-10-18: 53
- 2026-10-17: 53
- 2026-10-16: 53
- 2026-10-15: 53
- 2026-10-14: 53
- 2026-10-13: 20
- 2026-10-12: 20
- 2026-10-11: 20

## Common questions

### 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.

## Links

- Repository: https://github.com/jmrplens/gitlab-mcp-server
- Website: https://docs.jmrp.io/gitlab-mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/jmrplens-gitlab-mcp-server/gitlab-mcp-server-linux.xml
- Changelog JSON feed: https://verifymcp.io/servers/jmrplens-gitlab-mcp-server/gitlab-mcp-server-linux.json
- HTML version of this page: https://verifymcp.io/servers/jmrplens-gitlab-mcp-server/gitlab-mcp-server-linux