mcp
connectsgitlab.com
Official GitLab MCP Server
https://gitlab.com/api/v4/mcpOAuthlast checked 24 Aug 2026spoke MCP on 3 of 3 checks (30 days)initialize in 408 msHow to authenticate
Checked against the endpoint by our probe on 24 Aug 2026. These are the capabilities the server advertises, not a prediction about any particular client.
| Scheme | OAuth |
|---|---|
| Issuer | https://gitlab.com |
| Dynamic client registration | ✓Advertised (RFC 7591) |
| Client ID Metadata Document | ✕Not advertised |
| PKCE | ✓plain, S256 |
| Grant types | authorization_code, client_credentials, device_code, refresh_token |
| Scopes | api, read_api, read_user, create_runner, manage_runner, k8s_proxy, self_rotate, mcp, mcp_orbit, read_repository, write_repository, read_registry, write_registry, read_virtual_registry, write_virtual_registry, read_observability, write_observability, ai_features, sudo, admin_mode, read_service_ping, openid, profile, email, ai_workflows, user:* |
| Protected-resource metadata | ✓Published (RFC 9728) |
| Anonymous access | Refused — credentials required |
Contract history
No contract recorded yet — the server has not answered an anonymous connection.
Run this server? A verified owner can publish snapshots with their own credentials, and the contract history starts here, marked owner-reported.
mcpi-cli publish https://gitlab.com/api/v4/mcpGet alerted when this contract changes
Depend on this server? Leave an email. No contract is on record here yet, so alerts can only start once one is published — and alerts are being built; signing up is what tells us to hurry.
Prefer a feed reader? This page's contract changes are also an Atom feed.
Status badge
Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.
[](https://mcpi.app/servers/com-gitlab-mcp)Own this server?
Sign in to claim this listing by proving control of the endpoint.