MCP.Market

Gitlab Ci MCP server

by mshegolev·io.github.mshegolev/gitlab-ci-mcp·v0.5.1·2 stars
No reviews yet

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

B78/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B78/100

full report

Adoption
Growing

2 stars49 downloads/wk

Reviews

Write one

Nobody has reviewed Gitlab Ci yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Gitlab Ci tools (23, 6 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • gitlab_cancel_pipelinewrite action

    Cancel a running pipeline. In-flight jobs will be interrupted.

  • gitlab_compare_branches

    Compare two branches — returns up to 30 commits and the list of changed files.

  • gitlab_create_merge_requestwrite action

    Create a merge request from ``source_branch`` into ``target_branch``.

  • gitlab_create_schedulewrite action

    Create a new CI/CD schedule with the given cron and variables.

  • gitlab_delete_schedulewrite action

    Delete a schedule by ID. Cannot be undone.

  • gitlab_get_file

    Read a text file from the repository, truncated to 500 lines.

  • gitlab_get_job_log

    Fetch the trace/log of a job, with optional regex filter.

  • gitlab_get_merge_request

    Get full information about a merge request by internal ID (``iid``).

  • gitlab_get_merge_request_changes

    List changed files in a merge request with truncated diffs (2KB per file).

  • gitlab_get_pipeline

    Get a single pipeline with full timing details.

  • gitlab_get_pipeline_jobs

    List jobs of a pipeline with stage, status, duration and web URL.

  • gitlab_list_branches

    List branches of a project, optionally filtered by substring.

  • gitlab_list_merge_requests

    List merge requests of a project, optionally filtered by state.

  • gitlab_list_pipelines

    List recent pipelines of a project, newest first.

  • gitlab_list_repository_tree

    List files and directories at a given path in the repository.

  • gitlab_list_schedules

    List all CI/CD schedules of a project.

  • gitlab_list_tags

    List tags of a project, newest first.

  • gitlab_merge_mr

    Perform the actual merge if GitLab reports the MR can be merged.

  • gitlab_pipeline_health

    Aggregate success rate over 7 and 30 days with a trend indicator.

  • gitlab_project_info

    Return basic metadata about a project: ID, default branch, visibility, counts.

  • gitlab_retry_pipeline

    Retry all failed jobs of an existing pipeline.

  • gitlab_trigger_pipelinewrite action

    Create a new pipeline on the given ref, optionally with CI variables.

  • gitlab_update_schedulewrite action

    Update an existing schedule. Only provided fields change.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan18 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 46 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 78/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Gitlab Ci compares

Against every graded Developer tools MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
78/100
higher than 50% of 1,119 Developer tools servers
Tools
23
the typical Developer tools server has 7
Tools that change things
26%
typical: 5%. Fewer write tools means less an agent can break
GitHub stars
2
more than 65% of 854 Developer tools servers
Downloads a week
49
more than 39% of 430 Developer tools servers with a package

What its tools let an agent do: 17 read · 6 change

Install Gitlab Ci in Claude Code, Cursor or VS Code

claude mcp add gitlab-ci-mcp -- uvx gitlab-ci-mcp
Add to Cursor

What the publisher says

From the Gitlab Ci repository's README, as published. We do not edit it. Read it on GitHub

gitlab-ci-mcp

<!-- mcp-name: io.github.mshegolev/gitlab-ci-mcp -->

MCP server for GitLab CI/CD. Lets an LLM agent (Claude Code, Cursor, OpenCode, DevX Agent, etc.) work with pipelines, jobs, schedules, branches, tags, merge requests and repository files.

Python, FastMCP, stdio transport.

Works with any GitLab — SaaS gitlab.com or self-hosted / on-prem. Designed with corporate networks in mind: configurable NO_PROXY handling, optional SSL-verify toggle, per-project scoping via env vars.

Design highlights

  • Tool annotations — every tool carries readOnlyHint / destructiveHint / idempotentHint / openWorldHint so MCP clients can classify operations (e.g. ask for confirmation only on destructive ones like gitlabmergemr, gitlabdeleteschedule).
  • Structured output on every tool — each tool declares a TypedDict return type, so FastMCP auto-generates an outputSchema and every result carries structuredContent alongside a pre-rendered markdown text block. Clients that can render structured data use it; agents that prefer compact text get the markdown. No response_format parameter needed.
  • Structured errors — authentication, 404, 403, 429 (rate-limit), 5xx, missing-env errors are converted to actionable ToolError messages (e.g. "GitLab authentication failed… verify GITLABTOKEN has api scope"_) and surfaced as isError=True results.
  • Pydantic input validation — every argument has typed constraints (ranges, lengths, literals) auto-exposed as JSON Schema.
  • Project scoping per call — every tool accepts an optional projectpath that overrides GITLABPROJECT_PATH for cross-project queries.
  • Pagination — list tools return a pagination block with page, total, hasmore, nextpage and a next-page hint in the markdown footer.
  • MCP Context integration — gitlabpipelinehealth and gitlabgetjoblog are async and emit info logs / reportprogress events through the MCP Context so clients can show progress bars.
  • MCP Resources — gitlab://project/info and gitlab://project/ci-config mirror common lookups for clients that prefer the Resource model over tools.
  • Lifespan management — python-gitlab HTTP sessions are closed cleanly on server shutdown via an asynccontextmanager lifespan hook.
  • Log grep — gitlabgetjoblog accepts greppattern + grep_context (surrounding lines) for regex-filtering megabyte-scale CI logs without pulling the whole trace into agent context.

Threading model

FastMCP automatically runs synchronous tools in a worker thread (anyio.tothread.runsync), so they do not block the asyncio event loop — python-gitlab is a synchronous library and wrapping every call in asyncio.tothread ourselves would be ceremony. Tools that benefit from the MCP Context (progress, info logs) are written as async def and explicitly wrap python-gitlab calls with asyncio.tothread.

Features

23 tools covering the everyday CI/CD surface:

Pipelines gitlablistpipelines · gitlabgetpipeline · gitlabgetpipelinejobs · gitlabgetjoblog · gitlabtriggerpipeline · gitlabretrypipeline · gitlabcancelpipeline · gitlabpipelinehealth

Schedules gitlablistschedules · gitlabcreateschedule · gitlabupdateschedule · gitlabdeleteschedule

Branches & tags gitlablistbranches · gitlablisttags · gitlabcomparebranches

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Gitlab Ci: common questions

Is Gitlab Ci MCP server safe?
Mostly: it is graded B (78/100). Read the Gitlab Ci safety report
How do I install Gitlab Ci?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Gitlab Ci need an API key?
Yes. The registry entry asks for GITLAB_TOKEN.
Is Gitlab Ci maintained?
The last commit was 82 days ago (2026-08-12). The latest release is v0.5.1.
What can I use instead of Gitlab Ci?
Servers from other publishers that do the same job: Gitlab MCP server, GitLab MCP Server and Nora MCP server.
How does Gitlab Ci compare with other Developer tools MCP servers?
safety score 78/100 (higher than 50% of 1,119 Developer tools servers); tools 23 (the typical Developer tools server has 7); tools that change things 26% (typical: 5%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Gitlab Ci

Same job from other publishers: the closest match first, then the best rated.

  • Gitlab
    GitLab MCP server (MCP 2026-07-28): projects, MRs, pipelines, CI/CD, issues; writes or read-only
    B
  • GitLab MCP Server
    GitLab MCP server for projects, merge requests, issues, pipelines, wiki, releases, and more.
    B
  • Nora
    Operate self-hosted OpenClaw and Hermes agent fleets on Docker or Kubernetes from MCP clients.
    B
  • Folio
    Self-hosted Git-backed team wiki: search, read and edit pages, data tables and whiteboards.
    A
  • HomeLab Monitor
    Self-hosted homelab dashboard with a built-in read-only MCP server (hosts, Docker, GPU, services).
    A

More from mshegolev →