GitLab

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

    Read
    gitlab_list_merge_requests

    List a project's merge requests, filtered by state, author or reviewer.

  • Get a merge request

    Read
    gitlab_get_merge_request

    Read a merge request's description, status and changes.

  • Search issues

    Read
    gitlab_search_issues

    Find issues by text, label, assignee or state.

  • Create an issue

    Write
    gitlab_create_issue

    Open an issue in a project, with labels and an assignee.

  • Add a comment

    Write
    gitlab_create_note

    Comment on an issue or a merge request.

  • Read a file

    Read
    gitlab_get_file

    Read a file from a repository at a branch, tag or commit.

  • List pipelines

    Read
    gitlab_list_pipelines

    List a project's CI/CD pipelines and their status.

  • Retry a pipeline

    Write
    gitlab_retry_pipeline

    Run a pipeline's failed jobs again.

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_requests and switch off gitlab_retry_pipeline if 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. 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.js
    Conceptual example
    Set 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. 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.js
    Conceptual example
    Let 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. 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.js
    Conceptual example
    Run 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.

Agent brief
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.

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.

  • GitHub

    GitHub

    Read repositories and work with issues and pull requests as the connected user.

    Managed OAuth Developer tools
  • Bitbucket

    Bitbucket

    List and open pull requests, comment, read code and check pipelines in your users' Bitbucket workspaces.

    Managed OAuth Developer tools
  • Jira

    Jira

    Search, create and transition Jira issues for the connected user.

    Managed OAuth Developer tools
  • Linear

    Linear

    Create and update issues, and read projects and cycles in your users' Linear teams.

    Managed OAuth Developer tools
200 OK

Start with GitLab.
Your agent does the rest.

Your users connect their own GitLab accounts. Agent200 handles the OAuth, the tokens and every tool call.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)