Which integrations are available for this server?

Provides tools for interacting with GitLab's REST API, enabling AI agents to manage projects, merge requests, issues, global search, and more across GitLab instances, data centers, and cloud.

How do I use md-gitlab-mcp?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@md-gitlab-mcp create a merge request from branch 'feature' to 'main' with title 'Add login'" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

md-gitlab-mcp

by DrBoria

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

md-gitlab-mcp 🦊

A fully-featured GitLab MCP Server tailored to behave like the GitHub MCP but specifically engineered for GitLab Data Centers, Instances, and Cloud.

md-gitlab-mcp is a Model Context Protocol (MCP) server written in TypeScript. It gives AI agents the powerful ability to interact deeply with GitLab via the REST API. This goes far beyond basic issue tracking and provides 25 advanced capabilities, identically structured to the famous GitHub MCP tools.

Features

This server exports an extensive list of tools allowing AI agents to:

Repositories: Search projects, create projects, get file contents, and importantly, push multi-file commits correctly using branching.
Merge Requests (PR Equivalents): Create MRs, approve MRs, list files changed globally, merge them, check CI/CD pipeline status, rebase, and comprehensively read notes/comments.
Issues: Create, list, search, update, and comment on issues seamlessly.
Search: Access Global Search to easily find issues, users, and code snippets across your entire GitLab instance.

Related MCP server: GitLab MCP Server

Why this exists?

The default @modelcontextprotocol/server-gitlab provides very limited tools (around 9 commands) and completely lacks operations regarding code review, reading pull request/merge request threads, or resolving discussions.

md-gitlab-mcp bridges this gap, adopting GitHub's best-practice MCP schema standards and flawlessly translating semantics (projects -> repos, merge requests -> pull requests internally but honoring GitLab's API structure) while delivering complete access to GitLab's API.

Usage

Agents powered by this MCP will see properly annotated tools with parameter descriptions via zod-to-json-schema, meaning the AI inherently knows exactly how to query your repositories without hallucination.

Quick Start (Roo Code / Cline)

You can directly add this to your mcp_settings.json:

{
  "mcpServers": {
    "gitlab": {
      "command": "node",
      "args": [
        "/path/to/md-gitlab-mcp/build/index.js"
      ],
      "env": {
        "GITLAB_API_URL": "https://gitlab.example.dev/api/v4",
        "GITLAB_PERSONAL_ACCESS_TOKEN": "your-access-token"
      }
    }
  }
}

Connecting with the Author

This tool is handcrafted and maintained by Mikita Dusmikeev. Check out my work and connect on social media:

🌍 Website: md-code.space
💻 GitHub: github.com/DrBoria
🛒 VS Code Marketplace: drboria Extensions
👔 LinkedIn: Mikita Dusmikeev
📸 Instagram: @mdcode.official
📱 TikTok: @mdcode.official

Created in 2026. Code like there's no tomorrow.

Available Tools

27 tools

add_issue_commentB

Add a comment to an existing issue

Inputs: body (required), repo (required), owner (required), issueIid (required).

create_branchB

Create a new branch in a GitLab repository

Inputs: repo (required), owner (required), branch (required), fromBranch.

create_issueB

Create a new issue in a GitLab repository

Inputs: repo (required), owner (required), title (required), body, +3 more.

create_merge_requestB

Create a new merge request in a GitLab repository

Inputs: base (required), head (required), repo (required), owner (required), +3 more.

create_merge_request_reviewC

Create a review/approval on a merge request

Inputs: body (required), repo (required), event (required), owner (required), +1 more.

create_repositoryA

Create a new GitLab project in your namespace

Inputs: name (required), autoInit, isPrivate, description.

fork_repositoryA

Fork a GitLab project to your account or specified namespace

Inputs: repo (required), owner (required), organization.

get_file_contentsC

Get the contents of a file or directory from a GitLab repository

Inputs: path (required), repo (required), owner (required), branch.

get_issueA

Get details of a specific issue in a GitLab repository

Inputs: repo (required), owner (required), issueIid (required).

get_merge_requestC

Get details of a specific merge request

Inputs: repo (required), owner (required), mergeRequestIid (required).

get_merge_request_by_urlA

Fetch merge request details using a full URL

Inputs: url (required).

get_merge_request_commentsB

Get the review comments/notes on a merge request

Inputs: repo (required), owner (required), mergeRequestIid (required).

get_merge_request_comments_by_urlA

Fetch merge request comments using a full URL

Inputs: url (required).

get_merge_request_filesA

Get the list of files changed in a merge request

Inputs: repo (required), owner (required), mergeRequestIid (required).

get_merge_request_reviewsB

Get the reviews/approvals on a merge request

Inputs: repo (required), owner (required), mergeRequestIid (required).

get_merge_request_statusA

Get the combined status of all status checks (pipelines) for a merge request

Inputs: repo (required), owner (required), mergeRequestIid (required).

list_commitsA

Get list of commits of a branch in a GitLab repository

Inputs: repo (required), owner (required), sha, page, +1 more.

