Enhanced GitLab Integration for Cursor

Ideas Feature Requests
1

Feature Request: Enhanced GitLab Integration for Cursor

Current State:

  • GitLab MCP server provides basic repository operations
  • Cannot fetch merge request details (open, closed, or merged)
  • Missing parity with GitHub PR integration

Requested Features:

  1. Fetch GitLab Merge Request Details

    • View MR diffs, metadata, comments
    • Access merged/closed MRs for context
    • Similar functionality to existing GitHub PR tool

  2. Enhanced GitLab MCP Tools

    • Get MR by number/ID
    • List MRs with filters (status, author, etc.)
    • Access MR discussions and approvals

  3. Parity with GitHub Integration

    • Same level of PR/MR access across platforms
    • Consistent developer experience

Use Case:

  • Developer workflows often reference historical MRs
  • Code reviews and context from merged MRs
  • Understanding recent changes and their rationale

Business Value:

  • Improved developer productivity
  • Better code context and decision-making
  • Reduced context switching between tools

Technical Context:

  • Current GitLab MCP server lacks fetch_merge_request equivalent
  • GitHub integration already provides comprehensive PR access
  • Would enable AI assistants to provide better code context
20 Likes
2

We are also in desperate need of gitlab integration with all the new features. Can’t justify a costly migration of all our team workflows to github for the cursor features, may end up considering other options.

4 Likes
3

We also need this feature

2 Likes
4

I’d also love to see support for Background agents with Gitlab connected repos.

4 Likes
6

You can use gitlab-mcp-server, which I recently released. It’s a GitLab-compatible MCP server that allows you to view and add comments directly from tools like Cursor, without needing to jump back into the GitLab UI.

7

It’s quite unfair that Gitlab users pay the same price as Github users! We just don’t have the same options!

1 Like
8

This is not an official GitLab MCP, use with caution. As far as I know, GitLab does not provide an official MCP.

9

We also have a great need for this integration with all features mentioned. Also considering other options because of this.

10

Vote for adding GitLab support!

11

YES MY KINGDOM FOR GITLAB SUPPORT.

Cake for the entire team if you ship this in Q4 :sweat_smile:

Sidenote: we’re currently using a Frankenstein-ish solution where we auto-mirror our Gitlab repositories to Github, connect Cursor to Github and use Github Actions to mirror PRs back to Gitlab automatically.

It kind of works, but it’s quite a hassle to set up and manage. Native Gitlab support would make things so much easier for us.

2 Likes
12

Same this would be a game changer, I have considered the mirroring strategy but a huge hassle. Having gitlab support would mean we’d used the background agents more.

13

do it

14

This feature would make a huge difference to our team renewing with cursor, please do it

15

Vote for adding GitLab support!

1 Like
16

Really would like to see GitLab support. It’s preventing us from using Cursor more at this stage, since there’s a limit to how much we can use Cursor without Background/Cloud Agents running.