GitLab to MCP: Drive GitLab from any AI Agent

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → GitLab, paste your credentials, mint an MCP API key and you're done. No Docker, no git clone, no local server.

GitLab

Let your AI work in GitLab: find projects, triage and update issues, review merge requests with their diffs and comments, check pipelines and read failing job logs, and read branches, commits and files. GitLab.com or your own GitLab instance, with a personal access token.

Setup

1. In GitLab, click your avatar → Edit profile → Access → Personal access tokens → Generate token. On GitLab.com the page is at gitlab.com/-/user_settings/personal_access_tokens.
2. Name the token (for example "AnythingMCP"), set an expiry date (at most 365 days on GitLab.com) and tick the scope api. For a read-only setup, tick read_api instead.
3. Copy the token right away: GitLab shows it only once. It starts with glpat-.
4. Paste the token into GITLAB_TOKEN, without the word Bearer. Set GITLAB_URL to https://gitlab.com for GitLab.com, or to the address of your self-managed or Dedicated instance as you open it in the browser (for example https://gitlab.example.com), without /api/v4 and without a trailing slash. Then install the connector.
5. Start with gitlab_get_current_user: it shows which GitLab user the token belongs to and confirms the address is right. Then name a project by its path, such as my-group/my-project, or let the AI find it with gitlab_list_projects.

Token expiry and access: on GitLab.com a token lasts at most 365 days. When yours expires, generate a new one with the same scope and paste it into GITLAB_TOKEN again. The connector acts as the token's user: the AI sees and changes exactly what that user can. A fine-grained personal access token (GitLab 19.2 and later) works the same way: give it read and write permission on issues, merge requests, repository, pipelines and jobs for the projects involved. Some GitLab.com groups enforce fine-grained tokens, and a classic token then fails on their projects with "Access denied: This operation requires a fine-grained personal access token". Project and group access tokens work too, but on GitLab.com they need Premium or Ultimate.

Read-only setup: use a token with read_api and switch off gitlab_create_issue, gitlab_update_issue, gitlab_add_issue_note, gitlab_create_merge_request, gitlab_update_merge_request, gitlab_add_merge_request_note and gitlab_create_branch.

Switched off at install: gitlab_delete_issue, which deletes an issue for good (only project owners and administrators may, and closing it with gitlab_update_issue is usually what you want), and gitlab_delete_branch. Turn them on only if the AI should delete issues or branches.

Projects, issues and merge requests: the tools take a project by its numeric id or its full path, such as my-group/my-project. Issues and merge requests are addressed by the number GitLab shows (#42, !17), not by their global id. gitlab_list_project_members provides the user ids for assignees and reviewers. gitlab_list_my_issues and gitlab_list_my_merge_requests work across all projects and show the token user's own items by default, including merge requests waiting for their review.

Reviews, pipelines and code: to review a merge request, the AI reads gitlab_get_merge_request (merge status and conflicts), then gitlab_get_merge_request_diffs page by page, gitlab_list_merge_request_commits and gitlab_list_merge_request_notes. A file whose diff is too large comes back without its text; the AI then reads it with gitlab_get_file_content on the source branch. For a failed pipeline it goes from gitlab_list_pipelines to gitlab_list_pipeline_jobs (failed jobs only) to gitlab_get_job_log. Files and job logs are cut at 200 KB, keeping the beginning: open a longer log in GitLab. gitlab_search_project searches code inside one project on every tier; code search across the whole instance with gitlab_search needs advanced search, a Premium feature.

Confirm writes first: issues, comments, merge requests and branches are created under the token user's name. The AI shows you the title, text or branch first and waits for your confirmation. GitLab carries out quick actions in a comment, such as /label, /assign, /close, /approve or /merge, so the AI only includes them when you ask. Creating a branch needs Developer access.

Rate limits: GitLab.com allows about 2,000 API requests per minute per user, 200 new issues and 60 new comments per minute, and 100 searches per minute. On a self-managed instance the administrator sets the limits. Over a limit GitLab answers 429: wait and try again.

Common errors: 401 means the token is wrong, expired or revoked, or GITLAB_URL points at a different instance than the one that issued it. 403 means a missing scope (for example a read_api token on a write) or a role too low for the action. 404 means the project, issue or file does not exist or the user cannot see it: GitLab hides private resources behind 404. 400 names the missing or invalid field. 409 on a new merge request means one is already open for those branches. A renamed project still answers reads at its old path, but writes there fail with 405: use the new path or the numeric id.

The connector has no tools to merge or approve merge requests, push commits, edit files, or run, retry or cancel pipelines, and it does not cover CI/CD variables, releases, wikis, packages, the container registry or administration.

Prerequisites: GITLAB_URL, GITLAB_TOKEN

Install the connector locally

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Open http://localhost:3000/connectors/store, pick GitLab and paste in the env vars listed under Prerequisites.

Available tools

Example prompts

• "Which merge requests are waiting for my review across all projects, and which of them have conflicts or a failing pipeline?"
• "Why did the latest pipeline on main in my-group/web-app fail? Show me the failed job and the error from its log."
• "Summarize merge request !128 in my-group/web-app: what changed, in which files, and which review comments are still unresolved."
• "Create an issue in my-group/web-app titled Checkout button misaligned on mobile, with the label bug, and assign it to Lena."

Next steps

• Connect to Claude
• Connect to ChatGPT