Developer tools
GitLab for AI agents.
Managed auth, ready-made tools.
Review merge requests, file issues, read code and check pipelines in your users' GitLab projects.
About GitLab
With the GitLab connector, your agent works in each user’s own GitLab projects through Agent200: it reviews open merge requests, finds and files issues, reads code and checks how pipelines ran. Every user connects their own account through managed OAuth, and the agent acts with that user’s project permissions, nothing more.
GitLab is a DevOps platform that brings source code, merge requests, issues and CI/CD pipelines into one application.
Tools
What your agent can do in GitLab.
Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own GitLab connection.
-
List merge requests
Readgitlab_list_merge_requestsList a project's merge requests, filtered by state, author or reviewer.
-
Get a merge request
Readgitlab_get_merge_requestRead a merge request's description, status and changes.
-
Search issues
Readgitlab_search_issuesFind issues by text, label, assignee or state.
-
Create an issue
Writegitlab_create_issueOpen an issue in a project, with labels and an assignee.
-
Add a comment
Writegitlab_create_noteComment on an issue or a merge request.
-
Read a file
Readgitlab_get_fileRead a file from a repository at a branch, tag or commit.
-
List pipelines
Readgitlab_list_pipelinesList a project's CI/CD pipelines and their status.
-
Retry a pipeline
Writegitlab_retry_pipelineRun a pipeline's failed jobs again.
No tool matches that search.
Control
Limits you can set.
You decide what your agent may do in GitLab, and Agent200 runs every call within those limits.
-
Turn single tools on or off
Keep reading tools such as
gitlab_list_merge_requestsand switch offgitlab_retry_pipelineif your agent should never trigger CI. -
Restrict what the agent reaches
Choose the endpoints and scopes a project may use. A read-only agent never needs write access, and a call outside them is refused.
Get started
Connect GitLab
in three steps.
-
1
Set up the SDK
Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.
agent.jsConceptual exampleSet up the SDK with the Agent200 API key // One Agent200 API key covers every connector enabled for the project. const agent200 = new Agent200({ apiKey: process.env.AGENT200_API_KEY, }); -
2
Let your user connect GitLab
Each end user authorizes their own GitLab account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.
connect.jsConceptual exampleLet an end user connect their account (managed OAuth) // Each end user authorizes their own GitLab account, once. const connection = await agent200 .user("user_123") .connect("gitlab"); if (connection.authorizationUrl) { // Show this link to your user; Agent200 handles the rest. console.log(connection.authorizationUrl); } -
3
Run with the GitLab tools
Name the user, the model and the tools. The model decides which GitLab tools to call, and Agent200 executes them with that user's connection.
run.jsConceptual exampleRun a request with the connector's tools const result = await agent200 .user("user_123") .run({ model: "openai/gpt-5.6-sol", input: "Which merge requests are waiting for my review", tools: ["gitlab"], }); console.log(result.output);
Access
Sign-in and permissions.
-
Who signs in
Each of your users, once, on GitLab's own page. You never see or store their GitLab password.
-
What access is requested
GitLab lists the scopes on its consent screen, such as read-only API access or full API access when the agent writes. The agent reaches only the projects that user can already open.
For agents
Instructions for AI agents.
Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the GitLab connector and how to use it.
Connector: GitLab, through Agent200. In code: "gitlab". What it does: Review merge requests, file issues, read code and check pipelines in your users' GitLab projects. Page: https://www.agent200.com/tools/gitlab/ 1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs. 2. Sign-in is managed OAuth. Each end user approves access once, on GitLab's own page, through the authorization link Agent200 returns. Never ask a user for a GitLab password or token in chat. 3. Give every request a stable id for the end user. Agent200 uses only that user's own connection. 4. Read tools: gitlab_list_merge_requests, gitlab_get_merge_request, gitlab_search_issues, gitlab_get_file, gitlab_list_pipelines. Write tools: gitlab_create_issue, gitlab_create_note, gitlab_retry_pipeline. Name "gitlab" in the tools of a request; the model decides which tool to call. 5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it. 6. Before a write, confirm with the user, unless they asked for that exact change. 7. For setup with a specific framework, follow its guide: https://www.agent200.com/tools/gitlab/framework/claude/ https://www.agent200.com/tools/gitlab/framework/chatgpt/ https://www.agent200.com/tools/gitlab/framework/claude-code/ https://www.agent200.com/tools/gitlab/framework/muse/ https://www.agent200.com/tools/gitlab/framework/grok-bot/ https://www.agent200.com/tools/gitlab/framework/openai-dots/ https://www.agent200.com/tools/gitlab/framework/claude-duet/ https://www.agent200.com/tools/gitlab/framework/hermes-agent/ https://www.agent200.com/tools/gitlab/framework/openclaw/ The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/
This page is also available as Markdown, for agents and LLMs: /tools/gitlab.md
Guides
Use GitLab with the AI you build on.
Step-by-step setup for GitLab with a specific model, assistant or agent framework.
-
GitLab + Claude
How to connect GitLab to Claude
-
GitLab + ChatGPT
How to connect GitLab to ChatGPT
-
GitLab + Claude Code
How to connect GitLab to Claude Code
-
GitLab + Muse
How to connect GitLab to Muse
-
GitLab + Grok Bot
How to connect GitLab to Grok Bot
-
GitLab + OpenAI Dots
How to connect GitLab to OpenAI Dots
-
GitLab + Claude Duet
How to connect GitLab to Claude Duet
-
GitLab + Hermes Agent
How to connect GitLab to Hermes Agent
-
GitLab + OpenClaw
How to connect GitLab to OpenClaw
FAQ
GitLab and Agent200, answered.
Who handles the GitLab OAuth flow and the tokens?
Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for GitLab.
Does my agent act as the end user?
Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's GitLab connection, never another user's. It cannot reach anything the user or GitLab has not authorized.
Can I limit what my agent can do in GitLab?
Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.