GitLab MCP Server

What the code does

We read the source, 5 h ago · tools taken from the live server · rules 995398eba69f

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

        dir := filepath.Join(resolve(root, opts.siteCharts), l.Code)

  cursor_headers = next_link_of(cursor_probe).select { |_name, value| value == next_cursor }.keys

  pager = %w[desc asc].flat_map do |sort|

child = spawn(binary, process.argv.slice(2), {

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

claude mcp add gitlab-mcp-server --transport http https://gitlab-mcp-server.fly.dev/

https://gitlab-mcp-server.fly.dev/

[mcp_servers.gitlab-mcp-server]
url = "https://gitlab-mcp-server.fly.dev/"

{
  "mcpServers": {
    "gitlab-mcp-server": {
      "url": "https://gitlab-mcp-server.fly.dev/"
    }
  }
}

{
  "servers": {
    "gitlab-mcp-server": {
      "type": "http",
      "url": "https://gitlab-mcp-server.fly.dev/"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

This server publishes 2 more addresses. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

Endpoints