Connect GitLab to Codex
Search, read and write GitLab from Codex. Arlet links the two through one MCP connection and takes care of keys and authentication.
Arlet makes GitLab's official MCP server available from the AI client you already use. Signing in to GitLab.com completes the connection.
The AI can read projects and repositories, review and comment on merge requests, create and update issues, and inspect or rerun CI pipelines and jobs. The available tools are those provided by GitLab's official server, which GitLab offers as a beta.
How to connect GitLab to Codex
- 1
In the Arlet dashboard, open Integrations β Add an integration and choose GitLab. Sign in with Link GitLab, name the connection and click Create.
- 2
In your terminal, run codex mcp add arlet --url https://mcp.arlet.dev/mcp/ to add Arlet as an MCP server.
- 3
Codex detects OAuth support and opens your browser. Sign in with Google and click Allow on the consent screen.
- 4
Once connected, both the CLI and the IDE extension can call Arlet tools (the configuration is shared).
If the browser does not open, run codex mcp login arlet to redo the authentication.
What you can do
GitLab tools that Codex can call.
searchSearch across GitLab.com by keyword.
list_projectsList projects.
get_projectGet a project's details.
get_repository_fileRead a file from a repository.
list_repository_treeList a repository's file tree.
list_commitsList commits.
list_merge_requestsList merge requests.
get_merge_requestGet a merge request's details.
get_merge_request_diffsGet a merge request's diffs.
save_merge_requestCreate or update a merge request.
save_merge_request_reviewPost a review on a merge request.
save_noteComment on a merge request or issue.
list_work_itemsList issues, tasks and epics.
save_work_itemCreate or update an issue, task or epic.
list_pipelinesList CI pipelines.
get_jobGet a CI job's details and log.
save_pipelineRun, retry or cancel a pipeline.
The tool list follows what GitLab's official MCP server provides and may change.
Example uses
Review a merge request
Read the diff, point out problems and post them as review comments.
Debug a failed pipeline
Read the failing job's log and summarize the cause and a fix.
File issues
Turn meeting notes into issues with labels and assignees.
Explore the code
Search across repository files and explain where something is implemented.
Prompts you can use as-is
- Review the diff of merge request !128 and post your concerns as comments
- Read the job log of the last failed pipeline on main and explain the cause
- Create issues in the backend project for the action items in these notes, with assignees
- Find where payment retries are implemented in the repository and explain it
