IntegrationsGitLab integration
Your GitLab projects.One clear review plan.
Connect GitLab to Claude Code, Codex, Cursor or any MCP agent through CoreSpeed. Your agent lists a project's merge requests, issues and CI pipelines on GitLab.com, reads a file at any branch, and drafts a review plan or a release note. It uses your own GitLab account, and opening an issue or adding a comment is a separate call.
From merge requeststo the next step.
Requests you can make once GitLab is connected. The data is fictional.
- GitLabMerge request
!128 · Retry failed webhook deliveries
- Target: main, from feature/webhook-retries.
- Open question: is five retries the right limit?
- Pipeline: passed.
Understand a merge request
A summary, not a merge
- GitLabacme/api · pipelines
- #9041main · 4f2a9c1Failed
- #9038feature/webhook-retriesPassed
- #9035feature/rate-limitsRunning
Find the failed pipelines
From the projects you can access
Approval requestWaiting
Claude Code for Drew
gitlab__create_issue
“Fix the flaky migration test on main.”
Policy: Ask before creating issues in a shared project.
ApproveDeny
Open an issue, with a yes
Held for a person
Know what needs review.See which pipelines failed.
Ask your agent for the open merge requests, the failed pipelines, and the next step, in the GitLab projects you connect.
Reads fromGitLab
All connectors →List the open merge requests in acme/api and the pipelines that failed this week. Draft a review plan. Do not comment or change anything.
gitlab__list_merge_requestsok
3 open, 1 waiting for review
Keep your agent.Bring your work.
One CoreSpeed account, across compatible agents.
- 1
Set up CoreSpeed
Give your agent the setup line. It adds CoreSpeed and signs you in.
- 2
Connect GitLab
Authorize the account and the content you need.
- 3
Start with one task
Ask for a summary, a brief, or a draft. Review the answer.
Setup guidesClaude CodeCodexCursor