GitLab MCP Server

Created By
yoda-digitala year ago
Enhanced MCP server for GitLab: group projects listing and activity tracking
Overview

What is GitLab MCP Server?

GitLab MCP Server is an enhanced Model Context Protocol (MCP) server designed for interacting with the GitLab API, providing features for group projects listing and activity tracking.

How to use GitLab MCP Server?

To use the GitLab MCP Server, install the dependencies, build the server, and start it. You can then integrate it with MCP-enabled applications by adding it to your MCP configuration.

Key features of GitLab MCP Server?

  • Create or update files in GitLab repositories
  • Search for GitLab projects using keywords
  • Create new GitLab repositories
  • Retrieve file contents from repositories
  • Push multiple files in a single commit
  • Create issues and merge requests
  • List group projects and track project activities

Use cases of GitLab MCP Server?

  1. Organization-wide project discovery and management
  2. CI/CD integration across multiple repositories
  3. Activity monitoring for commits, issues, and merge requests
  4. Code review and analysis of commit history
  5. Issue tracking and management

FAQ from GitLab MCP Server?

  • Can I use this server for all GitLab projects?

Yes! It supports all GitLab projects as long as you have the necessary permissions.

  • Is there a cost to use GitLab MCP Server?

No! It is free to use and open-source.

  • What programming language is used for this server?

The server is built using JavaScript.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
yoda-digital
Star
6
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