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.
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.
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.
Not established by this review
- Server launch, authenticated tool calls, and release-to-source parity were not tested.
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.
DOCUMENTED COMMAND
claude mcp add --transport http GitLab https://gitlab.com/api/v4/mcpCopying does not execute this command. It may retrieve a newer version than the reviewed source.
- Enable MCP access for the GitLab.com group or self-managed instance.
- The command below configures Claude Code for GitLab.com; replace the hostname for your own enabled instance.
- 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.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.
- GitLab MCP setup and scope ↗Checked
https://docs.gitlab.com/user/model_context_protocol/mcp_server/
Supports: summary, upstreamDescription, whySelected, bestFor, limitations, install, access, compatibility, transports, review
- GitLab MCP tool reference ↗Checked
https://docs.gitlab.com/user/model_context_protocol/mcp_server_tools/
Supports: summary, whySelected, bestFor, access, review