GitLab

# GitLab

Projects, merge requests, issues and pipelines over the GitLab API. A GitLab access token is required.

- **Publisher of the server:** GitLab
- **Upstream:** https://gitlab.com/gitlab-org/gitlab-mcp-server
- **Documentation:** https://gitlab.com/gitlab-org/gitlab-mcp-server
- **Transport:** streamable HTTP (remote)
- **Endpoint:** `https://gitlab.com/api/v4/`

## Credentials and configuration

- PRIVATE-TOKEN: <personal access token>

These are **placeholders describing what to supply**; the registry stores no credentials. Enter real values in your own AO instance when you create the connection.

## Tools (10)

- `list_projects` — List projects visible to the token.
- `get_project` — Read one project's metadata.
- `search_code` — Search code within or across projects.
- `list_merge_requests` — List merge requests in a project.
- `get_merge_request` — Read one merge request and its diff.
- `create_merge_request` — Open a merge request.
- `merge_merge_request` — Merge a merge request.
- `list_issues` — List issues in a project.
- `create_issue` — Open an issue.
- `list_pipelines` — List CI/CD pipelines for a project.

## Risk

Declared risk: **high**. Tools that can change state: `list_merge_requests`, `get_merge_request`, `create_merge_request`, `merge_merge_request`, `create_issue`. Write access must be enabled explicitly.

> This entry is a catalogue description. Installing it creates no connection and grants no agent access;
> your instance's own connection settings and approvals decide what an agent can reach.