io.github.vish288/mcp-gitlab

io.github.vish288/mcp-gitlab

GitLab MCP server (MCP 2026-07-28): projects, MRs, pipelines, CI/CD, issues; writes or read-only

Connect this server

Add this to your MCP client config — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor).Suits: Claude Desktop · Cursor.

{
  "mcpServers": {
    "mcp-gitlab": {
      "command": "uvx",
      "args": [
        "mcp-gitlab"
      ],
      "env": {
        "GITLAB_TOKEN": "<your GITLAB_TOKEN>",
        "GITLAB_URL": "<your GITLAB_URL>",
        "GITLAB_OAUTH_CLIENT_SECRET": "<your GITLAB_OAUTH_CLIENT_SECRET>",
        "GITLAB_OAUTH_JWT_KEY": "<your GITLAB_OAUTH_JWT_KEY>",
        "GITLAB_HTTP_BEARER_TOKEN": "<your GITLAB_HTTP_BEARER_TOKEN>"
      }
    }
  }
}
Environment variables
  • GITLAB_TOKENsecretGitLab personal access token (token mode). Optional after `mcp-gitlab auth login`; also accepts GITLAB_PAT, GITLAB_PERSONAL_ACCESS_TOKEN, GITLAB_API_TOKEN
  • GITLAB_URLrequiredGitLab instance URL (e.g. https://gitlab.com)
  • GITLAB_OAUTH_CLIENT_SECRETsecretSecret of the GitLab OAuth app (oauth mode)
  • GITLAB_OAUTH_JWT_KEYsecretFastMCP JWT signing key, >=32 random chars (oauth mode; defaults to one derived from the client secret)
  • GITLAB_HTTP_BEARER_TOKENsecretBearer token (min 16 chars) required to bind an HTTP transport to a non-loopback host; clients send it as 'Authorization: Bearer <token>' (token mode; --auth oauth has its own sign-in)

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
Developer Tools
Version
0.22.0
Registry
active
Published
11/6/2026
Browse all Developer Tools →

Add the badge to your site

Show visitors that io.github.vish288/mcp-gitlab is listed here — it’s also the link we check for a free listing.

io.github.vish288/mcp-gitlab — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/io-github-vish288-mcp-gitlab?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="io.github.vish288/mcp-gitlab — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![io.github.vish288/mcp-gitlab — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/io-github-vish288-mcp-gitlab?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.