Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

GitLab MCP Server

Owner verified

NPM · @JMRP.IO/GITLAB-MCP-SERVER · 6 COMPONENTS · SCANNED SEP 14

Go MCP server for GitLab: 2 dynamic tools reach 1000+ REST/GraphQL actions. Free/CE, no paid tier.

Available components

remote · mcp.jmrp.io 39 mcpb · gitlab-mcp-server.mcpb 14 npm · @jmrp.io/gitlab-mcp-server 50 nuget · gitlab-mcp-server 40 oci · ghcr.io/jmrplens/gitlab-mcp-server:3.0.0@sha256:80990c658d2ac1b95c98540fbd8fc2bcf300a86a9b18c73483ed7412441b2c04 10 pypi · jmrplens-gitlab-mcp-server 21
50 Trust /100
Trust breakdown (7 categories)

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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 0 of 6 dependencies flagged as unhealthy. View diagnostics → Pass
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 Usability0
  • Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

How do I install the GitLab MCP Server server?

GitLab MCP Server runs locally as an npm package, launched with npx -y @jmrp.io/gitlab-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @jmrp.io/gitlab-mcp-server

# add to Claude Code
claude mcp add jmrplens-gitlab-mcp-server -- npx -y @jmrp.io/gitlab-mcp-server
// .cursor/mcp.json
{
  "mcpServers": {
    "jmrplens-gitlab-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@jmrp.io/gitlab-mcp-server"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "jmrplens-gitlab-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@jmrp.io/gitlab-mcp-server"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add jmrplens-gitlab-mcp-server -- npx -y @jmrp.io/gitlab-mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "jmrplens-gitlab-mcp-server": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@jmrp.io/gitlab-mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add jmrplens-gitlab-mcp-server --command npx --arg -y --arg @jmrp.io/gitlab-mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  jmrplens-gitlab-mcp-server:
    command: "npx"
    args: ["-y", "@jmrp.io/gitlab-mcp-server"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "jmrplens-gitlab-mcp-server": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@jmrp.io/gitlab-mcp-server"
      ]
    }
  }
}
# add to Vellum
assistant mcp add jmrplens-gitlab-mcp-server -t stdio -c npx -a -y @jmrp.io/gitlab-mcp-server
// mcp.json
{
  "mcpServers": {
    "jmrplens-gitlab-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@jmrp.io/gitlab-mcp-server"
      ]
    }
  }
}
Changelog

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.

  • 10 Sept 26 50

    First indexed and scored.

Diagnostics

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 14 Sept 2026 · Analysed npm/@jmrp.io/gitlab-mcp-server@3.0.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 npm
Reason Verified
Discovered via Registry attestation endpoint
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.0.0
Rekor log index 2779582660
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:23040d761e7cadbc9a5a365c4a0198566d85f4a2538833b1786d9227754b9deeba1eabaa252aa5e7924b412db51659b5a5af91de1fa7c6e1b321c103f

Background: How many MCP packages publish verified provenance →

Dependencies 6 packages
Packages resolved 6
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools

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 →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

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 1000+ REST/GraphQL actions. Free/CE, no paid tier. This page covers its npm package (@jmrp.io/gitlab-mcp-server). Its publisher has verified ownership with us.

Is the GitLab MCP Server server safe to use?

GitLab MCP Server scores 50 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 14 September 2026. It declares no install or post-install scripts. 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.

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 14 September 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.