Ctrlk
Go to WebsiteLoginGet a Demo
For the complete documentation index, see llms.txt. This page is also available as Markdown.

GitLab

Connect your company's GitLab to Cakewalk so agents can work with issues, merge requests, and repositories through the gateway.

Connect your company's GitLab to Cakewalk's MCP Gateway. Every agent tool call against GitLab passes through the gateway and is evaluated against your Policies.

GitLab lists its MCP server as Beta.

Setup Flow: Sign in and go

GitLab supports Dynamic Client Registration, so there is no OAuth app to create and no Client ID or Secret to paste. An Admin enables the Connection, the employee signs in to GitLab, approves the consent screen, and the Connection goes live.

Before the sign in works, someone with the right role in GitLab has to turn the MCP server on. That is the only manual part, and it happens once on the GitLab side. See Step 1.

Requirements

  • A GitLab Premium or Ultimate subscription. The MCP server is not available on Free.

  • For GitLab.com: the Owner role on the top-level group, to turn on beta and experimental features.

  • For GitLab Self-Managed or Dedicated: administrator access to the instance.

About Scopes

The GitLab MCP server uses a single scope, mcp. The employee grants it once on the GitLab consent screen during sign in. What the agent can then do (read or write issues, merge requests, repositories) follows the signing-in employee's own GitLab permissions, and every call is still gated by your Cakewalk Policies.

Step 1: Turn on the GitLab MCP Server

The MCP server ships as a beta feature and is off by default. Turn it on once in GitLab.

On GitLab.com (Owner role on the top-level group):

  1. Go to your top-level group.

  2. Select Settings > GitLab Duo.

  3. Select Change configuration.

  4. Under Feature preview, select Turn on experiment and beta GitLab Duo features.

  5. Save changes.

The setting cascades to all projects in the group.

On GitLab Self-Managed or Dedicated (administrator access):

  1. Confirm GitLab Duo is turned on for the instance.

  2. On the Admin area, select Settings > GitLab Duo.

  3. Expand Change configuration.

  4. Under Feature preview, select Use experiment and beta GitLab Duo features.

  5. Save changes.

Step 2: Enable the Connection in Cakewalk

  1. Open https://app.getcakewalk.io.

  2. Go to All Connections.

  3. Find GitLab and enable it.

  4. On GitLab Self-Managed or Dedicated, set the MCP server URL to your instance: https://<your-gitlab-host>/api/v4/mcp. On GitLab.com the URL is https://gitlab.com/api/v4/mcp.

Step 3: Sign In

From an agent platform connected to Cakewalk, the employee connects GitLab and signs in. GitLab opens a browser window, the employee approves the mcp consent screen, and the Connection becomes Active. No credentials change hands.

Verifying It Works

The GitLab Connection card flips to Active on All Connections. From an agent platform connected to Cakewalk, ask the agent "Which MCP server version are you using?" or ask it to list your open merge requests on a project. If GitLab returns the data, the Connection is live.

Troubleshooting

  • 404 Not Found when the server starts, or POST /api/v4/mcp returns 404 after sign in. GitLab Duo, or beta and experimental features, are turned off. Recheck Step 1. On Self-Managed, also confirm GitLab Duo is turned on for the instance.

  • "Server's protocol version is not supported: 2025-06-18." The GitLab instance is on 18.6 or earlier, where the MCP client library is incompatible. Upgrade GitLab, or have the agent platform update its MCP client.

  • Sign in succeeds but no GitLab tools appear. Confirm the signing-in employee has access to at least one active project, and that their GitLab permissions cover what the agent is trying to do.

Learn More

PreviousDropboxNextGoogle Gmail

Last updated

Was this helpful?