Gitlab Api

CLI or API | MCP

Documentation — Installation, deployment, usage across the API, CLI, and MCP backing GitLab instance are maintained in the official documentation.

---

Overview

Gitlab Api is a production-grade Agent and Model Context Protocol (MCP) server designed to interface directly with GitLab API + MCP Server.

---

Key Features

• Consolidated Action-Routed MCP Tools: Minimizes token overhead and eliminates tool bloat in LLM contexts by grouping methods into optimized, togglable tool modules.
• Enterprise-Grade Security: Complete support for Eunomia policies, OIDC token delegation, and granular execution context tracking.
• Native Telemetry & Tracing: Out-of-the-box OpenTelemetry exports and native Langfuse tracing.

---

CLI or API

This agent wraps the GitLab API + MCP Server API. The operator can interact with it programmatically or via its integrated execution entrypoints.

Detailed instructions on how to use the underlying API wrappers, extended schema bindings, and developer SDK references are maintained in docs/index.md.

---

MCP

This server use dynamic Action-Routed tools to optimize token overhead and maximize IDE compatibility.

Tool surface

Every GitLab operation is one typed tool (gitlab_get_branches, gitlab_create_merge_request, ...) with explicit parameters. There are no action-routed tools. Destructive tools take confirm=true.

Available MCP Tools

Auto-generated from the live MCP server — do not edit by hand.

This is the beginning of the README. Read the rest at the original. Read the full README ↗