GGitLab MCP (official, remote)

Vendor-hosted
Generally available (GitLab 19.5).
Sources: https://docs.gitlab.com/user/model_context_protocol/mcp_server/ · https://docs.gitlab.com/releases/19/gitlab-19-5-released/ · https://about.gitlab.com/blog/mcp-server-ga/ · https://registry.modelcontextprotocol.io/v0/servers?search=com.gitlab/mcp

Transport: Needs credentials to confirm transport · probed 2026-10-28 without credentials

Score 65/100 · Tools — · Token cost — · Compare · Last tested 2026-10-24 · Server version not reported · Remote endpoint https://gitlab.com/api/v4/mcp (streamable-http)

Summary: GitLab MCP (official, remote) requires credentials or a backing service before it will list tools.

Evidence summary

Handshake

auth-gated

Tools listed

—

Context cost

Not measured ranking

Login

Needs OAuth sign-in

Tested

2026-10-24

Test results

Local-model readiness

Not yet tested (no tools/list response without credentials).

What we tested and what we didn't

Methodology: how we test (vendor-hosted rule). A high score means it responds and its vendor documents and dates it, not that it is safe to give it access to your data.

{
  "name": "gitlab-remote",
  "version": null,
  "registry": "remote",
  "status": "auth-gated",
  "tested": "2026-10-24",
  "tools_count": null,
  "tools_schema_tokens_est": null,
  "deprecated": false,
  "archived": null,
  "tests": {
    "install": [
      "pass",
      20,
      "Endpoint https://gitlab.com/api/v4/mcp reachable over streamable-http (HTTP 401) in 3.2s; no install step for remote servers."
    ],
    "handshake": [
      "auth-gated",
      5,
      "Needs credentials: vendor-hosted, OAuth sign-in required. HTTP 401 with OAuth challenge (WWW-Authenticate resource_metadata https://gitlab.com/.well-known/oauth-protected-resource/api/v4/mcp; metadata lists authorization server https://gitlab.com). We do not sign in; not counted as working until a credentialed test exists."
    ],
    "maintenance": [
      "pass",
      25,
      "Vendor-hosted rule: scored from vendor release note 2026-10-15 (https://docs.gitlab.com/releases/19/gitlab-19-5-released/), 9 days before test. Registry (corroboration only, not scored): com.gitlab/mcp 0.0.1 published 2025-10-02."
    ],
    "docs": [
      "pass",
      15,
      "official MCP docs page; states the endpoint URL; client setup instructions. Vendor-hosted rule: scored from the vendor's official MCP docs (https://docs.gitlab.com/user/model_context_protocol/mcp_server/)."
    ],
    "license": [
      "fail",
      0,
      "Vendor-hosted service with no public repo: no license to cite, so 0 (rule: no points without a cited source)."
    ]
  }
}

Install

https://gitlab.com/api/v4/mcpCopy

Tools listed

Not available (handshake did not complete without credentials).

Quick config

{
  "mcpServers": {
    "gitlab-mcp-official-remote": {
      "type": "http",
      "url": "https://gitlab.com/api/v4/mcp"
    }
  }
}

Add to config Opens the config generator with this server selected.

{
  "mcpServers": {
    "gitlab-mcp-official-remote": {
      "type": "http",
      "url": "https://gitlab.com/api/v4/mcp"
    }
  }
}

Related: MCP servers that need an OAuth sign-in · How to secure AI API keys

FAQ

Is GitLab MCP (official, remote) deprecated?

No. gitlab-remote was not deprecated or archived when we last tested it on 2026-10-24.

What replaces GitLab MCP (official, remote)?

Nothing; GitLab MCP (official, remote) is not deprecated as of 2026-10-24.

Does GitLab MCP (official, remote) need an API key?

Not an API key: it needs an OAuth sign-in. Without signing in, the endpoint returned HTTP 401 with an OAuth challenge and did not list tools.

Embed the badge

Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.

Copy HTML

Copy Markdown Claim this listing · Report an issue