https://github.com/owayo/gitlab-mcp-server

by owayo

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

Related Servers

Alternatives to https://github.com/owayo/gitlab-mcp-server

No user-submitted related servers found.

Related Servers

qodev-gitlab-mcp
Version Control CI/CD & DevOps
qodevai
A
license
Not graded
quality
D
maintenance
A Model Context Protocol server for GitLab integration, enabling AI assistants to manage projects, merge requests, pipelines, issues, releases, and more.
Updated 6 months ago (2026-04-02 21:19 UTC)
MIT
GitLab MCP Server
Version Control Developer Tools
ZephyrDeng
-
license
Not graded
quality
Not graded
maintenance
A Model Context Protocol server that enables AI assistants to interact with GitLab repositories, allowing tasks like managing merge requests, searching projects, and creating comments through RESTful API integration.
Updated a year ago (2025-04-02 10:34 UTC)
7 npm
2
-
gitlab-mcp
Version Control CI/CD & DevOps Developer Tools
LeonRLewis
F
license
A
quality
D
maintenance
MCP server for GitLab that enables AI assistants to manage CI pipelines, job logs, repositories, branches, merge requests, and commits via the GitLab REST API.
Updated 3 months ago (2026-06-30 21:52 UTC)
20
-
GitLab MCP Server
Version Control CI/CD & DevOps Developer Tools
snowild
A
license
B
quality
D
maintenance
A Model Context Protocol server that enables AI assistants to interact with self-hosted GitLab instances through 30 specialized tools. It supports managing projects, merge requests, CI/CD pipelines, and repository operations via the GitLab REST API v4.
Updated 6 months ago (2026-03-18 03:32 UTC)
30
MIT
GitLab MCP Server
Version Control CI/CD & DevOps
alesdrobysh
A
license
Not graded
quality
D
maintenance
A Model Context Protocol (MCP) server for GitLab integration, written in TypeScript. This server allows you to interact with GitLab merge requests, commits, pipelines, and jobs through MCP tools.
Updated 6 months ago (2026-03-18 11:37 UTC)
11 npm
ISC
mcp-gitlab-jira
Version Control Project Management
HainanZhao
A
license
B
quality
C
maintenance
A Model Context Protocol (MCP) server for GitLab and Jira integration. This server allows AI agents like gemini-cli to interact with your GitLab and Jira instances.
Updated a year ago (2025-09-05 03:49 UTC)
32
6 npm
11
MIT

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.1/5.0

Scored 2026-04-18 11:15 across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: get_pipeline_failed_jobs targets pipeline failures, get_review_changes targets MR file diffs, and get_review_comments targets MR unresolved comments. There is no overlap in functionality or ambiguity between these three tools.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with 'get_' prefix and snake_case formatting (get_pipeline_failed_jobs, get_review_changes, get_review_comments). The naming convention is perfectly uniform across all tools.

Tool Count2/5

With only 3 tools, this server feels severely under-scoped for a GitLab integration. While the tools are coherent, a typical GitLab MCP server would need many more operations (e.g., list projects, create MRs, trigger pipelines) to be useful. The count is too low for the apparent domain.

Completeness2/5

The tool surface is extremely incomplete for GitLab operations. It only provides three specific 'get' operations for pipelines and MRs, missing all CRUD/lifecycle coverage (no create, update, delete, or listing operations). Agents will encounter dead ends when trying to perform basic GitLab workflows.