Our grade: 4 checks
Based on public data, not a full audit. See how we grade. Something changed? Request a re-grade.
Community rating
- 5 2
- 4 3
- 3 1
- 2 0
- 1 0
Trust in production
- Trust it - 67%
- With caveats - 17%
- Wouldn't - 17%
83% would recommend this server
How reviewers scored it
- Setup & docs 4.0
- Auth experience 3.7
- Reliability 4.2
- Maintainer responsiveness 4.0
Why it got an A
Built into GitLab at /api/v4/mcp, generally available since 19.5 on all tiers for GitLab.com, Self-Managed and Dedicated. It uses OAuth 2.0 with dynamic client registration and a dedicated mcp scope. Two MCP bugs (a token-scope bypass and a cross-user search leak) were fixed in the patch release that disclosed them. Default toolsets can comment, commit, merge MRs and run pipelines, and GitLab warns that issue and MR text can carry prompt injection, so limit toolsets with the X-Gitlab-Enabled-Mcp-Server-Toolsets header. Biggest deduction: one mcp scope covers every tool, including writes, and there is no read-only mode.
How to connect
// ~/.cursor/mcp.json
{ "mcpServers": { "GitLab": { "type": "http", "url": "https://<gitlab.example.com>/api/v4/mcp" } } }claude mcp add -s user --transport http GitLab https://<gitlab.example.com>/api/v4/mcp// claude_desktop_config.json (stdio via mcp-remote, Node.js 20+)
{ "mcpServers": { "GitLab": { "command": "npx",
"args": ["-y", "mcp-remote", "https://<gitlab.example.com>/api/v4/mcp"] } } }Is GitLab MCP Server safe?
Is GitLab MCP Server safe to use?
GitLab MCP Server grades A (strong public trust signals). Login is required, but access is coarse: one sign-in or key covers more than your agent needs, so grant the narrowest account you can.
Does GitLab MCP Server have known vulnerabilities?
Not in our current data: it has no open CVEs or advisories. We re-check as new ones are published.
Does GitLab MCP Server support authentication?
Yes. It requires a login, so access can be tied to a person or a scoped key.
Alternatives in Developer Tools
- A Atlassian Rovo MCP ServerOfficial hosted Atlassian server for Jira, Confluence, Jira Service Management, Compass, Bitbucket, Loom, Goals, Projects, and Teams, with OAuth 2.1 sign-in.
- A Buildkite MCP ServerOfficial Buildkite server for pipelines, builds, jobs, logs, annotations, and Test Engine data, hosted or local.
- A Dynatrace Remote MCP ServerDynatrace's hosted MCP server, running inside your Dynatrace SaaS environment, to run and explain DQL, look into problems, vulnerabilities and Kubernetes events, and forecast time series.
- A GitHub MCP ServerOfficial GitHub server for repos, issues, pull requests, Actions, and code security, hosted or local.
- A Honeycomb MCPHoneycomb's hosted MCP server to query datasets, read traces, run BubbleUp, and read or change boards, triggers and SLOs, with per-resource OAuth scopes.
Embed this badge
[](https://trustedmcp.io/servers/gitlab-mcp-server)<a href="https://trustedmcp.io/servers/gitlab-mcp-server"><img src="https://trustedmcp.io/badge/gitlab-mcp-server.svg" alt="TrustedMCP grade A" height="80"></a>Community reviews
Earned a permanent spot in my config
Clear tool names, sensible outputs, very few surprises. Scoped the token to just what the agent needs and it respected that. Read-only mode is the first thing I enable, and it covers most of what I need. Keep permissions tight and it is a good tool.
Used for Pairing with Claude Code on a monorepo
- Setup & docs 5/5
- Auth experience 4/5
- Reliability 5/5
- Maintainer responsiveness 4/5
Surprisingly polished
Our agents call this dozens of times a day. Nice that it supports both stdio and HTTP, I use stdio locally and HTTP for the shared agent. Read-only mode is the first thing I enable, and it covers most of what I need.
Used for Scripting routine maintenance tasks
- Setup & docs 5/5
- Auth experience 3/5
- Reliability 5/5
- Maintainer responsiveness 4/5
Recommended it to two teams already
Started with it as an experiment, now it is a fixture. Turned on read-only mode on day one, highly recommend doing the same. Auth is handled properly, and revoking access later was one click. It is in our production agent and I sleep fine.
Used for Keeping project tickets in sync with code changes
- Setup & docs 3/5
- Auth experience 4/5
- Reliability 3/5
- Maintainer responsiveness 4/5
Solid and well behaved
Hooked GitLab MCP Server into Claude Code and it worked on the first try. The scope options are worth reading carefully, the defaults are broader than I wanted. Sign-in flow was painless and I never had to paste a key into a config file.
Used for Automating release notes
- Setup & docs 5/5
- Auth experience 4/5
- Reliability 5/5
- Maintainer responsiveness 4/5
Promising, a bit raw
It does the job, but it took some tweaking. Sign-in flow was painless and I never had to paste a key into a config file. Keeping it to local experiments for now.
Used for Onboarding new devs with an agent that answers repo questions
- Setup & docs 2/5
- Auth experience 3/5
- Reliability 3/5
- Maintainer responsiveness 5/5
The GitLab integration I wanted
I use this almost daily. Filed an issue and got a reply within two days.
Used for Internal developer assistant
- Setup & docs 4/5
- Auth experience 4/5
- Reliability 4/5
- Maintainer responsiveness 3/5
Write a review
Ran this server? Tell other teams how it went. You get one review per server. We email you a link to confirm it, then an editor checks it before it goes up. We never show your email.