What is gitlab-setup?

A command for configuring a GitLab MCP server, which lets an agent connect to GitLab. It checks for a GitLab access token and guides you through setting one up.

Use it to set or check GITLAB_TOKEN, configure a custom GitLab URL, and confirm the connected GitLab account.

It removes the guesswork from connecting the agent to GitLab. It can also verify the connection and handle self-hosted GitLab addresses.

gitlab-setup — Command for Claude Code by wanadev/gitlab-mcp

Install

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.

Clone the repo

git clone --depth 1 https://github.com/wanadev/gitlab-mcp

Made for: Claude Code.

Or install wanadev-gitlab, the plugin that ships this one along with the rest of its 1 command, 1 hook, 1 MCP server.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/wanadev/gitlab-mcp/gitlab-setup/github.svg)](https://agentmods.dev/commands/wanadev/gitlab-mcp/gitlab-setup)

Your own site

<a href="https://agentmods.dev/commands/wanadev/gitlab-mcp/gitlab-setup"><img src="https://agentmods.dev/badge/commands/wanadev/gitlab-mcp/gitlab-setup/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/wanadev/gitlab-mcp/gitlab-setup"><img src="https://agentmods.dev/badge/commands/wanadev/gitlab-mcp/gitlab-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 264 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00018	$0.00264
Opus 5.5	$0.00007	$0.00106
Sonnet 5.5	$0.00004	$0.00053
Haiku 4.5	$0.00002	$0.00026

Measured 2mo ago against content hash 02fe6375a84c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

gitlab-setup 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 2mo 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.

plugins/wanadev-gitlab/commands/gitlab-setup.md · 21 lines

What it actually says

Check if the GITLAB_TOKEN environment variable is set.

If GITLAB_TOKEN is NOT set or empty, guide the user step by step in their language:

Go to GitLab > Settings > Access Tokens
Create a token with the api scope (or read_api for read-only access)
Copy the token
Set it as an environment variable:
- Linux/macOS: add export GITLAB_TOKEN=glpat-xxxx to ~/.bashrc or ~/.zshrc, then run source ~/.bashrc
- Windows: add it via System Properties > Environment Variables, or run setx GITLAB_TOKEN glpat-xxxx
Restart Claude Code with /reload-plugins

Also ask if they need to configure GITLAB_BASE_URL (for self-hosted GitLab instances — default is https://gitlab.com).

If GITLAB_TOKEN IS set, confirm that the connection works by calling the get_current_user tool. Show the user their GitLab identity and confirm everything is working.

Changes

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.

2mo ago First seen · 21 lines · 18 tokens per session scan A 02fe6375a84c

Subscribe to this mod's changes

gitlab-setup is a command published in the GitHub repository wanadev/gitlab-mcp (2 stars, last pushed 5mo ago), licensed MIT. It adds 18 tokens to every session and 264 once invoked, about $0.0001 per session on Opus 5.5. 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.

Git and workflow

gitlab-setup next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
gitlab-setupwanadev/gitlab-mcp	Command	2	5mo ago	MIT	A	18	Claude Code
merge-conflict-analysisrjmurillo/ai-agents	Command	49	yesterday	MIT	A	0	GitHub Copilot
release-notesOpenHands/extensions	Command	179	today	MIT	A	44	Claude Code
repo-audittractorjuice/arc-kit	Command	2.3k	yesterday	none	A	29	Claude Code
commitechoVic/blade-code	Command	181	26d ago	MIT	A	8	Claude Code
propsmill/infrahub-mcp	Command	10	today	Apache-2.0	A	18	Claude Code
codex-reviewoalders/kitchen-sink	Command	5	yesterday	MIT	A	41	Claude Code