Gitlab CI MCP Server

What the code does

We read the source, 20 h ago · rules 3dff92dd89df

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.

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 -- uvx gitlab-ci-mcp

{
  "mcpServers": {
    "gitlab-ci-mcp": {
      "args": [
        "gitlab-ci-mcp"
      ],
      "command": "uvx"
    }
  }
}

[mcp_servers.gitlab-ci-mcp]
command = "uvx"
args = ["gitlab-ci-mcp"]

{
  "mcpServers": {
    "gitlab-ci-mcp": {
      "args": [
        "gitlab-ci-mcp"
      ],
      "command": "uvx"
    }
  }
}

{
  "mcpServers": {
    "gitlab-ci-mcp": {
      "args": [
        "gitlab-ci-mcp"
      ],
      "command": "uvx"
    }
  }
}

This one needs environment variables set before it will start: GITLAB_URL (GitLab instance URL (e.g. https://gitlab.com or https://gitlab.example.com)), GITLAB_TOKEN (GitLab Personal Access Token with 'api' scope), 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.). The author declared them in the registry entry; get the values from the project itself.