GitLab, verified
MCP server by GitLab · Verified
Trabaja con issues, merge requests, pipelines y búsqueda de GitLab desde tu asistente de IA.
Connect to GitLab
GitLab needs sign-in. Connect with its own URL:
Your client opens GitLab’s sign-in the first time you use it. The token stays between your client and GitLab.
Share this server
Opens this page, with the URL and setup steps.
mcp.tc/i/gitlabAbout
El servidor MCP oficial de GitLab conecta un asistente con una instancia de GitLab. Está pensado para trabajar con issues, merge requests, pipelines y búsqueda en proyectos de GitLab.
Funciona como un endpoint streamable HTTP alojado en https://gitlab.com/api/v4/mcp. Los usuarios inician sesión con GitLab mediante OAuth usando el scope mcp. Las instancias autogestionadas exponen el mismo endpoint en https:///api/v4/mcp. La lista de herramientas no estaba disponible en el probe, así que las herramientas exactas dependen de la versión de GitLab.
What you can do
- Trabajar con issues de GitLab
- Revisar y gestionar merge requests
- Consultar pipelines de CI/CD
- Buscar en el contenido de GitLab
- Conectar con gitlab.com o con una instancia autogestionada
Tools
GitLab lists its tools only after you sign in, so we can’t show them here. Your client lists them once you’re connected.
Example prompts
Lista los issues abiertos asignados a mí en mi proyecto de GitLab
Resume el último merge request de mi proyecto
¿Por qué falló el último pipeline en la rama main?
Busca en GitLab usos de la opción de configuración obsoleta
Set up
Every client connects to gitlab.com, and GitLab asks you to sign in the first time. Pick yours; the page remembers your choice.
Claude Code
- Run this in a terminal, in your project folder:
claude mcp add --transport http gitlab https://gitlab.com/api/v4/mcp- Start Claude Code, type
/mcp, pick gitlab and choose Authenticate. A browser window opens for the GitLab sign-in.
Add --scope user to make it available in every project, not just this one.
Claude Desktop
- Open Settings → Connectors and click Add custom connector.
- Name it GitLab and paste this URL:
https://gitlab.com/api/v4/mcp- Click Add, then Connect, and sign in when GitLab asks.
Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.
claude.ai
- Open the connector form on claude.ai. This button fills in the name and URL for you:
Add to claude.ai (opens in a new tab)
- Check that the URL reads
https://gitlab.com/api/v4/mcpand click Add. - Click Connect and sign in when GitLab asks.
Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under Organization settings → Connectors.
ChatGPT
- On chatgpt.com, open Settings → Security and login and turn on Developer mode.
- Go to
chatgpt.com/pluginsand click + to create an app for a remote MCP server. - Paste
https://gitlab.com/api/v4/mcpas the server URL and choose OAuth. ChatGPT sends you to GitLab to sign in.
Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts.
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": {
"url": "https://gitlab.com/api/v4/mcp"
}
}
}Cursor shows Needs login next to the server. Click it to sign in.
VS Code
Install in VS Code (opens in a new tab)
Or from a terminal:
code --add-mcp '{"name":"gitlab","type":"http","url":"https://gitlab.com/api/v4/mcp"}'Or commit it to the repo in .vscode/mcp.json:
{
"servers": {
"gitlab": {
"type": "http",
"url": "https://gitlab.com/api/v4/mcp"
}
}
}VS Code asks you to sign in the first time the server starts.
Devin Desktop
- Add it to
~/.config/devin/mcp_config.json(macOS and Linux) or%APPDATA%\devin\mcp_config.json(Windows):
{
"mcpServers": {
"gitlab": {
"serverUrl": "https://gitlab.com/api/v4/mcp"
}
}
}- Refresh the MCP server list in Cascade and sign in when asked.
Devin Desktop is the new name for Windsurf. It reads serverUrl (or url) for remote servers.
Codex
codex mcp add gitlab --url https://gitlab.com/api/v4/mcp
codex mcp login gitlabOr edit ~/.codex/config.toml directly:
[mcp_servers.gitlab]
url = "https://gitlab.com/api/v4/mcp"Gemini CLI
gemini mcp add --transport http gitlab https://gitlab.com/api/v4/mcpThen, inside Gemini CLI, run /mcp auth gitlab to sign in.
This adds it to the current project. Add -s user to use it everywhere.
Any client
Most clients accept this shape. Some name the URL field differently: serverUrl in Devin Desktop, httpUrl in Gemini CLI’s settings file.
{
"mcpServers": {
"gitlab": {
"type": "http",
"url": "https://gitlab.com/api/v4/mcp"
}
}
}Zed puts servers under context_servers in its settings. Cline needs "type": "streamableHttp", or it assumes SSE.
Client only starts local servers? Bridge it with npx -y mcp-remote https://gitlab.com/api/v4/mcp.
FAQ
Can I paste mcp.tc/i/gitlab into my MCP client?
No. mcp.tc links are pages, not server addresses. Connect with https://gitlab.com/api/v4/mcp, so your client talks to GitLab directly. The sign-in token only works there anyway. The quick link is for sharing: it opens this page, with setup steps for every client.
Does GitLab need an API key or a sign-in?
Yes, you need a GitLab account. The first time your client connects, it opens GitLab’s sign-in page. The token goes straight to the server’s own URL, never through mcp.tc.
Is GitLab a remote or a local server?
Remote. GitLab hosts it at https://gitlab.com/api/v4/mcp, and it speaks Streamable HTTP. There’s nothing to install.
What can GitLab do?
You can trabajar con issues de GitLab, revisar y gestionar merge requests and consultar pipelines de CI/CD.
Which clients can use it?
Any client that supports remote MCP servers: Claude Code, Claude Desktop, claude.ai, ChatGPT in developer mode, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. The setup steps cover each one.
Who wrote this page?
mcp.tc’s robot read GitLab’s own metadata (its MCP handshake, tool list and public 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. This translation was made by an AI model from the English text.
Embed
Show GitLab in a README or on your site. Each embed links to this page, uses the server’s own URL, and sets no cookies. How embeds work
README badge
[](https://mcp.tc/i/gitlab)<a href="https://mcp.tc/i/gitlab"><img src="https://mcp.tc/i/gitlab/badge.svg" alt="GitLab 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.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" title="GitLab 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, the server’s own URL, tools and the “Add to” links. Any site can read it (CORS is open).
https://mcp.tc/i/gitlab.jsonmcp.tc isn’t affiliated with GitLab. This page was built from GitLab’s public metadata, last checked on 3 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. The translation was made by an AI model from the English text.