GitLab

Created By
modelcontextprotocola year ago
GitLab API, enabling project management
Overview

what is GitLab MCP Server?

GitLab MCP Server is an API that enables project management and file operations through the GitLab platform. It facilitates various Git-related tasks using a user-friendly interface.

how to use GitLab MCP Server?

To use the GitLab MCP Server, create a Personal Access Token on GitLab, configure your Claude Desktop application to include your token and GitLab API URL, and employ the various API endpoints for specific tasks like creating projects and managing files.

key features of GitLab MCP Server?

  • Automatic Branch Creation: Automatically creates branches if they do not exist during file operations.
  • Comprehensive Error Handling: Provides clear error messages for common issues encountered.
  • Git History Preservation: Maintains Git history accurately without the need for force pushing.
  • Batch Operations Support: Allows both single-file and multi-file operations.

use cases of GitLab MCP Server?

  1. Managing GitLab project repositories programmatically.
  2. Automating file creation and updates across multiple GitLab projects.
  3. Facilitating team collaboration through issue and merge request management.

FAQ from GitLab MCP Server?

  • How do I create a Personal Access Token?

Visit User Settings > Access Tokens in GitLab to generate a token with the necessary scopes.

  • Is there a limit on the number of operations I can perform?

There may be rate limits based on your GitLab account type. Monitor your API usage to avoid exceeding limits.

  • Can I use GitLab MCP Server for self-hosted GitLab instances?

Yes! You can configure the GITLAB_API_URL environment variable to point to your self-hosted instance.

Server Config

{
  "mcpServers": {
    "gitlab": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-gitlab"
      ],
      "env": {
        "GITLAB_PERSONAL_ACCESS_TOKEN": "<YOUR_TOKEN>",
        "GITLAB_API_URL": "https://gitlab.com/api/v4"
      }
    }
  }
}
Project Info
Featured
Created At
a year ago
Updated At
a year ago
Author Name
modelcontextprotocol
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago