mcp-gitlab

What this does

mcp-gitlab exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

GITLAB_TOKEN
GITLAB_URL
GITLAB_READ_ONLY
MCP_READ_ONLY
GITLAB_AUTH
GITLAB_OAUTH_CLIENT_ID
GITLAB_OAUTH_CLIENT_SECRET
GITLAB_OAUTH_BASE_URL
GITLAB_OAUTH_SCOPES
GITLAB_OAUTH_JWT_KEY
GITLAB_HTTP_BEARER_TOKEN

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

How do I install mcp-gitlab?

Run the Claude Code command in the install section to add mcp-gitlab to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with mcp-gitlab?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to mcp-gitlab as well.

Does mcp-gitlab need an API key?

Yes. Before it can run, set these environment variables: GITLAB_TOKEN, GITLAB_URL, GITLAB_READ_ONLY, MCP_READ_ONLY, GITLAB_AUTH, GITLAB_OAUTH_CLIENT_ID, GITLAB_OAUTH_CLIENT_SECRET, GITLAB_OAUTH_BASE_URL, GITLAB_OAUTH_SCOPES, GITLAB_OAUTH_JWT_KEY, GITLAB_HTTP_BEARER_TOKEN. They go in the env block of your MCP config.