GitLab
Work with GitLab projects, issues, and merge requests from your Runnit agents.
Category: Developer and operations
Availability
Section titled “Availability”This connector uses the vendor’s official MCP server.
Vendor requirements: GitLab 18.6 or later
Connecting
Section titled “Connecting”Open Admin > Agent Integrations, select Browse connectors, and choose GitLab. The form asks for:
GitLab.com
Section titled “GitLab.com”- Sign in with the vendor: selecting Connect sends your browser to the vendor to approve access, then returns you to Runnit to finish. The approval must finish in the same browser it started in.
Self-hosted instance
Section titled “Self-hosted instance”- Server URL: For self-hosted GitLab 18.6+, the server lives on your instance at https://<your-gitlab-host>/api/v4/mcp; paste that URL.
- Sign in with the vendor: selecting Connect sends your browser to the vendor to approve access, then returns you to Runnit to finish. The approval must finish in the same browser it started in.
Agents act in GitLab as the account you connect, and the vendor attributes their actions to it. Runnit asks you to confirm this before connecting. Where possible, sign in with a dedicated service account rather than a personal one. The connected account is shown on the integration card.
More detail
Section titled “More detail”- GitLab developer documentation
- Agent Integrations covers testing, availability to agents, reconnecting, and removing an integration.