# How to connect GitLab to Muse

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

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

## Instructions for AI agents

Goal: connect GitLab to Muse with Agent200, through its MCP server.
Guide: https://www.agent200.com/tools/gitlab/framework/muse/

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 Muse'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 Muse: 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 Muse'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, Muse 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 Muse through Agent200's MCP server. When you finish, Muse can search, read and act in GitLab with the tools Agent200 provides, whenever a request needs them.

You add one MCP server to Muse 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:** Muse · 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/muse/#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.
- **Muse, with custom MCP servers allowed.** Muse creates custom connectors from a chat, and your key goes into its secure credentials sheet, never into the chat. Muse Code reads servers from its settings file.

## Connect GitLab to Muse

### 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 Muse 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: Ask Muse to create a custom connector

Start a new Muse chat and send this message. Muse builds the connector and shows a button to add your API key.

File `Muse chat`:

```text
Create a Custom Connector for the Agent200 remote MCP server and connect to it:
Name: Agent200
Transport: remote streamable HTTP
URL: https://api.agent200.com/mcp/
Auth: API key sent in the Authorization header as "Bearer <key>"
Open the secure credentials store so I can enter the API key there, not in this chat.
Then list its tools to confirm the connection works.
```

### Step 3: Add your key in the secure sheet

Tap the button Muse shows to open **Add custom connector**, paste your Agent200 API key and tap **Add**. Muse keeps it in its Secure Credentials Store and lists the Agent200 tools once the connection works.

### Step 4: Using Muse Code? Add the server to its settings

In the terminal version, declare the server in `~/.config/muse/settings.json` and export `AGENT200_API_KEY` in your shell instead of writing the key in the file. Run `/mcp` in a session to see it.

File `~/.config/muse/settings.json`:

```json
{
  "schema_version": 1,
  "mcp_servers": {
    "agent200": {
      "transport": "streamable_http",
      "url": "https://api.agent200.com/mcp/",
      "headers": { "Authorization": "Bearer ${AGENT200_API_KEY}" },
      "enabled": true,
      "mode": "optional"
    }
  }
}
```

### Step 5: Connect your GitLab account

The first time you ask Muse 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 Muse 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, Muse calls an Agent200 tool for GitLab, such as `gitlab_list_merge_requests`.

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

## GitLab tools Muse 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 Muse.** In your own words, for something in GitLab.
2. **Muse 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. **Muse 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

### You pasted the API key into the chat

Create a new key on the API keys page, stop using the old one, and enter the new one only through the secure Add custom connector sheet. Keys typed in a chat stay in its history.

### Muse returns unauthorized when it lists the tools

Ask Muse to update the Agent200 connector’s credential and enter the key again in the secure sheet. Say that it goes in the Authorization header with the Bearer prefix.

### Muse asks for a local command or a package

Answer that Agent200 is a hosted server over remote streamable HTTP, with API key sign-in. Nothing has to be installed.

### Muse does not use Agent200 in a later chat

Start a new chat after connecting, and name Agent200 and GitLab in the request.

### Muse 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 Muse 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 Muse's MCP settings, and stop using the old one. Paste the key only into Muse'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 + 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 + Claude Duet](https://www.agent200.com/tools/gitlab/framework/claude-duet.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/
