# How to connect GitLab to Claude Duet

> Connect GitLab to Claude Duet through Agent200's MCP server: managed OAuth, ready-made tools and one API key.

- Page: https://www.agent200.com/tools/gitlab/framework/claude-duet/
- Connector: [GitLab](https://www.agent200.com/tools/gitlab.md)
- Framework: Claude Duet
- Updated: 2026-11-15

## Instructions for AI agents

Goal: connect GitLab to Claude Duet with Agent200, through its MCP server.
Guide: https://www.agent200.com/tools/gitlab/framework/claude-duet/

1. The user needs an Agent200 API key. If they have none, send them to https://agent200.com/platform/apikeys/ to choose "Create an API key". They paste it into Claude Duet's settings themselves: never ask for it in chat and never write it into files you share.
2. Make sure GitLab is enabled for their project in the Agent200 dashboard (Connectors), with the tools the task needs.
3. Add Agent200's MCP server to Claude Duet: URL https://api.agent200.com/mcp/, transport streamable HTTP, header "Authorization: Bearer <the user's Agent200 API key>". Follow the setup steps on the guide page for Claude Duet's exact menus or commands.
4. The first GitLab request returns an authorization link if the user has not connected GitLab yet: show it to them and continue once they have approved access on GitLab's own page.
5. Check it works with this request: "Which merge requests are waiting for my review"
   What should come back:
   - An answer built from your own GitLab data.
   - Behind the scenes, Claude Duet calls an Agent200 tool for GitLab, such as `gitlab_list_merge_requests`.
6. 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.

## Overview

This guide connects GitLab to Claude Duet through Agent200's MCP server. When you finish, Claude Duet can search, read and act in GitLab with the tools Agent200 provides, whenever a request needs them.

You add one MCP server to Claude Duet with your Agent200 API key. Your GitLab account is connected through managed OAuth: you approve access once on GitLab's own page, and Agent200 keeps the connection working.

- **Connector:** [GitLab](https://www.agent200.com/tools/gitlab/)
- **Works with:** Claude Duet · Agent app, through MCP
- **Authentication:** Managed OAuth, per end user
- **You need:** [An Agent200 API key](https://agent200.com/platform/apikeys/)
- **Tools:** [8 tools](https://www.agent200.com/tools/gitlab/framework/claude-duet/#tools)
- **MCP server:** `https://api.agent200.com/mcp/`

## Before you start

- **An Agent200 API key.** Create one on the [API keys page](https://agent200.com/platform/apikeys/) 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.
- **Claude Duet, with custom MCP servers allowed.** Claude Duet is a research preview for Pro, Max and Ultra users in the US, by invitation. It uses the connectors of your Claude account, and sending an API key needs Claude's Request headers option.

## Connect GitLab to Claude Duet

### Step 1: Create your Agent200 API key

Open the API keys page in the Agent200 dashboard and choose Create an API key. You add it to Claude Duet in the next step, as "Authorization: Bearer <your key>". One key covers GitLab and every other connector enabled for your project. Keep it out of chats and source control.

Create an API key: https://agent200.com/platform/apikeys/

### Step 2: Add Agent200 as a custom connector in Claude

Duet has no connector settings of its own: it uses those of your Claude account. In Claude, go to **Customize > Connectors**, choose **Add > Add custom connector**, enter the server URL, choose **No sign-in** and add the `authorization` request header with `Bearer` and your key.

File `Add custom connector`:

```text
Remote MCP server URL:  https://api.agent200.com/mcp/
Authentication:         No sign-in
Request header name:    authorization
Value:                  Bearer YOUR_AGENT200_API_KEY
```

### Step 3: Use it from Duet

Open Claude Duet with the same Claude account. The connectors set up in Claude are there from your first message; manage them in your Claude settings.

### Step 4: Approve actions when Duet asks

Duet asks before it sends a message, pays, signs or deletes anything. If you cannot approve right away, it finishes the rest and brings the approval back later.

### Step 5: Connect your GitLab account

The first time you ask Claude Duet for something in GitLab, Agent200 returns an authorization link. Open it and approve access on GitLab's own page. Agent200 stores the connection and keeps it working; your password never reaches Claude Duet or Agent200.

## Test your connection

Ask: "Which merge requests are waiting for my review"

What should come back:

- An answer built from your own GitLab data.
- Behind the scenes, Claude Duet calls an Agent200 tool for GitLab, such as `gitlab_list_merge_requests`.

If Claude Duet shows an authorization link instead, you have not connected GitLab yet: open it, approve access, then ask again.

## GitLab tools Claude Duet can call

- **List merge requests** (`gitlab_list_merge_requests`, read): List a project's merge requests, filtered by state, author or reviewer.
- **Get a merge request** (`gitlab_get_merge_request`, read): Read a merge request's description, status and changes.
- **Search issues** (`gitlab_search_issues`, read): Find issues by text, label, assignee or state.
- **Create an issue** (`gitlab_create_issue`, write): Open an issue in a project, with labels and an assignee.
- **Add a comment** (`gitlab_create_note`, write): Comment on an issue or a merge request.
- **Read a file** (`gitlab_get_file`, read): Read a file from a repository at a branch, tag or commit.
- **List pipelines** (`gitlab_list_pipelines`, read): List a project's CI/CD pipelines and their status.
- **Retry a pipeline** (`gitlab_retry_pipeline`, write): Run a pipeline's failed jobs again.

## How it works

1. **You ask Claude Duet.** In your own words, for something in GitLab.
2. **Claude Duet picks a tool.** It sees the GitLab tools on the Agent200 MCP server and calls the one the request needs.
3. **Agent200 runs the call.** With your own GitLab connection, within the tools and scopes your project allows.
4. **Claude Duet answers.** It gets the result back from the MCP server and uses it in its reply or its next step.

**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

### Duet does not see the Agent200 connector

Duet must run on the same Claude account where you added the connector. Check it is listed under Customize > Connectors in Claude.

### Scheduled tasks do not call Agent200

Run the task while you are in the conversation. For unattended work, build the agent with the Agent200 SDK.

### There is no Request headers option in Claude

Request headers are a Claude beta that only some accounts have, and Duet has no key field of its own. Use Claude Code, or the Agent200 SDK.

### Claude Duet shows a GitLab authorization link

You have not connected GitLab yet, or the connection needs to be approved again. Open the link, approve access on GitLab's own page, then ask Claude Duet again.

### A tool call is refused or returns less than expected

Agent200 runs only what your project allows. Check that GitLab and the tools you need are enabled in the dashboard's Connectors settings, and that you granted GitLab the access the task needs.

### The API key was pasted into a chat or committed

Create a new key on the [API keys page](https://agent200.com/platform/apikeys/), replace it in Claude Duet's MCP settings, and stop using the old one. Paste the key only into Claude Duet's settings, never into a chat.

## Use GitLab with another framework

- [GitLab + Claude](https://www.agent200.com/tools/gitlab/framework/claude.md)
- [GitLab + ChatGPT](https://www.agent200.com/tools/gitlab/framework/chatgpt.md)
- [GitLab + Claude Code](https://www.agent200.com/tools/gitlab/framework/claude-code.md)
- [GitLab + Muse](https://www.agent200.com/tools/gitlab/framework/muse.md)
- [GitLab + Grok Bot](https://www.agent200.com/tools/gitlab/framework/grok-bot.md)
- [GitLab + OpenAI Dots](https://www.agent200.com/tools/gitlab/framework/openai-dots.md)
- [GitLab + Hermes Agent](https://www.agent200.com/tools/gitlab/framework/hermes-agent.md)
- [GitLab + OpenClaw](https://www.agent200.com/tools/gitlab/framework/openclaw.md)

---

Agent200: https://www.agent200.com/ · API keys: https://agent200.com/platform/apikeys/ · Docs: https://docs.igpt.ai/
