MCP Gitlab runs on your own machine — the client starts it, so there is no endpoint to ping. 4 803 installs a week from pypi. Last commit 23 Oct 2026.
GitLab MCP server (MCP 2026-07-28): projects, MRs, pipelines, CI/CD, issues; writes or read-only
Today is the operative word: we check MCP Gitlab every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
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 mcp-gitlab -e 'GITLAB_URL=<GITLAB_URL>' -- uvx mcp-gitlab
{
"mcpServers": {
"mcp-gitlab": {
"command": "uvx",
"args": [
"mcp-gitlab"
],
"env": {
"GITLAB_URL": "<GITLAB_URL>"
}
}
}
}
[mcp_servers.mcp-gitlab]
command = "uvx"
args = ["mcp-gitlab"]
env = { GITLAB_URL = "<GITLAB_URL>" }
{
"mcpServers": {
"mcp-gitlab": {
"command": "uvx",
"args": [
"mcp-gitlab"
],
"env": {
"GITLAB_URL": "<GITLAB_URL>"
}
}
}
}
{
"servers": {
"mcp-gitlab": {
"type": "stdio",
"command": "uvx",
"args": [
"mcp-gitlab"
],
"env": {
"GITLAB_URL": "<GITLAB_URL>"
}
}
}
}
Put your own value in place of
<GITLAB_URL> (GitLab instance URL (e.g. https://gitlab.com)).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
GITLAB_TOKEN (GitLab personal access token (token mode). Optional after `mcp-gitlab auth login`; also accepts GITLAB_PAT, GITLAB_PERSONAL_ACCESS_TOKEN, GITLAB_API_TOKEN), GITLAB_READ_ONLY (Alias for MCP_READ_ONLY. Any value other than false/0/no/off/empty locks the server read-only; --read-only can only raise the lock), MCP_READ_ONLY (Locks the server read-only: write tools and write-workflow prompts are not listed and nothing lifts the lock at runtime. Shared name across the mcp-* servers; set it in the deployer's env), GITLAB_AUTH (Authentication mode: token (default) or oauth (OAuth 2.1 proxy; streamable-http only)), GITLAB_OAUTH_CLIENT_ID (Application ID of the GitLab OAuth app (oauth mode, or local sign-in on a self-managed instance)), GITLAB_OAUTH_CLIENT_SECRET (Secret of the GitLab OAuth app (oauth mode)), GITLAB_OAUTH_BASE_URL (Public URL of this server, no trailing slash (oauth mode); redirect URI is <base>/auth/callback), GITLAB_OAUTH_SCOPES (Space-separated GitLab scopes required on every request (oauth mode; default api)), GITLAB_OAUTH_JWT_KEY (FastMCP JWT signing key, >=32 random chars (oauth mode; defaults to one derived from the client secret)), GITLAB_HTTP_BEARER_TOKEN (Bearer token (min 16 chars) required to bind an HTTP transport to a non-loopback host; clients send it as 'Authorization: Bearer <token>' (token mode; --auth oauth has its own sign-in)).
Secure MCP server for GitLab projects, merge requests, issues, and pipelines
GitLab MCP server for projects, merge requests, issues, pipelines, wiki, releases, and more.
Argo CD MCP server (MCP 2026-07-28): status, sync, rollback, drift, AppSets; writes or read-only
Coda MCP server (MCP 2026-07-28): docs, pages, tables, rows, automations; writes or read-only
Jira/Confluence MCP server (MCP 2026-07-28): sprints, boards, attachments; writes or read-only
MCP server for the GitHub REST API: issues, PRs, repos; read always on, write env-gated.
GitLab CI/CD MCP — pipelines, jobs, schedules, MRs, files. Any GitLab (SaaS or self-hosted).
Governed self-managed GitLab + Gitea CI/CD ops: pipelines, runners, artifacts, RCA. 28 tools.
Answers built from our own checks of this server.