# Your GitLab projects. One clear review plan. Source: https://corespeed.io/integrations/gitlab 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. ## Set up an agent Give your agent this line: `set up https://corespeed.io/SKILL.md (read it raw, e.g. with curl)` It fetches the skill at https://corespeed.io/SKILL.md, adds the CoreSpeed MCP server, signs you in (or up), and keeps the skill for next time. Connect GitLab after setup. Access follows the connected account and its permissions. Create an account: https://app.corespeed.io/sign-up ## 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. You ask your agent: "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." It calls CoreSpeed: - `gitlab__list_merge_requests`: ok, 512 ms - `gitlab__list_pipelines`: ok, 448 ms It reads from: GitLab. ### Review plan: What to look at first. One merge request needs a decision on its retry limit. The latest pipeline on main failed. **Review** - !128: confirm the retry limit before it merges. **Follow up** - Pipeline #9041 on main failed: open its job log in GitLab to find the cause. _Illustrative project · No comments added or issues created_ All connectors: https://corespeed.io/docs/connectors ## From merge requests to the next step Requests you can make once GitLab is connected. The data is fictional. ### Understand a merge request !128 · webhook retries · Changes at a glance - Changed: Retries with backoff for failed deliveries - Review needed: Confirm the retry limit - A summary, not a merge ### Find the failed pipelines acme/api · this week · Pipelines by branch - Failed: main, at commit 4f2a9c1 - Passed: feature/webhook-retries - From the projects you can access ### Open an issue, with a yes A follow-up for the team · A write that waits - Issue: Fix the flaky migration test - Policy: Ask before creating issues - Held for a person Full example: https://corespeed.io/solutions/agent-approvals (Markdown: https://corespeed.io/solutions/agent-approvals.md) ## 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 guides: Claude Code https://corespeed.io/docs/mcp#claude-code · Codex https://corespeed.io/docs/mcp#codex · Cursor https://corespeed.io/docs/mcp#cursor ## Questions ### Does it work with self-managed GitLab? Not today. The connector signs in to GitLab.com accounts. ### Can my agent merge a merge request? No. CoreSpeed's GitLab tools read merge requests and comment on them; none of them merges. ### Does this change anything on its own? No. Reading is separate from writing. Creating an issue or adding a comment is its own tool call, which approvals can hold for a person. ### Do I have to switch agents? No. CoreSpeed adds tools to the agent you already use: Claude Code, Codex, Cursor, or another MCP client. Each one signs in once. ### Can my agent access every account in our organization? No. Access follows your CoreSpeed identity, each connection's visibility, and the app's own permissions. Personal connections stay private. ### Does this work without connecting an account? No. Connect the app's account first; your CoreSpeed workspace shows what each app needs. The examples on this page use fictional data. All connectors: https://corespeed.io/docs/connectors Every tool and price: https://corespeed.io/catalog/gitlab ## Related pages - [Bitbucket for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/bitbucket): Bring Bitbucket pull requests, pipelines and deployments into your agent. Read the diff, find the failed step, then decide. - [GitHub for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/github): Turn GitHub issues and pull requests into a clear project update inside your agent, without the tab tour. - [MCP gateway for your agents and tools](https://corespeed.io/solutions/mcp-gateway): Reach connected apps, built-in tools, and your own remote MCP servers through one authenticated CoreSpeed MCP endpoint. - [Sentry for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/sentry): Bring Sentry issues, events and stack traces into your agent. Find the error that matters and the likely cause. - [Stack Exchange for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/stack-exchange): Search Stack Overflow and the Stack Exchange sites from your agent. Read the answers that fit your error, with their comments. - [WakaTime for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/wakatime): Bring your WakaTime coding stats, goals and team dashboards into your agent. See where the week went, by project. ## Sources - Connectors: https://corespeed.io/docs/connectors - GitLab merge requests API: https://docs.gitlab.com/api/merge_requests/ - GitLab pipelines API: https://docs.gitlab.com/api/pipelines/ - GitLab issues API: https://docs.gitlab.com/api/issues/ Reviewed 2026-11-10. ## Links - Product overview: https://corespeed.io/ (Markdown: https://corespeed.io/index.md) - All integrations: https://corespeed.io/integrations (Markdown: https://corespeed.io/integrations.md) - Documentation: https://corespeed.io/docs - Pricing: https://corespeed.io/pricing (Markdown: https://corespeed.io/pricing.md)