Enterprise DNAEnterprise DNA

MCP Servers

jmrplens/gitlab-mcp-server

Open source GitLab MCP server for AI assistants: 2-tool dynamic find/execute over 870+ GitLab actions (1,000+ Enterprise), stdio/HTTP/OAuth, safe/read-only modes.

Our verdict

Not reviewed yet

We have not reviewed jmrplens/gitlab-mcp-server yet

No one at Enterprise DNA has checked this listing against its sources. The description comes from public listings gathered automatically. Any fact below shows where it came from and when it was last checked.

How we review records

From the listing

About jmrplens/gitlab-mcp-server

An open source GitLab MCP server that lets AI assistants interact with GitLab via two tools: dynamic find and execute. It covers over 870 GitLab actions (1,000+ for Enterprise) and supports stdio, HTTP, and OAuth transports with safe/read-only modes.

Best for

Developers who want to give AI assistants direct GitLab access with safety controls

Use cases

  • Automate GitLab project management tasks through an AI assistant
  • Search, create, or update merge requests programmatically
  • Integrate AI with GitLab for read-only auditing of projects

Notes

8 stars on GitHub. Last updated 2026-06-01. Licensed MIT.

Pros

  • Open source and written in Go for easy deployment
  • Supports a large number of GitLab actions out of the box
  • Includes safe and read-only modes for risk reduction

Cons

  • Limited to only two tools (find and execute) for all operations
  • Requires GitLab administrator access to set up OAuth
  • May have a learning curve for configuring transports and permissions

Key facts

What we have checked

Days since the last commit
0
Checked GitHub
GitHub forks
10
Checked GitHub
GitHub stars
47
Checked GitHub
Open issues
88
Checked GitHub
Releases in the last 90 days
15
Checked GitHub

Each value shows when we last confirmed it and where it came from. Values we have not confirmed are left out, never guessed.

How to use

How to set it up

As the listing publishes it. We have not run this install.

Install

npx -y @jmrp.io/gitlab-mcp-server

Tools exposed

  • docker
  • claude mcp add
  • brew
  • curl
  • powershell

Clients the listing names (not checked here)

Claude Desktop, Claude Code, Cursor, VS Code

Example client config

{
  "mcpServers": {
    "gitlab": {
      "command": "/path/to/gitlab-mcp-server",
      "env": {
        "GITLAB_TOKEN": "glpat-xxxxxxxxxxxxxxxxxxxx"
      }
    }
  }
}

Install

Add jmrplens/gitlab-mcp-server to your client

Not verified yet

Our lab has not run this server yet. "Config checked" on a client means the recipe matches that client's documented config format; it does not mean we ran it.

Claude Code

Config checked

Run in your terminal (remote server)

claude mcp add --transport http jmrplens-gitlab-mcp-server https://mcp.jmrp.io/gitlab

Version 3.3.0 · From the Official MCP registry, read · Format checked against Claude Code's config docs

Claude Desktop

Config checked

Add to claude_desktop_config.json (runs on your computer)

{
  "mcpServers": {
    "jmrplens-gitlab-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@jmrp.io/gitlab-mcp-server@3.3.0"
      ],
      "env": {
        "GITLAB_TOKEN": "YOUR_GITLAB_TOKEN"
      }
    }
  }
}

Needs GITLAB_TOKEN: replace each YOUR_ value with your own.

Version 3.3.0 · From the Official MCP registry, read · Format checked against Claude Desktop's config docs

Cursor

Config checked

Add to .cursor/mcp.json (remote server)

{
  "mcpServers": {
    "jmrplens-gitlab-mcp-server": {
      "url": "https://mcp.jmrp.io/gitlab"
    }
  }
}

Version 3.3.0 · From the Official MCP registry, read · Format checked against Cursor's config docs

VS Code

Config checked

Add to .vscode/mcp.json (remote server)

{
  "servers": {
    "jmrplens-gitlab-mcp-server": {
      "type": "http",
      "url": "https://mcp.jmrp.io/gitlab"
    }
  }
}

