OpenBot
DownloadApp
All plugins

GitLab

Issues, merge requests and pipelines

GitLab lets agents search projects, read and create issues, review and update merge requests, read repository files and commits, and check CI pipelines and jobs on GitLab.com. Each user signs in to their own GitLab account through the browser. Agents get the same permissions as the user: they can push commits, change issues and merge requests, and merge them. For a self-hosted GitLab, add an MCP server with your GitLab address followed by /api/v4/mcp in the MCP servers settings, and sign in there.

What an agent can do with GitLab

  • Review merge requests

    The agent lists merge requests with list_merge_requests and reads one with get_merge_request. It can leave a review with save_merge_request_review, open or update a merge request with save_merge_request, and merge it with accept_merge_request.

  • Work with issues

    GitLab keeps issues as work items. The agent finds them with list_work_items, reads one with get_work_item, and creates or updates one with save_work_item. It adds a comment with save_note.

  • Read the code

    The agent reads a file with get_repository_file, walks the tree with list_repository_tree, and reads history with list_commits and get_commit. It can also create a branch and add a commit.

  • Check CI pipelines

    The agent lists pipelines with list_pipelines, reads one with get_pipeline, and reads a job with get_job. Use this to find out why the last pipeline failed.

How to connect GitLab to OpenBot

  1. Open GitLab in OpenBot

    Press Open in OpenBot on this page, or find GitLab in the app's Apps tab. Get the app first if it is not on this computer.

  2. Sign in

    Press Connect and finish the sign-in in your browser. OpenBot keeps the token on the computer that runs OpenBot. You can disconnect at any time.

  3. Give an agent a task

    Ask an agent for work that needs GitLab, such as one of the example prompts below. The agent uses the plugin's tools to do it.

Example prompts3

  • GitLabWhich merge requests wait for my review?
  • GitLabWhy did the last pipeline on the default branch fail?
  • GitLabFile an issue for the crash in the sync queue with reproduction steps.

Apps1

  • GitLab

    Projects, issues, merge requests, repositories and CI pipelines, over GitLab's MCP server with browser sign-in.

Information6

Developer
GitLab
Category
Coding
Version
1.0.0
Website
about.gitlab.com
Privacy policy
about.gitlab.com/privacy
Terms
about.gitlab.com/terms

Questions

Is the GitLab MCP server official?

Yes. GitLab builds the server into GitLab itself, at /api/v4/mcp. It is generally available on the Free, Premium and Ultimate tiers, on GitLab.com, GitLab Self-Managed and GitLab Dedicated.

Does the GitLab plugin need a personal access token?

No. Each user signs in to their own GitLab account through the browser. OpenBot registers itself with GitLab, does the sign-in, keeps the tokens in encrypted storage, and adds the Authorization header. The plugin catalog holds no secret.

Does it work with a self-hosted GitLab?

Yes, but not from this listing, which connects to GitLab.com. Add an MCP server with your GitLab address followed by /api/v4/mcp in the MCP servers settings, and sign in there. On GitLab Self-Managed, an administrator must allow access to the MCP server for the instance.

What data does GitLab get?

Your workspaces, conversations and files stay on the computer that runs OpenBot. GitLab gets the requests that the agent sends, such as a search query or a merge request update. The tools work on the groups and projects that your GitLab account can access.

Sources

Every statement about GitLab comes from the pages below, checked on . They can change after that date.