Gitlab CI MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 887 installs a week from pypi. Last commit 30 Oct 2026.
GitLab CI/CD MCP — pipelines, jobs, schedules, MRs, files. Any GitLab (SaaS or self-hosted).
What the code does
We read the source, 3 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
ENV GITLAB_TOKEN=""
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add gitlab-ci-mcp -e 'GITLAB_URL=<GITLAB_URL>' -e 'GITLAB_TOKEN=<GITLAB_TOKEN>' -- uvx gitlab-ci-mcp{
"mcpServers": {
"gitlab-ci-mcp": {
"command": "uvx",
"args": [
"gitlab-ci-mcp"
],
"env": {
"GITLAB_TOKEN": "<GITLAB_TOKEN>",
"GITLAB_URL": "<GITLAB_URL>"
}
}
}
}[mcp_servers.gitlab-ci-mcp]
command = "uvx"
args = ["gitlab-ci-mcp"]
env = { GITLAB_URL = "<GITLAB_URL>", GITLAB_TOKEN = "<GITLAB_TOKEN>" }{
"mcpServers": {
"gitlab-ci-mcp": {
"command": "uvx",
"args": [
"gitlab-ci-mcp"
],
"env": {
"GITLAB_TOKEN": "<GITLAB_TOKEN>",
"GITLAB_URL": "<GITLAB_URL>"
}
}
}
}{
"servers": {
"gitlab-ci-mcp": {
"type": "stdio",
"command": "uvx",
"args": [
"gitlab-ci-mcp"
],
"env": {
"GITLAB_TOKEN": "<GITLAB_TOKEN>",
"GITLAB_URL": "<GITLAB_URL>"
}
}
}
}Put your own values in place of
<GITLAB_URL> (GitLab instance URL (e.g. https://gitlab.com or https://gitlab.example.com)), <GITLAB_TOKEN> (GitLab Personal Access Token with 'api' scope).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
GITLAB_PROJECT_PATH (Default project path (e.g. my-org/my-repo); can be overridden per call), GITLAB_SSL_VERIFY (Verify SSL certificates (true/false). Set to 'false' for self-hosted GitLab with self-signed certs).
Alternatives to Gitlab CI MCP
same job, measured the same wayGitLab MCP server (MCP 2026-07-28): projects, MRs, pipelines, CI/CD, issues; writes or read-only
Governed self-managed GitLab + Gitea CI/CD ops: pipelines, runners, artifacts, RCA. 28 tools.
Read-only MCP server for self-hosted Atlassian Bamboo CI/CD
Secure MCP server for GitLab projects, merge requests, issues, and pipelines
CI pipeline monitoring for GitLab and GitHub - no API key.
GitLab MCP server for projects, merge requests, issues, pipelines, wiki, releases, and more.
Read ServiceMonster customers, jobs, orders and schedules, and add customer notes.
Self-hosted MCP server: run OpenAI Codex CLI prompts and manage workspace files.
Gitlab CI MCP — questions
Answers built from our own checks of this server.