GitLab (zereight)
MCP server by zereight
Manage GitLab projects, merge requests, issues, pipelines, wikis and releases from your assistant, on GitLab.com or self-managed.
Install GitLab (zereight)
Runs on your machine. Your client starts it with this command:
Needs Node.js on your computer. The setup steps below show where the command goes in each client.
GITLAB_PERSONAL_ACCESS_TOKENsecret GitLab personal access token for local stdio use. Create a token with the GitLab scopes needed by the tools you plan to use, such as api…GITLAB_JOB_TOKENsecret optional Optional GitLab CI job token to use instead of a personal access token when running inside GitLab CI.GITLAB_AUTH_COOKIE_PATHoptional Optional path to a GitLab authentication cookie file for cookie-based authentication.GITLAB_API_URLoptional GitLab API base URL. Use https://gitlab.com/api/v4 for GitLab.com or your self-managed GitLab API URL.GITLAB_ALLOWED_PROJECT_IDSoptional Optional comma-separated list of GitLab project IDs that this server is allowed to access.GITLAB_READ_ONLY_MODEoptional Set to true to expose only read-only tools and block write operations.
Share this server
Opens this page, with the install command and setup steps.
mcp.tc/i/gitlab-zereightAbout
Community GitLab server that exposes the GitLab API as MCP tools. It covers projects, merge requests, issues, pipelines, wiki, releases, tags and milestones. The README lists about 267 tools and a discover_tools helper, so you can start with a small toolset and enable more at runtime. Merge request review uses a two-step flow: list changed files, then fetch batched file diffs.
It runs locally through npx as the npm package @zereight/mcp-gitlab, over stdio, SSE or Streamable HTTP. It needs a GitLab personal access token in GITLAB_PERSONAL_ACCESS_TOKEN, or OAuth2 sign-in. Options include read-only mode, project allow lists, toolset selection and a custom GITLAB_API_URL for self-managed instances.
What you can do
- Browse GitLab projects, groups and users
- Review merge requests with batched file diffs
- Create and update issues and merge requests
- Inspect and manage CI/CD pipelines
- Read and edit wiki pages when the wiki is enabled
- Manage releases, tags and milestones
- Restrict access with read-only mode, project allow lists or toolsets
Tools
GitLab (zereight) lists its tools only to clients with a key, so we can’t show them here.
Example prompts
List open merge requests assigned to me in my main project
Show the changed files in merge request 142 and summarize the diff
Create an issue for the failing login test and label it bug
Which pipelines failed on main this week?
Set up
Every client starts GitLab (zereight) on your machine with the same command. Pick yours; the page remembers your choice.
Claude Code
- Run this in a terminal, in your project folder:
claude mcp add --transport stdio gitlab-zereight --env "GITLAB_PERSONAL_ACCESS_TOKEN=<YOUR_GITLAB_PERSONAL_ACCESS_TOKEN>" --env "GITLAB_JOB_TOKEN=<YOUR_GITLAB_JOB_TOKEN>" -- npx -y @zereight/mcp-gitlab- Start Claude Code and type
/mcp. gitlab-zereight should show as connected.
Add --scope user to make it available in every project. Replace the placeholders with your own values.
Claude Desktop
- Open Settings → Developer → Edit Config. It opens
claude_desktop_config.json. Add:
{
"mcpServers": {
"gitlab-zereight": {
"command": "npx",
"args": [
"-y",
"@zereight/mcp-gitlab"
],
"env": {
"GITLAB_PERSONAL_ACCESS_TOKEN": "<YOUR_GITLAB_PERSONAL_ACCESS_TOKEN>",
"GITLAB_JOB_TOKEN": "<YOUR_GITLAB_JOB_TOKEN>"
}
}
}
}- Save the file and restart Claude Desktop. Replace the placeholders with your own values.
Needs Node.js on your computer. The file lives in ~/Library/Application Support/Claude/ on macOS and %APPDATA%\Claude\ on Windows.
Cursor
Add to Cursor (opens in a new tab)
Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):
{
"mcpServers": {
"gitlab-zereight": {
"command": "npx",
"args": [
"-y",
"@zereight/mcp-gitlab"
],
"env": {
"GITLAB_PERSONAL_ACCESS_TOKEN": "<YOUR_GITLAB_PERSONAL_ACCESS_TOKEN>",
"GITLAB_JOB_TOKEN": "<YOUR_GITLAB_JOB_TOKEN>"
}
}
}
}Needs Node.js on your computer. Replace the placeholders with your own values.
VS Code
Add it to .vscode/mcp.json. VS Code asks for the secret the first time and stores it securely:
{
"servers": {
"gitlab-zereight": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@zereight/mcp-gitlab"
],
"env": {
"GITLAB_PERSONAL_ACCESS_TOKEN": "${input:gitlab-personal-access-token}",
"GITLAB_JOB_TOKEN": "${input:gitlab-job-token}"
}
}
},
"inputs": [
{
"type": "promptString",
"id": "gitlab-personal-access-token",
"description": "GITLAB_PERSONAL_ACCESS_TOKEN",
"password": true
},
{
"type": "promptString",
"id": "gitlab-job-token",
"description": "GITLAB_JOB_TOKEN",
"password": true
}
]
}Needs Node.js on your computer.
Devin Desktop
- Add it to
~/.config/devin/mcp_config.json(macOS and Linux) or%APPDATA%\devin\mcp_config.json(Windows):
{
"mcpServers": {
"gitlab-zereight": {
"command": "npx",
"args": [
"-y",
"@zereight/mcp-gitlab"
],
"env": {
"GITLAB_PERSONAL_ACCESS_TOKEN": "<YOUR_GITLAB_PERSONAL_ACCESS_TOKEN>",
"GITLAB_JOB_TOKEN": "<YOUR_GITLAB_JOB_TOKEN>"
}
}
}
}- Refresh the MCP server list in Cascade. Replace the placeholders with your own values.
Devin Desktop is the new name for Windsurf.
Codex
codex mcp add gitlab-zereight --env "GITLAB_PERSONAL_ACCESS_TOKEN=<YOUR_GITLAB_PERSONAL_ACCESS_TOKEN>" --env "GITLAB_JOB_TOKEN=<YOUR_GITLAB_JOB_TOKEN>" -- npx -y @zereight/mcp-gitlabOr edit ~/.codex/config.toml directly:
[mcp_servers.gitlab-zereight]
command = "npx"
args = ["-y", "@zereight/mcp-gitlab"]
env = { GITLAB_PERSONAL_ACCESS_TOKEN = "<YOUR_GITLAB_PERSONAL_ACCESS_TOKEN>", GITLAB_JOB_TOKEN = "<YOUR_GITLAB_JOB_TOKEN>" }Needs Node.js on your computer. Replace the placeholders with your own values.
Gemini CLI
gemini mcp add -e "GITLAB_PERSONAL_ACCESS_TOKEN=<YOUR_GITLAB_PERSONAL_ACCESS_TOKEN>" -e "GITLAB_JOB_TOKEN=<YOUR_GITLAB_JOB_TOKEN>" gitlab-zereight npx -- -y @zereight/mcp-gitlabThis adds it to the current project. Add -s user to use it everywhere.
Any client
Most clients that start local servers accept this shape:
{
"mcpServers": {
"gitlab-zereight": {
"command": "npx",
"args": [
"-y",
"@zereight/mcp-gitlab"
],
"env": {
"GITLAB_PERSONAL_ACCESS_TOKEN": "<YOUR_GITLAB_PERSONAL_ACCESS_TOKEN>",
"GITLAB_JOB_TOKEN": "<YOUR_GITLAB_JOB_TOKEN>"
}
}
}
}Zed puts servers under context_servers in its settings, with the same command, args and env fields.
Needs Node.js on your computer. Replace the placeholders with your own values.
Embed
Show GitLab (zereight) in a README or on your site. Each embed links to this page, uses the server’s own install command, and sets no cookies. How embeds work
The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.
README badge
[](https://mcp.tc/i/gitlab-zereight)<a href="https://mcp.tc/i/gitlab-zereight"><img src="https://mcp.tc/i/gitlab-zereight/badge.svg" alt="GitLab (zereight) on mcp.tc" height="20"></a>It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.
Website card
<script src="https://mcp.tc/w/gitlab-zereight.js" async></script>The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.
iframe
<iframe src="https://mcp.tc/embed/gitlab-zereight" title="GitLab (zereight) on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.
JSON
The listing as data for your own pages and tools: name, tagline, install command, tools and the “Add to” links. Any site can read it (CORS is open).
https://mcp.tc/i/gitlab-zereight.jsonAI prompt
Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the GitLab (zereight) card to your site.
Add the mcp.tc card for GitLab (zereight), an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.
Put this tag where the card should appear. The card renders right before it:
```html
<script src="https://mcp.tc/w/gitlab-zereight.js" async></script>
```
To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.
```html
<div data-mcptc="gitlab-zereight"><a href="https://mcp.tc/i/gitlab-zereight">GitLab (zereight) on mcp.tc</a></div>
```
Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.
If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).
For a README or other Markdown docs, use the badge instead:
```markdown
[](https://mcp.tc/i/gitlab-zereight)
```
Reference: https://mcp.tc/embedChange history
This server runs on your computer, so we follow its npm package: each new version shows up here, with edits by its owner.
-
New version 2.3.29 (was 2.3.28). Read from npm.
-
New version 2.3.28 (was 2.3.27). Read from npm.
-
New version 2.3.27 (was 2.3.26). Read from npm.
-
New version 2.3.26 (was 2.3.25). Read from npm.
-
New version 2.3.23 (was 2.3.22). Read from npm.
-
New version 2.3.22 (was 2.3.21). Read from npm.
-
New version 2.3.20 (was 2.3.19). Read from npm.
-
New version 2.3.18 (was 2.3.17). Read from npm.
-
New version 2.3.16 (was 2.3.15). Read from npm.
-
New version 2.3.14 (was 2.3.13). Read from npm.
-
New version 2.3.12 (was 2.3.11). Read from npm.
-
New version 2.3.8 (was 2.3.7). Read from npm.
-
New version 2.3.7 (was 2.3.6). Read from npm.
-
New version 2.3.6 (was 2.3.5). Read from npm.
-
New version 2.3.5 (was 2.3.4). Read from npm.
-
New version 2.3.4 (was 2.3.3). Read from npm.
-
New version 2.3.3 (was 2.3.2). Read from npm.
-
New version 2.3.2 (was 2.3.1). Read from npm.
-
New version 2.3.0 (was 2.2.6). Read from npm.
-
New version 2.2.5 (was 2.2.4). Read from npm.
-
New version 2.2.2 (was 2.2.1). Read from npm.
-
New version 2.2.1 (was 2.2.0). Read from npm.
-
New version 2.1.70 (was 2.1.69). Read from npm.
-
Tracking started: version 2.1.69.
FAQ
Can I paste mcp.tc/i/gitlab-zereight into my MCP client?
No. GitLab (zereight) runs on your own computer, started by your client, so it has no web address to connect to. The quick link is the page to share; the install command is npx -y @zereight/mcp-gitlab.
Does GitLab (zereight) need an API key?
Yes. It reads GITLAB_PERSONAL_ACCESS_TOKEN and GITLAB_JOB_TOKEN from its environment, and GITLAB_PERSONAL_ACCESS_TOKEN and GITLAB_JOB_TOKEN are secrets. Put the values in your client’s config on your own machine, never in a shared file.
Is GitLab (zereight) a remote or a local server?
Local. Your client starts it as a process on your computer with npx -y @zereight/mcp-gitlab, which needs Node.js.
What can GitLab (zereight) do?
You can browse GitLab projects, groups and users, review merge requests with batched file diffs and create and update issues and merge requests.
Which clients can use it?
Any client that starts local servers: Claude Code, Claude Desktop, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. claude.ai and ChatGPT only connect to remote servers.
Does mcp.tc track changes to GitLab (zereight)?
Partly. It runs on your computer, so we follow its npm package: its History tab shows each new version and edits by its owner. Follow the listing to get an email when it changes.
Who wrote this page?
mcp.tc’s robot read GitLab (zereight)’s public metadata (its package and repository pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.
mcp.tc isn’t affiliated with zereight. This page was built from GitLab (zereight)’s public metadata, last checked on 4 Oct 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.