list_issuesB

List issues in a GitLab repository with filtering options

Inputs: repo (required), owner (required), page, state, +2 more.

list_merge_requestsC

List and filter repository merge requests

Inputs: repo (required), owner (required), page, state, +1 more.

merge_merge_requestC

Merge a merge request

Inputs: repo (required), owner (required), mergeRequestIid (required), commitMessage.

push_filesB

Push multiple files to a GitLab repository in a single commit

Inputs: repo (required), files (required), owner (required), branch (required), +1 more.

search_codeC

Search for code across GitLab repositories

Inputs: q (required), page, perPage.

search_issuesA

Search for issues and merge requests across GitLab repositories

Inputs: q (required), page, perPage.

search_repositoriesC

Search for GitLab projects

Inputs: query (required), page, perPage.

search_usersB

Search for users on GitLab

Inputs: q (required), page, perPage.

update_issueC

Update an existing issue in a GitLab repository

Inputs: repo (required), owner (required), issueIid (required), body, +3 more.

update_merge_request_branchA

Update a merge request branch with the latest changes from the target branch (rebase)

Inputs: repo (required), owner (required), mergeRequestIid (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

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.3/5.0

Scored 2026-08-30 11:15 across 27 tools

Disambiguation4/5

Most tools target a distinct resource/action, and search/create/get/list are clearly separated. The main ambiguity is among the many merge request tools, especially get_merge_request_comments vs get_merge_request_reviews and their by_url variants, though the descriptions do help.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern: search_, create_, get_, list_, update_, add_, merge_, push_, fork_. Minor quirks like merge_merge_request are still predictable.

Tool Count2/5

With 27 tools the set is above the threshold for a focused MCP server. The merge request surface alone accounts for over a dozen tools, making the overall tool count feel heavy and harder for an agent to navigate.

Completeness4/5

Core GitLab workflows are covered: repository searching/creation, file pushes, issues with comments, and a thorough merge request lifecycle including reviews, status, and rebase. Missing operations like updating MR metadata or deleting repositories are minor gaps that agents can often work around.

Resources

Related MCP Connectors

GitLab MCP ServerA
io.github.jmrplens
Go MCP server for GitLab: 2 dynamic tools reach 1000+ REST/GraphQL actions. Free/CE, no paid tier.
CI/CD & DevOps Developer Tools Version Control
2149
https://mcp.jmrp.io/gitlab
GitlabB
io.github.pipeworx-io
GitLab MCP — wraps the GitLab REST API v4 (BYO API key)
Version Control CI/CD & DevOps Developer Tools
492
https://gateway.pipeworx.io/gitlab/mcp
neverinfamous-memory-journal-mcp
ai.smithery
A MCP server built for developers enabling Git based project management with project and personal…
Version Control Developer Tools Project Management
321
https://server.smithery.ai/@neverinfamous/memory-journal-mcp/mcp
Gitlab PublicA
io.github.pipeworx-io
GitLab Public MCP — wraps the GitLab REST API v4 (public endpoints, no auth)
Version Control CI/CD & DevOps Developer Tools
4721
https://gateway.pipeworx.io/gitlab-public/mcp

Related MCP Servers

GitLab MCP Server
Version Control Developer Tools
harshmaur
A
license
C
quality
D
maintenance
An MCP server that enables communication with GitLab repositories, allowing interaction with GitLab's API to manage projects, issues, and repositories through natural language.
Updated a year ago (2025-06-05 11:51 UTC)
45
170,164 npm
1
MIT
GitLab MCP Server
Version Control CI/CD & DevOps Project Management
martijndormans
A
license
Not graded
quality
D
maintenance
An MCP server for the GitLab API that enables comprehensive project management, file operations, and issue tracking. It supports automated branch creation, batch file pushes, and interaction with merge requests and CI/CD logs.
Updated a year ago (2025-06-19 20:10 UTC)
MIT
gitlab-mcp
Version Control CI/CD & DevOps Developer Tools
EllGree
A
license
Not graded
quality
C
maintenance
MCP server for interacting with GitLab API, supporting both self-hosted instances and gitlab.com. Provides tools for managing issues, merge requests, code review, pipelines, milestones, releases, search, and file access.
Updated 7 days ago (2026-11-06 10:13 UTC)
1,908 npm
MIT
mcp-gitlab
Version Control CI/CD & DevOps Developer Tools
vish288
A
license
Not graded
quality
B
maintenance
MCP server for the GitLab REST API providing tools to manage projects, merge requests, pipelines, CI/CD variables, approvals, issues, and code reviews.
Updated 4 days ago (2026-11-10 01:27 UTC)
6,421 PyPI
7
MIT

md-gitlab-mcp 🦊

Features

Why this exists?

Usage

Quick Start (Roo Code / Cline)

Connecting with the Author

Available Tools

Tool Schema Changelog

TDQS

Resources

Related MCP Connectors

Related MCP Servers

GitLab MCP Server

GitLab MCP Server

gitlab-mcp

mcp-gitlab