Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/CobolJunkie/gitlab-mcpInstalling this writes the configuration, not the program: `node` runs a file from the repository, so clone it first and make the path in the command match where you put it.
Wrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/coboljunkie/gitlab-mcp/gitlab)<a href="https://agentmods.dev/mcp/coboljunkie/gitlab-mcp/gitlab"><img src="https://agentmods.dev/badge/mcp/coboljunkie/gitlab-mcp/gitlab/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/coboljunkie/gitlab-mcp/gitlab"><img src="https://agentmods.dev/badge/mcp/coboljunkie/gitlab-mcp/gitlab.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
gitlab scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"gitlab": {
"command": "node",
"args": [
"--import",
"${PLUGIN_ROOT}/adapters/codex/preload.mjs",
"${PLUGIN_ROOT}/server/dist/gitlab-mcp.cjs",
"--stdio"
]
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 11 lines scan A df4344d38153
gitlab is an MCP server published in the GitHub repository CobolJunkie/gitlab-mcp (0 stars, last pushed 18d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
gitlab-mcp
GitLab MCP server for projects, merge requests, issues, pipelines, wiki, releases, and more. Runs locally from the @zereight/mcp-gitlab npm package. Needs 14 environment variables to run.
gitlab-mcp-server
MCP server "gitlab-mcp-server" as configured in jmrplens/gitlab-mcp-server. Launched with https://github.com/jmrplens/gitlab-mcp-server/releases/download/v3.0.0/gitlab-mc. Needs 17 environment variables to run.
mcp-gitlab
GitLab MCP server for the MCP 2026-07-28 specification (MCP 2.0): manage projects, MRs, pipelines, CI/CD, approvals, and issues for AI assistants. Runs locally from the mcp-gitlab Python package. Needs 3 environment variables to run.
cicd-aiops
Governed AI-ops for self-managed GitLab + Gitea CI/CD: pipelines, jobs, runners, artifacts, repo hygiene, flagship RCA analyses (pipeline failures, runner health, storage bloat, stale work), and governed writes (retry/cancel, pause/resume, artifact deletion, branch protection) with a built-in governance harness…
gitlab
GitLab MCP — wraps the GitLab REST API v4 (BYO API key). Remote server at gateway.pipeworx.io.
gitlab-ci-mcp
MCP server for self-hosted GitLab — pipelines, schedules, branches, merge requests and repository files. Runs locally from the gitlab-ci-mcp Python package. Needs 4 environment variables to run.