GitLab Self-Managed MCP server
by GitLab
Projects, issues, merge requests and pipelines on your own GitLab.
What it can do
- Get merge requests
- Manage work items
- Check CI pipelines
- List vulnerabilities
Through MCP1, every tool call is checked against your groups and rules, and recorded in the audit log.
How it connects
Authenticate with GitLab and approve MCP1. No token to copy; MCP1 keeps the connection sealed and refreshes it.
Self-Managed and Dedicated, GitLab 18.6 or later. An admin turns on MCP client access first.
- Endpoint
https://{host}/api/v4/mcp- Transport
- Streamable HTTP
- Docs
- docs.gitlab.com
With MCP1
GitLab Self-Managed for the whole team, behind one URL
- 01
Install it once
An admin adds GitLab Self-Managed from the MCP1 catalog. Its authentication or token stays sealed in MCP1, never on a laptop.
- 02
Decide who gets what
Open it to groups, fully or read-only, and set rules per tool. Destructive tools can need an admin.
- 03
Connect any client
Claude, Cursor, ChatGPT, Codex and the rest connect one gateway URL and sign in with their own account.
More for engineering
See all engineering servers- GitHubEngineering
Repositories, issues, pull requests, code search and Actions.
Token - GitLabEngineering
Projects, issues, merge requests and pipelines on GitLab.com.
One-click auth - LinearEngineering
Find, create and update issues, projects and comments.
One-click auth - SentryEngineering
Search errors, triage issues and analyze performance.
One-click auth - VercelEngineering
Projects, deployments, runtime logs and the Vercel docs.
One-click auth - NetlifyEngineering
Create, deploy and manage Netlify projects.
One-click auth