Gitlab-ci-mcp Server

GitLab CI/CD MCP — pipelines, jobs, schedules, MRs, files. Any GitLab (SaaS or self-hosted).

Local serverstdio

What is the Gitlab-ci-mcp Server?

Gitlab-ci-mcp is an MCP integration. GitLab CI/CD MCP — pipelines, jobs, schedules, MRs, files. Any GitLab (SaaS or self-hosted).

Packages and local setup

The published pypi package is gitlab-ci-mcp, version 0.5.1. Its declared MCP transport is stdio.

The package declares GITLAB_URL (required): GitLab instance URL (e.g. https://gitlab.com or https://gitlab.example.com); GITLAB_TOKEN (required): 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..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 0.5.1 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related developer tools MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
GITLAB_URLGitLab instance URL (e.g. https://gitlab.com or https://gitlab.example.com)Yes
GITLAB_TOKENGitLab Personal Access Token with 'api' scopeYes
GITLAB_PROJECT_PATHDefault project path (e.g. my-org/my-repo); can be overridden per callOptional
GITLAB_SSL_VERIFYVerify SSL certificates (true/false). Set to 'false' for self-hosted GitLab with self-signed certs.Optional