What can you do with this server?

This MCP server provides a GitLab REST API interface for AI agents, enabling management of merge requests, CI/CD pipelines, repositories, and local code review workflows. Discovery * Resolve project_id, current branch, and MR IID from a local repository path (gitlab_resolve_context). * Search for accessible GitLab projects by name or path (gitlab_search_projects). Merge Requests * Get MR metadata — title, state, branches, reviewers, labels, pipeline, approvals, and URL (gitlab_get_merge_request). * Check mergeability, including conflicts, draft status, pipeline results, approvals, and blocking discussions (gitlab_get_mr_merge_status). * Fetch MR diff/changes, optionally with failed CI job logs and discussions (gitlab_get_mr_context). * List review threads, inline comments, and general notes (gitlab_get_mr_discussions). * Post inline review comments on specific diff lines (gitlab_add_mr_inline_comment). * Full MR lifecycle: list, get, create, update, approve/unapprove, comment, merge, close, reopen, mark as draft/ready (gitlab_manage_merge_requests). CI/CD Pipelines * List recent pipelines filtered by branch, MR, or status (gitlab_list_pipelines). * Get pipeline details and job summaries (gitlab_get_pipeline). * Fetch full or truncated logs for a specific CI job (gitlab_get_job_trace). * Control pipelines/jobs: list jobs, play manual jobs, retry a job or pipeline, cancel a pipeline (gitlab_control_pipeline). Repository * Read remote file contents at any branch, tag, or commit SHA (gitlab_get_file). * Compare two refs to get commits and file diffs (gitlab_compare). Local Review * Create a git worktree from a local repo or shallow clone and auto-run dependency installation (e.g., npm ci, composer install) for local code review (gitlab_prepare_review). Read-Only Mode * Set GITLAB_READ_ONLY=true to block all write operations (merge, comment, approve, pipeline control, prepare_review), safe for analysis-only agents. Built-in Prompts/Workflows Predefined workflows for common tasks: reviewing an MR, merging an MR, diagnosing/fixing failed CI, creating an MR from a branch, and triaging open MRs.

Which integrations are available for this server?

Provides tools for interacting with GitLab's API, enabling AI agents to manage merge requests, pipelines, repositories, and perform code reviews.

How do I use @godrix/mcp-gitlab-utils?

1. Click on "Install 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., "@@godrix/mcp-gitlab-utils check the merge status of MR #42" 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.

@godrix/mcp-gitlab-utils

by godrix

Overview Schema Related Servers Score Discussions

TypeScript

Remote

This MCP server provides a GitLab REST API interface for AI agents, enabling management of merge requests, CI/CD pipelines, repositories, and local code review workflows.

Discovery

Resolve project_id, current branch, and MR IID from a local repository path (gitlab_resolve_context).
Search for accessible GitLab projects by name or path (gitlab_search_projects).

Merge Requests

Get MR metadata — title, state, branches, reviewers, labels, pipeline, approvals, and URL (gitlab_get_merge_request).
Check mergeability, including conflicts, draft status, pipeline results, approvals, and blocking discussions (gitlab_get_mr_merge_status).
Fetch MR diff/changes, optionally with failed CI job logs and discussions (gitlab_get_mr_context).
List review threads, inline comments, and general notes (gitlab_get_mr_discussions).
Post inline review comments on specific diff lines (gitlab_add_mr_inline_comment).
Full MR lifecycle: list, get, create, update, approve/unapprove, comment, merge, close, reopen, mark as draft/ready (gitlab_manage_merge_requests).

CI/CD Pipelines

List recent pipelines filtered by branch, MR, or status (gitlab_list_pipelines).
Get pipeline details and job summaries (gitlab_get_pipeline).
Fetch full or truncated logs for a specific CI job (gitlab_get_job_trace).
Control pipelines/jobs: list jobs, play manual jobs, retry a job or pipeline, cancel a pipeline (gitlab_control_pipeline).

Repository

Read remote file contents at any branch, tag, or commit SHA (gitlab_get_file).
Compare two refs to get commits and file diffs (gitlab_compare).

Local Review

Create a git worktree from a local repo or shallow clone and auto-run dependency installation (e.g., npm ci, composer install) for local code review (gitlab_prepare_review).

Read-Only Mode

Set GITLAB_READ_ONLY=true to block all write operations (merge, comment, approve, pipeline control, prepare_review), safe for analysis-only agents.

Built-in Prompts/Workflows Predefined workflows for common tasks: reviewing an MR, merging an MR, diagnosing/fixing failed CI, creating an MR from a branch, and triaging open MRs.

@godrix/gitlab-utils-mcp

Install MCP Server

Node.js MCP server for the GitLab REST API — built for AI agents (pipelines, merge requests, diffs, local review, and context discovery).

Version 0.3.1 — gitlab_-prefixed tools, full MR lifecycle, read-only mode, server instructions, prompts, and resources.

Prerequisites

Node.js 18+
GitLab PAT with api and read_repository (write scope for merge/comment/approve)
Git on PATH (for repo_path, worktrees, and local review)

Related MCP server: GitLab MCP Server

Quick install (npx)

No clone or local build — the published npm package includes compiled JavaScript.

Cursor / Claude Desktop (`mcp.json`)

{
  "mcpServers": {
    "gitlab-utils": {
      "command": "npx",
      "args": ["-y", "@godrix/gitlab-utils-mcp"],
      "env": {
        "GITLAB_TOKEN": "glpat-...",
        "GITLAB_BASE_URL": "https://gitlab.example.com",
        "GITLAB_READ_ONLY": "false"
      }
    }
  }
}

Restart your MCP client after saving. Optional variables: GITLAB_PROJECT_ID, WORKTREE_DIR.

Global install (alternative)

npm install -g @godrix/gitlab-utils-mcp

Then use "command": "gitlab-utils-mcp" in mcp.json (no npx).

Environment variables

Variable	Required	Description
`GITLAB_TOKEN`	Yes	Sent as `PRIVATE-TOKEN` header
`GITLAB_BASE_URL`	Yes	e.g. `https://gitlab.example.com`
`GITLAB_PROJECT_ID`	No	Fallback `group/repo` or numeric ID
`WORKTREE_DIR`	No	Default: `/tmp/referencia_ao_mcp_worktree`
`GITLAB_READ_ONLY`	No	Default: `false`. When `true`, blocks writes (merge, comment, approve, pipeline control, prepare_review)

Project resolution: pass project_id on a tool, or repo_path (local clone) to infer group/repo from origin, or set GITLAB_PROJECT_ID.

MR without IID: with repo_path, the current branch resolves the open MR (source_branch); errors if zero or multiple MRs match. Use gitlab_resolve_context to discover the IID.

Tools

Discovery

Tool	Description
`gitlab_resolve_context`	Resolve `project_path`, branch, and MR from `repo_path`
`gitlab_search_projects`	Search projects accessible by the token

Merge requests

Tool	Description
`gitlab_get_merge_request`	MR metadata (state, reviewers, pipeline)
`gitlab_get_mr_merge_status`	Mergeability: conflicts, draft, pipeline, approvals, blockers
`gitlab_get_mr_context`	Diff/changes + optional CI traces and discussions
`gitlab_get_mr_discussions`	Review threads and comments
`gitlab_add_mr_inline_comment`	Inline comment on a diff line
`gitlab_manage_merge_requests`	`list`, `get`, `create`, `update`, `approve`, `unapprove`, `comment`, `merge`, `close`, `reopen`, `mark_draft`, `mark_ready`

CI/CD

Tool	Description
`gitlab_list_pipelines`	List pipelines (by ref, MR, or status)
`gitlab_get_pipeline`	Pipeline + jobs
`gitlab_get_job_trace`	Job log
`gitlab_control_pipeline`	`list_jobs`, `play`, `retry_job`, `retry_pipeline`, `cancel_pipeline`

Repository

Tool	Description
`gitlab_get_file`	Read remote file at a ref (e.g. `.gitlab-ci.yml`)
`gitlab_compare`	Diff between two refs

