mpaarating/gitlab-mcp

GitLab MCP Server

A Model Context Protocol (MCP) server for retrieving GitLab merge request comments.

🔒 READ-ONLY: This server only fetches data from GitLab. It never modifies MR state, comments, or any other GitLab data.

What is this?

This MCP server enables AI coding agents (like Cursor, Claude Desktop, or any MCP-compatible client) to fetch comments from GitLab merge requests in a structured, agent-friendly format. It's designed to help agents:

• 📋 Compile unresolved comments into fix plans
• 🎯 Extract inline discussions with file paths and line numbers
• 🔍 Filter feedback by resolution status
• 📝 Generate human-readable summaries

Features

• Unified Comment Structure: Combines inline discussions and overview notes into a single normalized format
• Smart Filtering: Include/exclude system notes, filter by resolution status
• File Path Extraction: Automatically extracts file paths from inline comments
• Thread Context: Groups related comments by discussion thread
• Dual Output Formats: JSON for programmatic use, Markdown for human reading
• Retry Logic: Handles transient errors with exponential backoff
• Pagination Support: Automatically fetches all pages
• Security First: Token-based auth, secret redaction in logs

Quick Start

1. Install Dependencies

npm install

2. Build the Server

npm run build

3. Set Up GitLab Token

Create a Personal Access Token in GitLab:

1. Go to GitLab → Preferences → Access Tokens
2. Create a token with read_api scope (recommended for read-only access)
3. Copy the token

4. Configure MCP Client

For Cursor

Add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "gitlab-mr-comments": {
      "command": "node",
      "args": ["/absolute/path/to/gitlab-mcp/dist/server.js"],
      "env": {
        "GITLAB_BASE_URL": "https://gitlab.com",
        "GITLAB_TOKEN": "glpat_your_token_here"
      }
    }
  }
}

For Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%/Claude/claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "gitlab-mr-comments": {
      "command": "node",
      "args": ["/absolute/path/to/gitlab-mcp/dist/server.js"],
      "env": {
        "GITLAB_BASE_URL": "https://gitlab.com",
        "GITLAB_TOKEN": "glpat_your_token_here"
      }
    }
  }
}

5. Restart Your MCP Client

Restart Cursor or Claude Desktop for the configuration to take effect.

Available Tools

This MCP server provides the following tool(s):

gitlab_get_mr_comments

Fetches comments from a GitLab merge request, including inline discussions and overview notes.

Tool Name: gitlab_get_mr_comments

Description: Fetch comments from a GitLab merge request. Returns inline discussions and overview notes in a structured format. Supports filtering by resolution status and excluding system notes. Useful for AI agents to review feedback and plan code fixes.

When to use:

• Review unresolved comments for a merge request
• Get feedback on specific files
• Generate fix plans from reviewer comments
• Check resolution status of discussions

Usage

Basic Usage

Ask your AI agent:

"Fetch all unresolved comments from MR !123 in project my-org/my-repo"

The agent will automatically discover and use the gitlab_get_mr_comments tool with appropriate parameters.

Example Tool Call

{
  "tool": "gitlab_get_mr_comments",
  "arguments": {
    "project": "my-org/my-repo",
    "mr": 123,
    "onlyUnresolved": true,
    "includeSystem": false
  }
}

Tool Parameters

Note: onlyResolved and onlyUnresolved are mutually exclusive.

Agent Workflow Examples

Fix Plan Generation

User: "Review all unresolved comments on MR !456 and create a fix plan"

Agent:
1. Calls gitlab_get_mr_comments with onlyUnresolved=true
2. Groups comments by file_path
3. Generates prioritized fix plan:
   - src/api/users.ts (3 comments)
     • Line 45: Add error handling
     • Line 78: Extract to helper
     • Line 92: Add validation

File-Specific Review

User: "What feedback did reviewers leave on src/api/users.ts?"

Agent:
1. Fetches all comments from MR
2. Filters client-side for file_path = "src/api/users.ts"
3. Summarizes feedback for that specific file

Release Readiness

User: "Summarize blocking issues on MR !789"

Agent:
1. Fetches all unresolved comments
2. Searches for keywords: "blocker", "must fix", "breaking"
3. Presents summary of blocking issues

Environment Variables

Quick Setup:

cp .env.example .env
# Edit .env with your GITLAB_TOKEN

See .env.example for detailed configuration options.

Self-Managed GitLab

To use with a self-managed GitLab instance:

{
  "env": {
    "GITLAB_BASE_URL": "https://gitlab.your-company.com",
    "GITLAB_TOKEN": "glpat_your_token_here"
  }
}

Troubleshooting

"GITLAB_TOKEN environment variable is required"

Cause: The MCP server cannot find the GitLab token in the environment

Solution:

