GitLab MCP Server Status
Is the GitLab MCP server up? Live check of gitlab.com, plus the fixes that solve most connection problems.
The check above sends the official GitLab MCP endpoint https://gitlab.com/api/v4/mcp the first request every MCP client sends. Up with HTTP 401 is the normal state: the server answers and asks for sign-in. If it is up and your connector still fails, work through the fixes below.
| MCP server URL | https://gitlab.com/api/v4/mcp |
| Transport | Streamable HTTP |
| Authentication | sign-in or token (HTTP 401 without one) |
| Product | GitLab |
GitLab MCP not working? Fix it in this order
- Look at the live check above. If it says Down, the problem is on GitLab's side and usually clears up on its own; check again in a few minutes.
- Use the current URL:
https://gitlab.com/api/v4/mcp. - Sign in again or renew the token. GitLab answers requests without credentials with 401, so your client has to sign in or send a token from your GitLab account. If it worked before, the sign-in probably expired or was revoked: remove the connector, add it again and complete the sign-in. In Claude Code:
claude mcp remove gitlabandclaude mcp add --transport http gitlab https://gitlab.com/api/v4/mcp. - Check the network. VPNs, company proxies and firewalls can block
gitlab.com. Try another network to rule it out. - Update the client. Older clients only speak stdio or the old SSE transport. Current Claude, ChatGPT, Cursor and VS Code versions support remote servers over HTTP.
- Test it outside your client. Paste the URL into our MCP Server Tester to see exactly what the server answers.
Add GitLab MCP to your client
Claude (claude.ai, desktop): Customize, Connectors, + Add, Add custom connector, paste https://gitlab.com/api/v4/mcp. Claude Code: claude mcp add --transport http gitlab https://gitlab.com/api/v4/mcp. Cursor: { "mcpServers": { "gitlab": { "url": "https://gitlab.com/api/v4/mcp" } } }. VS Code: { "servers": { "gitlab": { "type": "http", "url": "https://gitlab.com/api/v4/mcp" } } }.
Status of the other servers: MCP server status overview.
How it works
- Check the live status Up, including HTTP 401, means the server answers.
- Use the current URL https://gitlab.com/api/v4/mcp
- Reconnect Remove the connector, add it again and sign in.
FAQ
Is GitLab MCP down right now?
The live check at the top of this page tests https://gitlab.com/api/v4/mcp at most every five minutes. Up, including HTTP 401, means the server is answering.
What is the GitLab MCP server URL?
https://gitlab.com/api/v4/mcp.
Why is GitLab MCP not working in Claude or Cursor?
Most often an expired or revoked sign-in, an outdated URL or a blocked network. Remove the connector, add it again with the current URL and sign in again.
Why does GitLab MCP return 401?
Without a valid token every request gets 401, which is how the client knows it has to sign in. If you see 401 after signing in, the token expired or was revoked; reconnect.