Developer tools GitLab
GitLab MCP server
Let an authorised agent work with GitLab repositories, issues, merge requests and pipeline information through MCP.
Source review: 2026-10-18 · Imported: 1 November 2026
A practical starting point
What could you build?
A development assistant can gather pipeline failures and the associated merge request context.
Before you connect
Grant the narrowest suitable token or OAuth scopes. Write actions should follow your project’s normal review process.
Capabilities & requirements
Dated specifications from the licensed source dataset. “Not published” indicates missing information, rather than confirmed absence.
| Capability | Details and source |
|---|---|
| Status | Generally available (GitLab 19.5) Experiment in 18.3, beta in 18.6, GA in 19.5. Source (external) · Verified 2026-10-18 on https://docs.gitlab.com/user/model_context_protocol/mcp_server/ |
| API key required | OAuth (mcp scope) or fine-grained PAT Our unauthenticated request returned HTTP 401 with a Bearer challenge for scope mcp. Source (external) · Verified 2026-10-18 by test request to https://gitlab.com/api/v4/mcp |
| Free tier | On GitLab Free Moved from Premium to Free in 19.2; some toolsets need paid features. Source (external) · Verified 2026-10-18 on https://docs.gitlab.com/user/model_context_protocol/mcp_server/ |
| Rate limit | Free 60/min; Premium+ 600/min Per user on GitLab.com across all clients (19.5, behind feature flags); self-managed admins set their own. Source (external) · Verified 2026-10-18 on https://docs.gitlab.com/user/model_context_protocol/mcp_server/ |
| Official MCP server | Built in, /api/v4/mcp Streamable HTTP with OAuth dynamic client registration; listed as com.gitlab/mcp in the official registry. Source (external) · Verified 2026-10-18 on https://docs.gitlab.com/user/model_context_protocol/mcp_server/ |
| Official SDK | Not applicable Any MCP client connects directly; GitLab’s REST API remains available for bulk jobs. Source (external) · Verified 2026-10-18 on https://docs.gitlab.com/user/model_context_protocol/mcp_server/ |
| Data license / terms | GitLab subscription terms Your own project data; GitLab’s terms govern the service. Source (external) · Verified 2026-10-18 on https://about.gitlab.com/terms/ |
| Commercial use allowed | Your own projects MCP access is a feature of your GitLab plan; the docs state no separate usage restriction. Source (external) · Verified 2026-10-18 on https://docs.gitlab.com/user/model_context_protocol/mcp_server/ |
| CORS / browser use | Access-Control-Allow-Origin: * Preflight returned 200 with *. Source (external) · Verified 2026-10-18 by test request to https://gitlab.com/api/v4/mcp |
| Freshness / coverage | Live project data Tools read and write your GitLab data directly. Source (external) · Verified 2026-10-18 on https://docs.gitlab.com/user/model_context_protocol/mcp_server/ |
Operational reference
Additional facts and qualifications retained from AgentAPIList’s CC BY 4.0 dataset, with provider references.
Price
Available on GitLab Free, Premium and Ultimate, on GitLab.com, Self-Managed and Dedicated. The MCP server moved from Premium to Free in GitLab 19.2. Some toolsets need paid features (Duo Agent Platform, Ultimate security tools).
Provider reference (external)API key / auth
OAuth access token with the mcp scope (clients get it through the OAuth flow) or a fine-grained personal access token with the MCP tool resource and Execute permission. Legacy, project and group tokens are rejected with 403 insufficient_scope. Our unauthenticated request on 2026-10-18 returned HTTP 401 with a Bearer challenge for scope mcp.
Provider reference (external)Rate limit
GitLab.com, per user across all clients: 60 MCP requests a minute on Free, 600 on Premium and Ultimate (introduced in 19.5 behind feature flags). Over the limit: HTTP 429 with Retry-After. Self-managed admins set their own limit.
Provider reference (external)Terms
GitLab’s subscription terms govern GitLab.com and licensed instances; the data is your own projects’.
Provider reference (external)Status
Generally available since GitLab 19.5 (experiment in 18.3, beta in 18.6). On GitLab.com the top-level group must allow MCP server access.
Provider reference (external)Registry listing
Listed in the official MCP Registry as com.gitlab/mcp with remote https://gitlab.com/api/v4/mcp.
Provider reference (external)Setup references
HTTP request example
Adapted from the attributed source dataset. Review before running; these examples were not executed by Tech in General.
# Not run: needs an OAuth token (mcp scope) or a fine-grained personal access token
curl -sS -X POST https://gitlab.com/api/v4/mcp \
-H "Authorization: Bearer $GITLAB_MCP_TOKEN" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-H "X-Gitlab-Enabled-Mcp-Server-Toolsets: core,merge_requests" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'Agent connection example
Adapted from the attributed source dataset. Review before running; these examples were not executed by Tech in General.
// Claude Code (OAuth opens in the browser on first use):
// claude mcp add -s user --transport http GitLab https://gitlab.com/api/v4/mcp \
// --header "X-Gitlab-Enabled-Mcp-Server-Toolsets: core,merge_requests"
// Codex:
// codex mcp add GitLab --url "https://gitlab.com/api/v4/mcp" && codex mcp login GitLab
// Cursor .cursor/mcp.json
{
"mcpServers": {
"GitLab": {
"type": "http",
"url": "https://gitlab.com/api/v4/mcp",
"headers": { "X-Gitlab-Enabled-Mcp-Server-Toolsets": "core,merge_requests" }
}
}
}A tool schema needs an HTTP implementation; it does not by itself install an MCP server. Keep credentials out of browser code.
Other connections to explore
- cve.now API + MCP (external)
- GitHub MCP server (external)
- Gitea MCP (external)
- Official MCP Registry API (external)
- App Store Connect API (external)
- Stack Exchange API (external)
Source & reuse
Download the complete licensed source snapshot (JSON), including the original source’s caveats, alternative notes and examples.