1. Verify MCP Configuration: Check your MCP config file and ensure GITLAB_TOKEN is in the env section:

   • Cursor: ~/.cursor/mcp.json
   • Claude Desktop: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS)

   Example:

   {
     "mcpServers": {
       "gitlab-mr-comments": {
         "command": "node",
         "args": ["/absolute/path/to/gitlab-mcp/dist/server.js"],
         "env": {
           "GITLAB_TOKEN": "glpat_your_token_here"
         }
       }
     }
   }
   

2. Restart Your Client: After adding/changing the token, you MUST completely restart Cursor or Claude Desktop

3. Check Token Format: Ensure the token starts with glpat- and has no extra spaces or quotes

4. Note: A .env file in the project directory is NOT used when running as an MCP server. The token must be in the MCP client's config file.

"Authentication failed"

Cause: Invalid or missing token, insufficient permissions

Solution:

• Verify GITLAB_TOKEN is set correctly
• Ensure token has read_api scope
• Check token hasn't expired
• Verify token has access to the project

"Project or MR not found"

Cause: Incorrect project path or MR number

Solution:

• Use the project path (e.g., my-org/my-project), not the numeric ID
• Use the MR IID (the !123 number visible in the URL), not the internal ID
• Ensure your token has access to the project

"Rate limit exceeded"

Cause: Too many requests to GitLab API

Solution:

• Wait a moment before retrying
• Use onlyUnresolved filter to reduce requests
• Set includeOverviewNotes: false if not needed
• For GitLab.com: free tier = 300 requests/minute

"Request timed out"

Cause: Large MR or slow network

Solution:

• Increase REQUEST_TIMEOUT environment variable
• Use filters to reduce data volume
• Check network connectivity to GitLab instance

Server not showing up in Cursor/Claude

Cause: Configuration or path issues

Solution:

• Verify absolute path to dist/server.js is correct
• Check JSON syntax in config file
• Restart Cursor/Claude Desktop after config changes
• Check logs: Cursor logs in ~/.cursor/logs, Claude logs in ~/Library/Logs/Claude

"Tools not found" or "What tools are available?"

Cause: AI agent can't discover the gitlab_get_mr_comments tool

Solution:

1. Verify server is connected:

   • Check MCP server status in your IDE (usually in settings/extensions)
   • Look for "gitlab-mr-comments" in the connected servers list
   • If not connected, see "Server not showing up" above

2. The tool name is: gitlab_get_mr_comments

   • You can tell your agent: "Use the gitlab_get_mr_comments tool to fetch comments from MR !530 in project zapier/team-sprout/templates"

3. Check server logs:

   • Look for "GitLab MR Comments tool registered successfully" message
   • If missing, the server may not have started properly

4. Restart both IDE and try again:

   • Sometimes tool discovery needs a fresh connection

Development

Run in Development Mode

npm run dev

Run Tests

npm test

Generate JSON Schema

npm run build
node scripts/generate-schema.ts

Linting

npm run lint
npm run format

Security

Token Management

• ✅ DO: Use tokens with read_api scope (least privilege)
• ✅ DO: Store tokens in environment variables or secure config files
• ❌ DON'T: Commit tokens to version control
• ❌ DON'T: Share tokens publicly

Read-Only Guarantee

This server is explicitly designed to be read-only:

• ✅ GitLab client only implements GET requests
• ✅ No POST, PUT, PATCH, or DELETE methods exist
• ✅ Recommended token scope is read_api (read-only)
• ✅ Integration tests verify no mutation endpoints are called

Data Privacy

• All data is processed in-memory (no disk writes)
• No caching or persistent storage
• Secrets are automatically redacted from logs
• No external services contacted (direct GitLab API only)

Architecture

AI Agent (Cursor/Claude)
        ↓ stdio (MCP Protocol)
MCP Server
        ↓ HTTPS (GET only)
GitLab REST API

See for detailed architecture documentation.

Performance

Typical Performance (GitLab.com, US region):

• ≤ 2s p50 latency for MRs with ≤ 500 comments
• ≤ 5s p95 latency

Optimization Tips:

• Use onlyUnresolved to reduce data volume
• Set includeOverviewNotes: false if not needed
• Use perPage: 100 (maximum) to minimize roundtrips

Contributing

Contributions are welcome! Please read the system design document and follow the existing code patterns.

Key Principles

1. Read-Only: Never add write operations
2. Type Safety: Use TypeScript and Zod for validation
3. Error Handling: Provide actionable error messages
4. Testing: Add tests for new functionality
5. Documentation: Update README and examples

License

MIT License - see file for details.

Support

• Issues: https://github.com/mpaarating/gitlab-mcp/issues
• Documentation: See directory
• PRD: See
• System Design: See

Acknowledgments

Built with:

• Model Context Protocol SDK
• GitLab REST API
• TypeScript, Zod, undici

Made with ❤️ for AI-powered code review workflows