| [ Web Proxy ] |
| Viewing: https://cursor.com/docs/integrations/gitlab | [Back] [Original] |
Search for a command to run...
The GitLab integration connects your repositories so you can use features like Cloud Agents and Bugbot.
Requires Cursor admin access and GitLab maintainer access.
GitLab integration requires a paid GitLab plan (Premium or Ultimate). Project access tokens, which are required for this integration, are not available on GitLab Free.
To disconnect your GitLab account, return to the integrations dashboard and click Disconnect Account.
Self-hosted instances support multiple connection methods beyond IP whitelisting.
Available for Enterprise customers. Allow Cursor to access your instance over a private network connection. See Private Connectivity or contact your Cursor representative for setup.
Best for: Instances behind a firewall on a private network, including AWS-hosted instances and environments that can run cloudflared
Security: HTTPS encryption, AWS PrivateLink, Cloudflare Tunnel, VPC allowlisting, service account access tokens
Drawbacks: Requires coordination with Cursor. Google Private Service Connect is not currently supported.
Available for Enterprise customers. Run a reverse proxy tunnel on-premises that establishes a long-lived websocket connection to Cursor's servers. Network requests are forwarded through to your instance. Requires no inbound network access. Contact your Cursor representative for setup.
Best for: Environments without inbound network access
Security: HTTPS encryption, service account access tokens
Drawbacks: Introduces additional complexity, maintenance requirements, and potential security considerations compared to more direct connection methods
Lock your GitLab group or namespace to your Cursor organization so only your teams can use its repositories with Cloud Agents, automations, and Bugbot. Protecting a scope requires the GitLab Owner role. See Protected Git Scopes.
Once your GitLab integration is connected, configure the features that use it:
Search for a command to run...
The GitLab integration connects your repositories so you can use features like Cloud Agents and Bugbot.
Requires Cursor admin access and GitLab maintainer access.
GitLab integration requires a paid GitLab plan (Premium or Ultimate). Project access tokens, which are required for this integration, are not available on GitLab Free.
To disconnect your GitLab account, return to the integrations dashboard and click Disconnect Account.
Self-hosted instances support multiple connection methods beyond IP whitelisting.
Available for Enterprise customers. Allow Cursor to access your instance over a private network connection. See Private Connectivity or contact your Cursor representative for setup.
Best for: Instances behind a firewall on a private network, including AWS-hosted instances and environments that can run cloudflared
Security: HTTPS encryption, AWS PrivateLink, Cloudflare Tunnel, VPC allowlisting, service account access tokens
Drawbacks: Requires coordination with Cursor. Google Private Service Connect is not currently supported.
Available for Enterprise customers. Run a reverse proxy tunnel on-premises that establishes a long-lived websocket connection to Cursor's servers. Network requests are forwarded through to your instance. Requires no inbound network access. Contact your Cursor representative for setup.
Best for: Environments without inbound network access
Security: HTTPS encryption, service account access tokens
Drawbacks: Introduces additional complexity, maintenance requirements, and potential security considerations compared to more direct connection methods
Lock your GitLab group or namespace to your Cursor organization so only your teams can use its repositories with Cloud Agents, automations, and Bugbot. Protecting a scope requires the GitLab Owner role. See Protected Git Scopes.
Once your GitLab integration is connected, configure the features that use it:
| Web Proxy Viewer | New URL | Original Page |