# Indexing Gitlab Repos as additional Codebase

**URL:** <https://forum.cursor.com/t/indexing-gitlab-repos-as-additional-codebase/25634>\
**Category:** Feature Requests\
**Created:** [October 31, 2024, 1:11pm UTC](https://forum.cursor.com/t/indexing-gitlab-repos-as-additional-codebase/25634 "2024-10-31T13:11:15Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![wolfwkg](https://avatars.discourse-cdn.com/v4/letter/w/858c86/32.png) [@wolfwkg](https://forum.cursor.com/u/wolfwkg)\
**Post date:** [October 31, 2024, 1:11pm UTC](https://forum.cursor.com/t/indexing-gitlab-repos-as-additional-codebase/25634/1 "2024-10-31T13:11:15Z")

</div>

Hi folks,

My dev team and I are using GitLab as our source control system, where we manage many projects. The GitLab projects and version history make up the entire coding knowledge base of our company. I’d like to use this knowledge as a codebase for Cursor. Does anyone have experience using multiple codebases with Cursor? Or, is there a planned feature for Cursor to integrate with Git repositories?

Thanks for any ideas and information!

Best regards,

---

<div class="post-metadata">

**Author:** ![pshenichnov](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/pshenichnov/32/31533_2.png) [@pshenichnov](https://forum.cursor.com/u/pshenichnov)\
**Post date:** [January 21, 2025, 6:36pm UTC](https://forum.cursor.com/t/indexing-gitlab-repos-as-additional-codebase/25634/2 "2025-01-21T18:36:03Z")

</div>

Same situation here… would be great to have Cursor integrated with GitLab but unfortunately it won’t happen in the nearest future.

---

<div class="post-metadata">

**Author:** ![danperks](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/danperks/32/19087_2.png) [@danperks](https://forum.cursor.com/u/danperks)\
**Post date:** [January 22, 2025, 8:02pm UTC](https://forum.cursor.com/t/indexing-gitlab-repos-as-additional-codebase/25634/3 "2025-01-22T20:02:13Z")

</div>

Hey, thanks for the suggestion!

We don’t have a good way of indexing external codebases, from platforms like GitHub or GitLab, but I can see the benefit it could provide, so I’ve added this to our internal feedback tracker to look at in the future.

---

<div class="post-metadata">

**Author:** ![amir-wyvern](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/amir-wyvern/32/40935_2.png) [@amir-wyvern](https://forum.cursor.com/u/amir-wyvern)\
**Post date:** [March 26, 2025, 11:29am UTC](https://forum.cursor.com/t/indexing-gitlab-repos-as-additional-codebase/25634/4 "2025-03-26T11:29:04Z")

</div>

you can use the gitlab mcp

---

<div class="post-metadata">

**Author:** ![josephinefoster](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/josephinefoster/32/43371_2.png) [@josephinefoster](https://forum.cursor.com/u/josephinefoster)\
**Post date:** [April 1, 2025, 10:05pm UTC](https://forum.cursor.com/t/indexing-gitlab-repos-as-additional-codebase/25634/5 "2025-04-01T22:05:33Z")

</div>

Amir, have you used gitlab mcp with cursor? If so, can you speak to the effectiveness of this approach?

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [June 18, 2026, 10:36am UTC](https://forum.cursor.com/t/indexing-gitlab-repos-as-additional-codebase/25634/6 "2026-06-18T10:36:29Z")

</div>

Closed on June 18, 2026, 10:36am UTC