GitLab + ChatGPT

Connect GitLab to ChatGPT with OpenAI models and the Agent200 SDK

ChatGPT cannot send an API key to a custom MCP server, so this guide builds GitLab into your own agent with OpenAI's models and the Agent200 SDK.

On this page
  1. Overview
  2. Before you start
  3. Setup steps
  4. Test your connection
  5. Instructions for AI agents
  6. GitLab tools
  7. How it works
  8. Troubleshooting

Overview

ChatGPT can add custom MCP servers, but it signs in to them only with OAuth or with no sign-in, and cannot send an API key. Agent200’s MCP server uses your API key, so this guide takes the SDK route: you build GitLab into your own agent with OpenAI’s models, through Agent200.

Your agent then calls the GitLab tools with each user’s own GitLab connection: Agent200 runs the OAuth flow, stores the tokens and keeps them fresh.

Connector
GitLab
Works with
ChatGPT · Your own agent code
Authentication
Managed OAuth, per end user
Tools
8 tools
Model in examples
openai/gpt-5.6-sol

Before you start

  • An Agent200 API key. Create one on the API keys page of the dashboard.
  • GitLab enabled for your project. In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
  • An end user with a GitLab account. They approve access once, on GitLab's own page.
  • A model for your agent. The examples use openai/gpt-5.6-sol, through the same Agent200 API key.

Connect GitLab to ChatGPT

  1. 1

    Step 1: Create your Agent200 API key

    Open the API keys page in the Agent200 dashboard and choose Create an API key. Copy the key and store it as an environment variable, AGENT200_API_KEY, or in your secrets manager. One key covers GitLab and every other connector and model enabled for your project. Keep it out of chats, prompts and source control.

    .env
    Conceptual example
    Store the Agent200 API key as an environment variable
    # Keep the key out of your code, prompts and chats.
    export AGENT200_API_KEY="paste-your-key-here"
  2. 2

    Step 2: Set up the Agent200 SDK

    Add the SDK to your project and create a client with the key from the environment.

    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,
    });
  3. 3

    Step 3: Let your user connect GitLab

    Each end user authorizes their own GitLab account once, through managed OAuth. If the user has not connected yet, Agent200 returns an authorization link: show it to them, and they approve access on GitLab's own page. Agent200 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);
    }
  4. 4

    Step 4: Run with the GitLab tools

    Name the user, the model and GitLab in the tools. The model decides when a GitLab tool is needed, and Agent200 executes the call with the user's own 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);

Test your connection

Run one request to check everything is wired up.

Ask

Which merge requests are waiting for my review

What should come back

  • An answer in result.output, built from the user's own GitLab data.
  • Behind the scenes, the model calls a GitLab tool, such as gitlab_list_merge_requests, and Agent200 runs it.

If Agent200 returns an authorization link instead, the user has not connected GitLab yet. Go back to the connect step.

Get your API key

Create a key in the Agent200 dashboard. It reaches GitLab and every other connector enabled for your project.

Read the SDK docs

Instructions for AI agents

Using a coding agent? Paste this brief into it, or give it the address of this page. It lists what to do, in order, to connect GitLab to ChatGPT.

Agent brief
Goal: connect GitLab to ChatGPT with Agent200.
Guide: https://www.agent200.com/tools/gitlab/framework/chatgpt/

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. Make sure GitLab is enabled for the project in the Agent200 dashboard (Connectors), with the endpoints and scopes the task needs.
3. Add the Agent200 SDK to the project and create a client with that key.
4. Give every request a stable id for the end user. Agent200 uses only that user's own connections.
5. Connect the user's GitLab account through Agent200. If Agent200 returns an authorization link, show it to the user and continue once they have approved access on GitLab.
6. Run requests through Agent200 with a model (for example openai/gpt-5.6-sol) and "gitlab" in the tools. The model decides when a GitLab tool is needed; Agent200 executes the call.
7. Check it works with this request: "Which merge requests are waiting for my review"
   What should come back:
   - An answer in `result.output`, built from the user's own GitLab data.
   - Behind the scenes, the model calls a GitLab tool, such as `gitlab_list_merge_requests`, and Agent200 runs it.
8. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard and the access the user granted in GitLab, then retry.

The code on the guide page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/

The whole guide is also available as Markdown, for agents and LLMs: /tools/gitlab/framework/chatgpt.md

GitLab tools ChatGPT can call

  • 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.

How it works

  1. 01

    Your app sends the request

    It calls Agent200 with the model, instructions, the input, the end user's id and the GitLab tools.

  2. 02

    The model picks a tool

    The model decides whether a GitLab tool is needed, and with which arguments.

  3. 03

    Agent200 runs the call

    It uses that user's own GitLab connection, within the endpoints and scopes your project allows, and returns the result to the model.

  4. 04

    Your app gets the result

    Agent200 returns the completed result. Your app decides when the agent runs and what happens next.

Each user's own connection. Connections belong to individual end users. A request for one user never reaches another user's GitLab account.

Permissions at every level. Your project settings decide what the agent may request, the end user decides what they authorize, and GitLab enforces what its API grants.

Troubleshooting

Why not add Agent200 to ChatGPT as an MCP server?

ChatGPT’s custom MCP servers sign in with OAuth or with no sign-in, and cannot send an API key. Agent200’s MCP server uses your API key, so for ChatGPT users the SDK route on this page is the one that works.

The request says GitLab authorization is required

The end user has not connected GitLab yet, or the connection needs to be approved again. Agent200 returns an authorization link: show it to the user, let them approve access on GitLab's own page, then run the request again.

ChatGPT does not use the GitLab tools

Check that GitLab is enabled for your project in the dashboard's Connectors settings and that it is in the tools you send with the request. Naming GitLab in the request, or in the instructions, also helps the model choose the right tool.

A tool call is refused or returns less than expected

Agent200 runs only what your project allows (services, endpoints and scopes), and GitLab returns only what the end user authorized. Widen the endpoints or scopes in the dashboard if the agent needs more, then ask the user to connect GitLab again so they can approve the new access.

The results come from the wrong account

Every request names an end user (user_123 in the examples). Pass the id of the person your agent is working for: Agent200 then uses only that user's GitLab connection, never another user's.

The API key was pasted into a chat or committed

Create a new key on the API keys page, update AGENT200_API_KEY wherever your app reads it, and stop using the old one. Keep keys in environment variables or a secrets manager, never in prompts, chats or source control.

Use GitLab with another framework

200 OK

GitLab, connected to ChatGPT.
One SDK. One API key.

Agent200 handles the OAuth, the tokens and every tool call. You keep your agent, your model and your code.

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)