Integration · Automate and collaborate

GitLab and Meteor AI agents

Connect GitLab to a WhatsApp Met: check merge requests, pipelines, releases and work items, and comment with GitLab's official MCP.

Book a demo See every integration

How does GitLab connect to Meteor?

With the GitLab ready connector, your Met uses GitLab.com's official MCP server with the account the admin authorizes. It searches projects and groups, lists and opens merge requests with their pipelines or comments, reviews pipelines and jobs, commits, branches, tags, files and published releases. It also lists, opens, creates and updates work items, such as issues or tasks, and comments on merge requests and work items. That way the Met tells a customer whether their change is live. Every tool checks the connected account's permissions in the project or group.

What it automates

What a Meteor Met does with GitLab

Answer whether a change is live

When your agency's client asks on WhatsApp whether their change is published, the Met finds their request, the merge request that solves it, its pipeline and the published release, and answers with what it finds.

Log a request as a work item

If the client asks for a new adjustment, the Met creates a work item in the project with what they asked for, so the team picks it up in GitLab.

Alert the team with a comment

The Met leaves a comment on the merge request or work item with what the client said. It can mark it as internal so only members with the Reporter role or higher see it.

Explain why a deployment failed

If the owner asks why a change did not go out, the Met reviews the pipeline, finds the job that failed and reads its log to explain in plain words what happened.

20 tools

Everything your Met can ask GitLab for

Each one is a real action in the connector. You can switch off the ones you would rather it never used.

Tool	What it does
`get_project`	Gets a project's details, with its ID, full path, default branch, visibility and link.
`list_projects`	Lists the projects where the account has at least the Guest role, or all the projects of a group and its subgroups.
`list_groups`	Lists the account's top-level groups, or the subgroups of a group.
`search`	Searches for a term across the whole instance, a group or a project, for example in work items, merge requests or projects.
`get_user`	Gets a GitLab user to obtain their numeric ID, by username or the account itself.
`list_merge_requests`	Lists or searches merge requests in a project or a group, with summary data.
`get_merge_request`	Gets a merge request and, if requested, its diffs, commits, notes, pipelines, discussions, approvals or conflicts.
`save_note`	Adds a comment to a merge request or a work item, or replies to a discussion, as the connected account.
`list_branches`	Lists a project's branches, with an optional filter by name.
`list_commits`	Lists a project's commits, with filters by ref, author, path or date.
`get_commit`	Gets a commit's details and, if requested, its diff or notes.
`get_repository_file`	Gets the contents of a repository file as it is at a ref.
`list_releases`	Lists a project's published releases, most recent first, without their notes.
`list_tags`	Lists a project's tags, most recently updated first.
`list_pipelines`	Lists a project's pipelines, with filters by ref, status, source and date.
`get_pipeline`	Gets a pipeline and, if requested, its jobs, downstream pipelines, trigger jobs or artifacts.
`get_job`	Gets a CI/CD job's details and, if requested, its log or artifacts.
`list_work_items`	Lists or searches work items, such as issues, incidents, tasks or epics, in a group or a project.
`get_work_item`	Gets a work item with its type, dates, assignees, labels, milestone and parent, and if requested its notes or related merge requests.
`save_work_item`	Creates or updates a work item, such as an issue, a task or an epic.

The limits

What the GitLab integration does NOT do

We would rather say it here than have you find out during rollout.

It does not ask you for confirmation in the chat before writing. The server also has actions that make commits, merge merge requests and run, retry or cancel pipelines: GitLab marks them as destructive and they start turned off. Forking a project also starts turned off until the admin turns it on. Others, such as creating merge requests or branches, arrive on; if the Met does not need them, the admin turns them off in Connections.
It does not see more than the connected account. According to GitLab, a listed tool does not grant access: every tool checks that account's permissions in the project or group.
It does not include the vulnerability or wiki tools by default: they are optional GitLab groups. The GitLab Duo Agent Platform tools only appear if the account has that service.
It does not read a release's notes when listing releases: GitLab returns each release's data without its notes.
It does not pay your GitLab plan. Usage runs on your account; Meteor does not resell the service.

Before you start

What you need to connect GitLab

1

A GitLab.com account with access to the projects

The account your team uses for the projects. It works on the Free, Premium and Ultimate tiers.
2

MCP server access allowed in the group

On GitLab.com, access to the MCP server is allowed in the top-level group. If the connection fails, check that option with whoever manages the group.
3

Connect it in Met

In Met, open Connections → GitLab → Connect. A GitLab window opens so you sign in and authorize Met. Then you choose which actions stay on.

Frequently asked questions

Questions about GitLab and Meteor

Yes. According to GitLab, the MCP server is available on the Free, Premium and Ultimate tiers. The vulnerability tools do need Ultimate, and this page does not use them.

This connector points to GitLab.com. GitLab also offers the server on self-managed installations, but that uses your instance's address, not the one this connector has.

The server has those actions, but GitLab marks them as destructive and they start turned off. This page does not list them; if your Met only serves customers, it is best to leave them that way.

You do, with your GitLab account and plan. Meteor does not resell GitLab or charge for the actions your Met takes there.

Step by step