Version 3.3.0 · From the Official MCP registry, read · Format checked against VS Code's config docs

Codex

Config checked

Add to ~/.codex/config.toml (remote server)

[mcp_servers.jmrplens-gitlab-mcp-server]
url = "https://mcp.jmrp.io/gitlab"

Version 3.3.0 · From the Official MCP registry, read · Format checked against Codex's config docs

ChatGPT

Config checked

Fill in the Add custom MCP server form (remote server)

Where
ChatGPT Plugins > + > Add custom MCP server
Name
GitLab MCP Server
Description
Go MCP server for GitLab: 2 dynamic tools reach ~876 actions on Free/CE, up to ~1103 on Ultimate.
Connection
Public endpoint
MCP server URL
https://mcp.jmrp.io/gitlab

Version 3.3.0 · From the Official MCP registry, read · Format checked against ChatGPT's config docs

Recipes come from the server's entry in the official MCP registry. Check the package name before you run it, and keep keys out of shared files.

Works with

What jmrplens/gitlab-mcp-server connects to

6 clients, each with how we know and when we checked.

Works withTypeHow we knowChecked
Claude CodeClientInstall recipe matches the client's documented formatRemote server, version 3.3.0Config checkedClaude Code docs
Claude DesktopClientInstall recipe matches the client's documented formatRuns locally, version 3.3.0Config checkedClaude Desktop docs
CursorClientInstall recipe matches the client's documented formatRemote server, version 3.3.0Config checkedCursor docs
VS CodeClientInstall recipe matches the client's documented formatRemote server, version 3.3.0Config checkedVS Code docs
CodexClientInstall recipe matches the client's documented formatRemote server, version 3.3.0Config checkedCodex docs
ChatGPTClientInstall recipe matches the client's documented formatRemote server, version 3.3.0Config checkedChatGPT docs

Stars and usage

How jmrplens/gitlab-mcp-server is growing

GitHub stars

45 to 47

stars. 29 Oct 2026 to 10 Nov 2026, 3 readings.

Source: GitHub. Checked .

Health and security

Is jmrplens/gitlab-mcp-server looked after, and what do its setup files show

Health score

56 out of 100

Does someone look after this repository? It does not say the code is good or safe. Worked out from GitHub signals checked . How it is worked out

PartPointsWhat we saw
Recent activity30 of 30Last push 0 days ago
Releases15 of 1515 releases in 90 days
Issue repliesNot countedThe latest check has no issue response reading (fewer than 3 measured issues, or issues switched off)
Maintainer0 of 15Owned by a single user
Official source0 of 20Community server

Security check static checks

100 out of 100

Reads what is published about the server: package advisories, licence, secrets in the documented setup and tool permissions. Nothing is installed or run, so this is not a security assessment. Checked by edna-static-v1 npm:@jmrp.io/gitlab-mcp-server@3.4.0. What it checks

Licence: MIT

  • Note Asks for GITLAB_TOKEN through environment variables.
  • Note The lab has not recorded this server's tool list yet, so tool permissions were not checked.
Tool permissions (1)
  • GITLAB_TOKEN, environment variable it asks for (a secret)

Sources

Where this comes from

  • GitHubRegistry

    Checked · Days since the last commit, GitHub forks, GitHub stars, Open issues, Releases in the last 90 days

A source shows what was published when we checked it. It does not certify security, performance or a working installation. Read our method.

Changelog

What changed

No changes recorded yet. Releases, price changes and deprecations appear here, with their dates, once we track them for this record.

Pairs with

Other entries in the index that connect to this one. Click through to see the chain.

Free 27-page guide

Get the free Developer’s Field Guide

A 27-page field guide to the AI coding workflow with Claude. Claude Code, MCP servers, the prompt patterns that work, and what to delegate. Free.

Enter your work email. We send it straight over, plus a few short notes worth knowing. Unsubscribe any time.

No spam. Unsubscribe any time.