How to connect GitLab to Cursor

  • Cursor gets 30 GitLab tools through one Metorial MCP URL.
  • Setup is 3 steps; teammates then sign in with SSO.
  • You need Cursor with MCP support.

What Cursor can do with GitLab

Ask your agent in plain language. Each of these maps to a real tool on the server.

  • Ask Cursor to use the browse repository tool in GitLab
  • Ask Cursor to use the manage branch tool in GitLab
  • Ask Cursor to search items in GitLab
  • Ask Cursor to use the list groups tool in GitLab
  • Ask Cursor to use the list projects tool in GitLab

Add the GitLab MCP server to Cursor

Run these once. Afterwards, everyone you give access to signs in the same way.

  1. 1. Enable GitLab in Metorial

    In your Metorial portal, enable the GitLab MCP server and sign in with the account that owns the data. Access stays governed by your team policies.

  2. 2. Add Metorial to your MCP config

    Use ~/.cursor/mcp.json for every project, or .cursor/mcp.json for one.

    {
    "mcpServers": {
    "metorial": {
    "url": "<your-magic-mcp-url>"
    }
    }
    }
  3. 3. Sign in

    Open Customize in the sidebar, find Metorial and sign in to load GitLab tools.

Give your team GitLab in Cursor

Once GitLab is enabled in Metorial, teammates sign in with SSO and get the same connection in Cursor, with only the tools their role allows.

One link covers every app you approve. See how the MCP gateway handles access, roles and audit logs for the whole company.

GitLab tools available in Cursor

Full descriptions and inputs are on the GitLab MCP server page.

  • Create Release: Create a new release for a project, or list existing releases.
  • Manage Pipeline: Trigger, retry, or cancel a CI/CD pipeline.
  • Manage Project: Create, update, fork, or delete a GitLab project.
  • Manage Issue: Create, update, close, reopen, or delete a GitLab issue.
  • List Merge Requests: List GitLab merge requests, optionally scoped to a project.
  • Manage Merge Request: Create, update, or merge a GitLab merge request.
  • List Issues: List GitLab issues filtered by project, state, labels, milestone, assignee, author, or search term.
  • List Pipelines: List CI/CD pipelines for a project.
  • Add Comment: Add a comment (note) to an issue or merge request.
  • Get Project: Retrieve detailed information about a specific GitLab project by its ID or URL-encoded path (e.g.
  • Browse Repository: Browse a project's repository tree, read file contents, or compare branches.
  • Manage Branch: List, create, or delete branches in a project repository.
  • Search: Search across GitLab for projects, issues, merge requests, milestones, code (blobs), commits, wiki content, and users.
  • List Groups: List GitLab groups accessible to the authenticated user.
  • List Projects: List GitLab projects accessible to the authenticated user.
  • And 15 more on the GitLab MCP server page.

Using GitLab tools in Cursor

What to expect once GitLab is connected.

  • Cursor picks MCP tools automatically when they are relevant, including in Plan Mode. Name a GitLab tool to steer it.
  • Cursor asks for approval before it uses an MCP tool by default. Click the arrow next to the tool name to check the arguments first.
  • Switch the Metorial server off from Customize in the sidebar without removing it.
  • Cursor shows each GitLab tool response in chat, with expandable views of the arguments and the result.

Troubleshooting Cursor

Metorial connects but tools are missing or failing
Open the Output panel (Cmd+Shift+U), choose MCP Logs, and look for authentication or connection errors.
Your company blocks the server
Enterprise admins approve remote servers in Team Settings, then MCP Configuration. Ask them to add a URL entry for your Metorial URL.
Cursor asks before every tool call
That is the default. Allowlist the Metorial tools you trust in your Run Mode settings to run them without a prompt.

Based on the Cursor MCP documentation.

Frequently asked questions

Common questions about connecting GitLab to AI agents with Metorial.

  1. Does Cursor support the GitLab MCP server?
    Yes. Cursor connects to the GitLab MCP server through its MCP config file, pointed at your Metorial URL. You need Cursor with MCP support.
  2. No. You sign in to GitLab once through Metorial, and Cursor uses that connection. No API keys go into Cursor's settings.
  3. All 30 GitLab tools your team allows, such as Create Release, Manage Pipeline, Manage Project. Admins can narrow that list per team.
  4. Yes. Role-based access control decides who can use GitLab and which of its tools appear in Cursor, and every call is logged with the person's identity.
  5. Open the Output panel (Cmd+Shift+U), choose MCP Logs, and look for authentication or connection errors.