GitLab MCP Server

Created By
TheRealChrisThomasa year ago
Gitlab MCP Server
Overview

What is GitLab MCP Server?

GitLab MCP Server is a tool designed to enhance project management and file operations within the GitLab API, allowing users to automate various tasks related to GitLab projects.

How to use GitLab MCP Server?

To use the GitLab MCP Server, you can install it via NPX or globally using npm. For NPX, run npx @therealchristhomas/gitlab-mcp-server. For global installation, use npm install -g @therealchristhomas/gitlab-mcp-server followed by gitlab-mcp.

Key features of GitLab MCP Server?

  • Automatic branch creation for file operations
  • Comprehensive error handling with clear messages
  • Preservation of Git history during operations
  • Support for batch operations on files
  • Project workflow management including labels and milestones
  • Repository management capabilities
  • File operations such as create, update, and retrieve
  • Issue and merge request management

Use cases of GitLab MCP Server?

  1. Automating project management tasks in GitLab.
  2. Managing multiple projects with group milestones.
  3. Streamlining file operations and version control in GitLab repositories.

FAQ from GitLab MCP Server?

  • What is the purpose of the GitLab MCP Server?

It automates project management and file operations within GitLab, enhancing productivity.

  • Is it necessary to have a GitLab account to use this server?

Yes, a GitLab account with appropriate permissions is required to access the API.

  • Can I use it for self-hosted GitLab instances?

Yes, you can configure the API URL for self-hosted instances.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
TheRealChrisThomas
Star
0
Language
TypeScript
License
MIT 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