GitHub
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
Description from the maker (original English)
Developer-ready GitLab MCP server for CE and EE instances.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
GITLAB_PERSONAL_ACCESS_TOKEN, GITLAB_API_URL, GITLAB_READ_ONLY, GITLAB_EXPOSE_ALL_TOOLS, MCP_OUTPUT_FORMATValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"gitlab": {
"command": "npx",
"args": [
"-y",
"@sumirati/mcp-gitlab"
],
"env": {
"GITLAB_PERSONAL_ACCESS_TOKEN": "your-value",
"GITLAB_API_URL": "your-value",
"GITLAB_READ_ONLY": "your-value",
"GITLAB_EXPOSE_ALL_TOOLS": "your-value",
"MCP_OUTPUT_FORMAT": "your-value"
}
}
}
}Run this in your terminal
claude mcp add gitlab --env GITLAB_PERSONAL_ACCESS_TOKEN=your-value --env GITLAB_API_URL=your-value --env GITLAB_READ_ONLY=your-value --env GITLAB_EXPOSE_ALL_TOOLS=your-value --env MCP_OUTPUT_FORMAT=your-value -- npx -y @sumirati/mcp-gitlabFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"gitlab": {
"command": "npx",
"args": [
"-y",
"@sumirati/mcp-gitlab"
],
"env": {
"GITLAB_PERSONAL_ACCESS_TOKEN": "your-value",
"GITLAB_API_URL": "your-value",
"GITLAB_READ_ONLY": "your-value",
"GITLAB_EXPOSE_ALL_TOOLS": "your-value",
"MCP_OUTPUT_FORMAT": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"gitlab": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@sumirati/mcp-gitlab"
],
"env": {
"GITLAB_PERSONAL_ACCESS_TOKEN": "your-value",
"GITLAB_API_URL": "your-value",
"GITLAB_READ_ONLY": "your-value",
"GITLAB_EXPOSE_ALL_TOOLS": "your-value",
"MCP_OUTPUT_FORMAT": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
GITLAB_API_URL envGITLAB_READ_ONLY envGITLAB_EXPOSE_ALL_TOOLS envMCP_OUTPUT_FORMAT envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account sumirati, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: GITLAB_PERSONAL_ACCESS_TOKEN
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (3.2.0) reached the registry 21 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: GitHub, Desktop Commander, Cloudflare MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
MCP server for terminal commands, file operations, and process management
Cloudflare MCP servers
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
@sumirati/mcp-gitlab)A modern, 2026 AI-native Model Context Protocol (MCP) server for GitLab API v4, engineered for self-hosted GitLab Community Edition (CE), Enterprise Edition (EE), and GitLab.com.
In early MCP servers, dumping 50–100 tools into the client's tool list consumed 10,000+ prompt context tokens on every turn ("System Prompt Tax") and resulted in poor Coherence ratings on the [Glama TDQS](https://github.com/glama-ai/tool-definition-quality-score) rubric.
@sumirati/mcp-gitlab v3 solves this with a 5-Tool Hybrid Surface:
get_file_contents, get_project, get_commit) remain eager tools for instant zero-hop execution.gitlab_find_actions $\rightarrow$ gitlab_execute_action), delivering 75%–96% token savings with default high-density Markdown tables and summaries (format: "markdown" | "json").list_pipelines), the server dynamically executes it with full input validation and projection.LLM Prompt Context (1,292 tokens total):
├── 1. gitlab_find_actions(query, [domain], [format]) [Meta Discovery] ├── 2. gitlab_execute_action(action, params, [format]) [Meta Dynamic Execution] ├── 3. get_file_contents(project_id, file_path, [ref]) [Eager Daily Driver #1] ├── 4. get_project(project_id, [statistics]) [Eager Daily Driver #2] └── 5. get_commit(project_id, sha) [Eager Daily Driver #3]
Under the hood (Dynamic Registry): └── 90 Curated Actions across 14 Domains (with 75%–99% token reduction projections)
system_health_check).list_push_mirrors) and force immediate sync (trigger_push_mirror_sync).list_runners, get_runner_status).list_project_hooks).buggycode/project-name), branch lifecycle, branch protection management (list_protected_branches, protect_branch, unprotect_branch), file/directory reading (get_file_contents), and atomic multi-file commits (push_files, create_commit).create_pipeline, cancel_pipeline, retry_pipeline), tail failed job logs (get_job_trace) without token blowout, read build artifacts (get_job_artifact_file), and inspect JUnit test reports (get_pipeline_test_report).get_merge_request_changes), automated lockfile pruning (package-lock.json), and inline diff discussions with SHA coordinate resolution (create_diff_discussion).list_issue_links, create_issue_link), and add progress notes (list_issue_notes, create_issue_note).toc_only: true), chapter extraction, and snippet management.create_group), and owned project discovery.npx (No installation needed)npx -y @sumirati/mcp-gitlab
npm install -g @sumirati/mcp-gitlab
mcp-gitlab
git clone https://github.com/sumirati/mcp-gitlab.git
cd mcp-gitlab npm install npm test npm start
| Variable | Required | Default | Description |
|---|---|---|---|
GITLAB_PERSONAL_ACCESS_TOKEN | Yes | — | Personal access token with api scope. |
GITLAB_API_URL | No | https://gitlab.com/api/v4 | Base API URL of your GitLab CE/EE or cloud instance. |
GITLAB_READ_ONLY | No | false | Enable Read-Only safety mode (true, 1, yes). Filters out mutating tools and strictly blocks write/modify HTTP requests across all 90 actions. |
GITLAB_EXPOSE_ALL_TOOLS | No | false | Set to true (or GITLAB_EXPOSE_LEGACY_TOOLS=true) to disable the 5-tool hybrid surface and expose all 90 tools directly on ListTools for legacy clients. |
MCP_OUTPUT_FORMAT | No | markdown | Default output format (markdown for compact tables/summaries, or json for structured objects). |
Add to your MCP configuration file (mcp_config.json or claude_desktop_config.json):
{
"mcpServers": { "gitlab": { "command": "npx", "args": ["-y", "@sumirati/mcp-gitlab"], "env": { "GITLAB_PERSONAL_ACCESS_TOKEN": " ", "GITLAB_API_URL": "https://gitlab.example.com/api/v4" } } } }
All 90 actions feature strict input validation and field-mask projections:
| Tool | Type | Description |
|---|---|---|
gitlab_find_actions | Meta | Search and discover available GitLab operations across all 14 domains with compact parameter signatures |
gitlab_execute_action | Meta | Execute any discovered GitLab platform action with input validation and token-optimized projection |
get_file_contents | Eager | Read decoded file contents, symbol outlines, or directory listings from any branch or commit ref without cloning |
get_project | Eager | Retrieve project metadata, project ID, visibility, clone URLs, topics, and default branch |
get_commit | Eager | Inspect Git commit details, author info, and token-capped file diffs |
enterprise — 6 actions)| Action | Description | Mutating? |
|---|---|---|
system_health_check | Perform end-to-end connectivity, latency, and permission diagnostics against the GitLab instance. Verifies API availability, authentication identity, server version/edition (when permitted), and active read-only policy. | No |
list_push_mirrors | List remote push mirrors configured for a project, including synchronization status, target URLs, and last error diagnostics. Essential for verifying repository synchronization between local self-hosted instances and upstream GitLab instances or remote Git hosts. | No |
trigger_push_mirror_sync | Force an immediate push mirror synchronization for a designated project remote mirror. Use when code has been committed locally and immediate upstream replication is required without waiting for the scheduled background sync interval. | Yes |
list_runners | List available GitLab CI/CD runners (instance, group, or project-level), detailing their online status, active/paused state, and executor types. Use to diagnose CI pipeline execution delays, runner connectivity, or missing executor tags. | No |
get_runner_status | Retrieve comprehensive details and health status for a specific CI/CD runner, including IP address, architecture, runner version, tags, and last contacted timestamp. Use to troubleshoot stuck jobs or unresponsive self-hosted runners. | No |
list_project_hooks | List configured project webhooks and their subscribed triggers (push, merge requests, issues, pipeline events). Use to audit integration webhooks and verify CI/CD automation hook registrations. | No |
repositories — 10 actions)| Action | Description | Mutating? |
|---|---|---|
search_repositories | Search for GitLab projects and repositories across the instance or scoped to a specific group namespace (recommended to reduce instance load). Capped at 100 per page. If project_id or path_with_namespace is already known, look up directly via 'get_project'. | No |
get_project | Retrieve comprehensive metadata for a specific GitLab project, including default branch, repository statistics, visibility, and topic tags. Use to inspect repository settings or verify project access. Do NOT use to inspect directory trees or source code; use 'get_file_contents' instead. | No |
create_repository | Create a new GitLab project/repository under your personal namespace or a designated group. Use when provisioning new codebases or initializing repositories. Side effect: creates a new GitLab project immediately. Do NOT use to duplicate existing projects; use 'fork_repository' instead. | Yes |
update_project | Update mutable project settings including display name, description, default branch, visibility level, and topics. Use to modify repository configurations or administrative details. Side effect: alters project settings immediately. Do NOT use to commit code changes; use 'create_or_update_file' or 'push_files'. | Yes |
delete_project | Permanently delete a GitLab project and all its repository files, issues, merge requests, and CI/CD pipelines. Use solely for project decommissioning. Side effect: DESTRUCTIVE and irreversible. Requires explicit safety confirmation via confirm_project_name. | Yes |
get_file_contents | Read the raw content of a specific file or directory tree from a repository at a designated branch, tag, or commit ref. Use when inspecting current repository source code or configs. Do NOT use for reviewing diffs between branches (use 'get_merge_request_changes') or viewing commit diffs (use 'get_commit'). | No |
create_or_update_file | Create a new file or update the content of an existing file in a repository with a Git commit. Use for single-file changes or documentation updates. Side effect: creates an immediate Git commit on the remote branch. Do NOT use when updating multiple files together; use 'push_files' instead for atomic multi-file commits. | Yes |
push_files | Atomically commit multiple file additions, modifications, or deletions to a target branch in a single Git commit. Use for multi-file refactors, features, or project scaffolding. Side effect: creates an atomic multi-action Git commit on the remote branch. Use instead of calling 'create_or_update_file' in a loop. | Yes |
| create_commit | Atomically commit multiple file additions, modifications, or updates to a target branch in a single Git commit using GitLab Commits API. Use for multi-file
Only the beginning is shown; read the rest in the repo