← Explore all mcp servers

REPOSITORY COLLABORATION / GitLab

GitLab MCP

Connect a client to project, repository, review and CI context on GitLab.com or an enabled GitLab instance.

“Access GitLab project information.”

01 / THE REASONING

Why this made the selection.

  • First-party OAuth exposes the GitLab resources the signed-in user may access.
  • HTTP setup supports GitLab.com and supported self-managed or dedicated installations.
  • GitLab’s MCP page says tools are listed only when the instance license includes the feature, and that listing a tool does not grant access.
  • Each call still checks project and namespace permissions, and a pre-registered OAuth application is required where dynamic client registration is turned off.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • Current GitLab MCP setup, enablement requirements, transport/authentication and toolset documentation.
  • GitLab MCP tools reference.
  • https://docs.gitlab.com/user/model_context_protocol/mcp_server/
  • https://docs.gitlab.com/user/model_context_protocol/mcp_server_tools/
  • Round 2 reread of acquired publisher setup and permission evidence; see immutable wave review.

Our findings

  • HTTP connects directly to /api/v4/mcp; mcp-remote is an optional stdio bridge, not the hosted server implementation.
  • Toolset and individual-tool selection headers combine as a union. Existing user permissions still apply.
  • GitLab documents an OAuth-based MCP server where every user still authorizes and receives their own access token. A shared application is the client identity, not a shared credential.
  • Listing a tool does not grant access. Each tool checks project and namespace permissions, and users can access only data they are permitted to.
  • Where an administrator turns off dynamic client registration, MCP clients cannot register applications automatically. One documented tool requires permission to push to the source branch of the merge request.
  • The server accepts OAuth tokens with mcp scope or fine-grained PATs with MCP Execute permission; legacy/project/group access tokens are rejected.

Not established by this review

  • Server launch, authenticated tool calls, and release-to-source parity were not tested.
  • The resource was not executed and its tools were not called.
  • The server was not called. A source review is not a runtime or security certification.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Connect a server deliberately.

Upstream setup instructions ↗

DOCUMENTED COMMAND

claude mcp add -s user --transport http GitLab https://<gitlab.example.com>/api/v4/mcp

Copying does not execute this command. It may retrieve a newer version than the reviewed source.

  1. Enable MCP access for the GitLab.com group or self-managed instance.
  2. Replace <gitlab.example.com> with gitlab.com, or with your instance URL, as the page instructs. The -s user scope makes the server available in every project. The command was not run.
  3. Use /mcp in Claude Code to authorize GitLab, then inspect available tools and review mutations.

Before you start

  • GitLab account with access to the relevant projects.
  • MCP enabled by the group or instance administrator; an OAuth-capable client.

Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

{
  "mcpServers": {
    "GitLab": {
      "type": "http",
      "url": "https://<gitlab.example.com>/api/v4/mcp"
    }
  }
}

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. https://docs.gitlab.com/user/model_context_protocol/mcp_server/

    Supports: summary, upstreamDescription, whySelected, bestFor, limitations, install, access, compatibility, transports, review

  2. https://docs.gitlab.com/user/model_context_protocol/mcp_server_tools/

    Supports: summary, whySelected, bestFor, access, review

Evidence & Ask