Give the engineers who work in GitLab the customer’s report, not a summary of it. Gleap connects to GitLab in two ways: the native integration turns tickets into GitLab issues, and Kai Code works in your GitLab repositories and opens merge requests. GitLab issues are available on the Team plan and higher, and Kai Code on Pro and Enterprise.
From customer report to GitLab issue
Choose the GitLab project that receives the issues. Gleap creates each issue with the report, its captured details and the screenshot, and labels it “Gleap”. The integration can also update the issue and send new messages to it as the conversation continues.
Send selected ticket types automatically, or send a single ticket from its sidebar once your team has decided it belongs in GitLab. Optional settings mark the ticket as done once it is sent, leave out personal data or keep internal notes in Gleap.
Connect GitLab
- Add GitLab in your project’s Integrations settings and authorize Gleap on GitLab.com.
- Choose the project that should receive issues.
- Turn on automatic sending for the ticket types that belong there, or leave it off for manual handoffs.
- Send a sample report and check the issue in GitLab.
The issue tracker setup guide covers routing and connection checks.
Merge requests from Kai Code
On Pro, Kai Code works in GitLab.com repositories. Connect a repository in Kai Code, start a task from a ticket or a prompt, and Kai Code opens a merge request from Kai Code Cloud or from the Kai Code Bridge on your own machine. Your team reviews it, merges and ships.
Gleap follows the merge request. After the merge, the customer follow-up runs with your release settings: by default a teammate confirms the fix is live before the customer hears back.
FAQ
Which Gleap plan includes the GitLab integration?
Team, Pro and Enterprise include the GitLab issue integration. Kai Code, which opens merge requests in your GitLab.com repositories, is part of Pro and Enterprise. See pricing for the plans.
Does Kai Code need the GitLab issue integration?
No. They connect separately: the issue integration in your project’s Integrations settings, and repositories in Kai Code. You can use either one alone.
Can Gleap’s AI agents use GitLab through MCP?
Yes, as an agent tool that is separate from this integration. Kai, the support agent, can use GitLab from the Team plan, and custom agents and Kai Code can on Pro and Enterprise. Gleap connects the tool through Composio’s MCP server for GitLab, and the agent calls only the actions you switch on. Other remote MCP servers can be added by URL as a Custom MCP tool.