Local review

Tool	Description
`gitlab_prepare_review`	`git worktree` + `npm ci` / `composer install`

Prompts (workflows)

Prompt	Use
`review_merge_request`	Full MR review with checklist
`merge_merge_request`	Validate mergeability and merge
`fix_failed_ci`	Diagnose and fix failed pipeline
`create_mr_from_branch`	Create MR from current branch
`triage_open_mrs`	Prioritize open MRs

Resources

URI	Content
`gitlab://guide`	Markdown agent guide (tools and flows)
`gitlab://project/{project_ref}`	Project metadata JSON

Read-only mode

With GITLAB_READ_ONLY=true:

Allowed: reads (MR, diff, pipeline, merge status, list/get)
Blocked: merge, comment, inline comment, approve, create/update MR, pipeline control, prepare_review

Useful for analysis/review agents without mutating GitLab.

Migration 0.2 → 0.3

New tools and actions (no breaking changes to existing names):

Addition	Description
`gitlab_get_mr_merge_status`	Mergeability state and blockers
`gitlab_add_mr_inline_comment`	Inline diff comment
`gitlab_manage_merge_requests`	New actions: `merge`, `close`, `reopen`, `mark_draft`, `mark_ready`

Migration 0.1 → 0.2

Legacy names were renamed with the gitlab_ prefix:

0.1.0	0.2.0
`control_pipeline`	`gitlab_control_pipeline`
`get_mr_context`	`gitlab_get_mr_context`
`manage_mrs`	`gitlab_manage_merge_requests`
`prepare_review`	`gitlab_prepare_review`

gitlab_control_pipeline: retry → retry_job; new actions retry_pipeline and cancel_pipeline.

MCPB install (Claude Desktop / local bundle)

Alternative to npx for clients that support .mcpb files:

Clone the repo: git clone ... && npm install && npm run build
npm run pack:mcpb — produces .mcpb with manifest.json, dist/, and node_modules
For a smaller bundle: npm run pack:mcpb:slim
Install the .mcpb in your client and fill in token + URL

Local development

To contribute or test changes before publishing to npm:

git clone https://github.com/godrix/mcp-gitlab-utils.git
cd mcp-gitlab-utils
npm install
cp .env.example .env   # set GITLAB_TOKEN and GITLAB_BASE_URL
npm run dev            # tsx, stdio
# or
npm run build && npm start

Cursor config pointing at the clone (instead of npx):

{
  "mcpServers": {
    "gitlab-utils": {
      "command": "node",
      "args": ["/absolute/path/mcp-gitlab-utils/dist/main.js"],
      "env": {
        "GITLAB_TOKEN": "glpat-...",
        "GITLAB_BASE_URL": "https://gitlab.example.com",
        "GITLAB_READ_ONLY": "false"
      }
    }
  }
}

Extra requirements for local review: npm and/or composer depending on the target repo.

License

MIT

Install Server

license - permissive license

quality

maintenance

How are these scores calculated?

Maintenance

–Maintainers

–Response time

–Release cycle

1Releases (12mo)

Commit activity

Resources

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Tools

View all tools

Latest Blog Posts

Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly
Lightport: Open-Sourcing Glama's AI Gateway
By punkpeye on April 27, 2026.
OpenAI
open source

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/godrix/mcp-gitlab-utils'

If you have feedback or need assistance with the MCP directory API, please join our Discord server

@godrix/gitlab-utils-mcp

Prerequisites

Quick install (npx)

Cursor / Claude Desktop (mcp.json)

Global install (alternative)

Environment variables

Tools

Discovery

Merge requests

CI/CD

Repository

Local review

Prompts (workflows)

Resources

Read-only mode

Migration 0.2 → 0.3

Migration 0.1 → 0.2

MCPB install (Claude Desktop / local bundle)

Local development

License

Maintenance

Resources

Looking for Admin?

Tools

Latest Blog Posts

MCP directory API

Cursor / Claude Desktop (`mcp.json`)