Featured

Deploy OpenClaw in 60 seconds — 20% off logoDeploy OpenClaw in 60 seconds — 20% off

Launch OpenClaw on Hostinger in about 60 seconds and keep your agent live 24/7. Our referral link gives you 20% off, no coupon code needed.

Launch on Hostinger
Run your Hermes agent on Hostinger, fully managed logoRun your Hermes agent on Hostinger, fully managed

Launch Hermes on Hostinger in one click, fully managed, no VPS knowledge needed. Use code ZACAARON10 for 10% off.

Launch on Hostinger
Crawl and scrape any site into clean data, 10% off logoCrawl and scrape any site into clean data, 10% off

Firecrawl crawls and scrapes any site into clean markdown for your agent. Get 1,000 free credits, and new users get 10% off their first purchase.

Try Firecrawl free
6,000+ web scrapers for your AI agent, start free logo6,000+ web scrapers for your AI agent, start free

Apify gives your agent live web data: 6,000+ prebuilt scrapers and actors, MCP-ready. Sign up free with $5 in usage credits.

Try Apify free
One API to scrape, enrich, and extract the internet. logoOne API to scrape, enrich, and extract the internet.

Context.dev gives your agents a single API to scrape, enrich, and extract live web data — no proxies, no parsers, no maintenance.

Start building free
SetupClaw: done-for-you OpenClaw for founders & exec teams logoSetupClaw: done-for-you OpenClaw for founders & exec teams

White-glove OpenClaw for founders and exec teams (4–50+ employees): we install, harden, integrate your tools, and maintain it — secured from day one.

Get it set up for you
SEO data APIs for your agent, $1 free credit logoSEO data APIs for your agent, $1 free credit

DataForSEO gives your agent live access to SERP results, keyword data, backlinks, and on-page SEO data through one API. New accounts get a $1 credit, good for up to 20,000 keyword or backlink lookups.

Try DataForSEO free
Reach 48,000+ AI builders

A flat monthly placement in front of developers actively installing AI tools. No lock-in, cancel anytime.

Advertise here

Works with

Claude CodeClaude DesktopCursorVS CodeClineCodex CLIOpenClaw+ any MCP client

Install to Claude Code

This server doesn't publish a one-line install command. Follow the setup in the source repository.

Summary

A Model Context Protocol server for self-hosted GitLab instances, enabling users to manage issues, merge requests, pipelines, and more via Claude Code.

README.md

GitLab MCP Server

Token-optimized Model Context Protocol server for self-hosted GitLab instances, designed for Claude Code.

Features

  • Multi-profile PAT management — switch between multiple GitLab instances
  • Compact text responses — minimal token usage for LLM context
  • Project caching — avoids redundant API calls (2min TTL)
  • Full GitLab workflow — issues, merge requests, pipelines, notes
  • Env or config-file auth — flexible credential management

Setup

1. Install dependencies

bun install

2. Get a GitLab Personal Access Token

  1. Go to your GitLab instance → SettingsAccess Tokens
  2. Create a token with scopes: api, read_user

3. Configure

Option A: Environment variables

export GITLAB_BASE_URL="https://gitlab.example.com"
export GITLAB_TOKEN="your-personal-access-token"
export GITLAB_DEFAULT_PROJECT="group/subgroup/repo"  # optional

Option B: Use the set_gitlab_pat tool at runtime — profiles are stored in ~/.config/gitlab-mcp-server/config.json with 0600 permissions.

4. Add to Claude Code

Add to your ~/.claude/settings.json or project .claude/settings.json:

{
  "mcpServers": {
    "gitlab": {
      "command": "bun",
      "args": ["run", "/path/to/gitlab-mcp-server/index.ts"],
      "env": {
        "GITLAB_BASE_URL": "https://gitlab.example.com",
        "GITLAB_TOKEN": "your-personal-access-token",
        "GITLAB_DEFAULT_PROJECT": "group/subgroup/repo"
      }
    }
  }
}

Available Tools

Profile Management

| Tool | Description | |------|-------------| | set_gitlab_pat | Save or update a GitLab PAT profile | | list_gitlab_profiles | List saved profiles (tokens masked) | | use_gitlab_profile | Switch active profile | | delete_gitlab_profile | Delete a saved profile | | get_authenticated_user | Verify PAT and show current user |

Projects

| Tool | Description | |------|-------------| | get_projects | List accessible projects (search, filter) | | get_project | Get project details by ID or path |

Issues

| Tool | Description | |------|-------------| | get_issues | List issues with filters (state, labels, assignee) | | get_issue | Full issue details with recent notes | | create_issue | Create a new issue | | add_issue_note | Add a comment to an issue |

Merge Requests

| Tool | Description | |------|-------------| | get_merge_requests | List MRs with filters (state, assignee) | | get_merge_request | Full MR details with recent notes | | create_merge_request | Create a new merge request | | add_merge_request_note | Add a comment to a merge request |

Pipelines

| Tool | Description | |------|-------------| | get_pipelines | List recent pipelines (filter by ref, status) | | get_pipeline | Pipeline details with job breakdown | | retry_pipeline | Retry all failed jobs in a pipeline | | cancel_pipeline | Cancel a running pipeline |

Multi-Instance Support

All tools use the active profile. Switch between GitLab instances:

# Save profiles
set_gitlab_pat(name: "work", baseUrl: "https://gitlab.company.com", token: "...")
set_gitlab_pat(name: "oss", baseUrl: "https://gitlab.com", token: "...")

# Switch
use_gitlab_profile(name: "work")

Projects can be referenced by ID or path:

projectId: "123"
projectPath: "group/subgroup/repo"

If defaultProject is set in the profile, it's used when neither is provided.

License

MIT

See related servers & alternatives →

Related MCP servers

Browse all →

Related guides

Hand-picked reading to help you choose and use Developer Tools servers.