The GitLab MCP that reaches merge requests and CI, not just issues
Connect one access token and 82 typed nodes put issues, merge requests and their approvals, branches, commits, CI pipelines and jobs, releases, labels, projects, and groups on your automation canvas. GitLab.com and self-managed instances both work.
What the GitLab MCP connector does
The GitLab connector for Mattering Automations covers the GitLab REST API v4 across the surfaces engineering teams actually automate: project and group issues, issue comments, merge requests with their commits, diffs, approvals, and merge, branches and commits, CI pipelines and jobs including the raw job log, releases, labels, projects, groups, and members. That is 82 nodes, split between read nodes that answer questions and action nodes that change something.
Each capability is a node on the Automations canvas, and every node speaks MCP, the open protocol for connecting AI assistants to tools. Claude, ChatGPT, and any MCP-capable assistant can use them, and they also power Matter, the AI assistant built into the platform. Describe the review or release workflow you want in plain language and it gets built on the canvas in front of you, where you can see every step and edit it.
Self-managed GitLab is a first-class case here rather than an afterthought. Every node carries an optional API base field: leave it blank for GitLab.com, or paste your instance host and Mattering works out the rest, adding the scheme, trimming a trailing slash, and appending the /api/v4 path when you have not already. Naming things is just as forgiving. A project can be given as its numeric id or as the path you read in the browser, my-group/my-project, and the connector URL-encodes the slash that would otherwise come back as a confusing 404. The same goes for branch names like feature/login and label names with spaces in them.
One connection, three surfaces
- Visual automations. Drag GitLab nodes onto the canvas and wire them to triggers, conditions, and other apps.
- AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
- The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.
Every GitLab node, ready to drop on the canvas
82 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.
Read and query nodes 41
GitLab: Get Branch
Get a single branch, including its head commit.
GitLab: Get Commit
Get a single commit by SHA, branch name, or tag name.
GitLab: Get Commit Diff
Get the file by file diff of a single commit.
GitLab: Get Current User
Get the account the access token belongs to. Takes no parameters, so this is the connector's auth probe: run it first to confirm the token and the host are right.
GitLab: Get Group
Get one group by numeric id or full path.
GitLab: Get Issue
Get one issue by its project internal id, with author, assignees, labels, milestone, and time tracking totals.
GitLab: Get Issue Comment
Get one comment on an issue by its note id.
GitLab: Get Job
Get one CI job with its status, stage, timings, runner, and the commit it ran on.
GitLab: Get Job Log
Get a job's log (trace) as plain text. GitLab returns raw text here rather than JSON, so the log arrives on the `log` field and the last 200 lines are also split out on `tail` for posting into a chat message.
GitLab: Get Latest Pipeline
Get the most recent pipeline for a branch or tag. Without ref, the project's default branch is used.
GitLab: Get Latest Release
Get the project's latest release through GitLab's permalink, so you do not need to know the tag name.
GitLab: Get Merge Request
Get one merge request. Read detailed_merge_status to find out whether it can be merged and why not if it cannot.
GitLab: Get Merge Request Approvals
Get the approval state of a merge request: how many approvals are required, how many are left, and who has approved. Available on all tiers.
GitLab: Get Merge Request Comment
Get one comment on a merge request by its note id.
GitLab: Get Pipeline
Get one pipeline with its status, duration, triggering user, and detailed status block.
GitLab: Get Pipeline Variables
List the variables a pipeline was started with. Treat the values as sensitive: they can carry secrets passed at trigger time.
GitLab: Get Project
Get one project by numeric id or full path, including its default branch, visibility, URLs, and namespace.
GitLab: Get Release
Get one release by its tag name, including its assets and notes.
GitLab: Get User
Get a single user by numeric id.
GitLab: List Branches
List a project's repository branches with their protection status and head commit.
GitLab: List Commits
List repository commits. Filter by branch or tag, by date window, by file path, or by author.
GitLab: List Group Issues
List issues across every project in a group, including its subgroups. Same filters as the project issue list.
GitLab: List Group Members
List the direct members of a group with their access levels.
GitLab: List Group Merge Requests
List merge requests across every project in a group, including its subgroups. The review-queue view for a whole team.
GitLab: List Group Projects
List the projects in a group. Set include_subgroups to true to walk the whole subgroup tree.
GitLab: List Groups
List the groups visible to the token.
GitLab: List Issue Comments
List the notes (comments) on an issue. GitLab returns both human comments and system notes, so filter on the `system` field when you only want what people wrote.
GitLab: List Issues Closed by a Merge Request
List the issues a merge request will close when it merges, taken from its closing pattern references.
GitLab: List Labels
List a project's labels, optionally with issue and merge request counts.
GitLab: List Merge Request Comments
List the notes (comments) on a merge request. Both human comments and system notes come back, so filter on the `system` field for review conversation only.
GitLab: List Merge Request Commits
List the commits that a merge request would bring in.
GitLab: List Merge Request Diffs
List the file diffs in a merge request, one entry per changed file. This is the supported replacement for the deprecated changes endpoint.
GitLab: List Merge Requests
List the merge requests in a project. Filter by state, branch, author, assignee, reviewer, labels, or draft status.
GitLab: List Pipeline Jobs
List the jobs in one pipeline. The usual first step after a pipeline-failed trigger: find which job failed, then read its log.
GitLab: List Pipelines
List a project's CI pipelines. Filter by status, branch, source, or the user who triggered them.
GitLab: List Project Issues
List the issues in a project, newest first by default. Filter by state, labels, milestone, assignee, or a free text search.
GitLab: List Project Jobs
List a project's CI jobs across all of its pipelines.
GitLab: List Project Members
List the direct members of a project with their access levels. Use this to turn a name into the numeric user id that assignee fields expect.
GitLab: List Projects
List projects visible to the token. Set membership to true for just the projects the token's user belongs to, which is almost always what an automation wants.
GitLab: List Releases
List a project's releases, newest first by default.
GitLab: List Users
List users visible to the token. Filter by username or a free text search to resolve a username into the numeric id that assignee and reviewer fields expect.
Action nodes 41
GitLab: Approve Merge Request
Approve a merge request as the user the access token belongs to. Available on all tiers. Reverse it with GitLab: Revoke Merge Request Approval.
GitLab: Cancel Job
Cancel a running or pending job. Retry it afterwards if you need to.
GitLab: Cancel Pipeline
Cancel a pipeline and its running jobs. Retry it afterwards with GitLab: Retry Pipeline.
GitLab: Close Issue
Close an issue. This is the edit-issue endpoint with state_event fixed to close, so nothing else about the issue changes. Reopen it with GitLab: Update Issue.
GitLab: Comment on Commit
Add a comment to a commit. Supply path, line, and line_type together to anchor the comment to a specific line of the diff.
GitLab: Comment on Issue
Add a comment to an issue. The comment is attributed to the user the access token belongs to.
GitLab: Comment on Merge Request
Add a comment to a merge request. The comment is attributed to the user the access token belongs to.
GitLab: Create Branch
Create a branch from an existing branch, tag, or commit SHA.
GitLab: Create Commit
Create a commit that adds, updates, moves, or deletes several files in one call. Each entry in actions needs an action of create, update, move, delete, or chmod plus a file_path.
GitLab: Create Issue
Create an issue in a project. Only the title is required. Assignees are numeric user ids, which GitLab: List Project Members resolves.
GitLab: Create Label
Create a project label. Both name and color are required, and color is a six digit hex value with a leading hash.
GitLab: Create Merge Request
Open a merge request. source_branch, target_branch, and title are required. Prefix the title with Draft: to open it as a draft.
GitLab: Create Project
Create a project. Supply name, path, or both. Without namespace_id the project lands in the token user's personal namespace.
GitLab: Create Release
Create a release. If the tag does not exist yet, supply ref and GitLab creates the tag from it first.
GitLab: Delete Branch
Delete a branch. DESTRUCTIVE: commits reachable only from this branch become unreferenced. Protected branches are refused.
GitLab: Delete Issue
Delete an issue. DESTRUCTIVE and irreversible: the issue and its comments are gone. Requires Owner or administrator rights. Close the issue instead unless you really mean to erase it.
GitLab: Delete Issue Comment
Delete a comment from an issue. DESTRUCTIVE and irreversible: the comment text is not recoverable.
GitLab: Delete Label
Delete a project label. DESTRUCTIVE: the label is removed from every issue and merge request that carries it.
GitLab: Delete Merge Request
Delete a merge request. DESTRUCTIVE and irreversible, and it needs Owner or administrator rights. Close the merge request with GitLab: Update Merge Request instead unless you mean to erase it.
GitLab: Delete Merge Request Comment
Delete a comment from a merge request. DESTRUCTIVE and irreversible: the comment text is not recoverable.
GitLab: Delete Merged Branches
Delete every branch already merged into the default branch. DESTRUCTIVE and bulk: protected branches are kept, everything else merged is removed. The work runs in the background.
GitLab: Delete Pipeline
Delete a pipeline. DESTRUCTIVE and irreversible: the pipeline, its jobs, its logs, and its artifacts are removed. Cancel it instead if you only want it to stop.
GitLab: Delete Project
Delete a project. DESTRUCTIVE: this removes the repository, its issues, and its merge requests. Depending on instance settings the project is either marked for delayed deletion or removed at once.
GitLab: Delete Release
Delete a release. DESTRUCTIVE: the release, its notes, and its asset links are removed. The underlying Git tag is kept.
GitLab: Erase Job
Erase a job's log and artifacts. DESTRUCTIVE and irreversible: the job record stays but its output is gone. Read the log first if you need it.
GitLab: Fork Project
Fork a project into a namespace the token's user can write to. Forking runs in the background, so the response can arrive before the repository has finished copying.
GitLab: Merge a Merge Request
Merge a merge request into its target branch. Returns 405 when the merge request cannot be merged yet, so check detailed_merge_status first or set merge_when_pipeline_succeeds.
GitLab: Move Issue
Move an issue to another project. GitLab closes the original and creates a copy in the target project, keeping a link between them.
GitLab: Play Manual Job
Start a manual job, the API equivalent of pressing play in the pipeline view. This is how an automation triggers a gated deploy.
GitLab: Rebase Merge Request
Rebase the merge request's source branch onto its target branch. The rebase runs in the background: the response only confirms it was queued.
GitLab: Retry Job
Retry a single failed or canceled job. Returns the new job.
GitLab: Retry Pipeline
Retry the failed and canceled jobs in a pipeline.
GitLab: Revoke Merge Request Approval
Withdraw the token user's own approval from a merge request. Available on all tiers.
GitLab: Run Pipeline
Start a new pipeline on a branch or tag. Note the singular /pipeline path: this is the one write endpoint in the pipelines family that does not use the plural form.
GitLab: Update Issue
Update an issue. Only the fields you supply change. Use state_event close or reopen to move the issue between states, and add_labels or remove_labels to edit labels without replacing the whole set.
GitLab: Update Issue Comment
Edit the text of an existing issue comment.
GitLab: Update Label
Rename or recolour a project label, or change its description and priority.
GitLab: Update Merge Request
Update a merge request. Only the fields you supply change. Use state_event close or reopen to change its state.
GitLab: Update Merge Request Comment
Edit the text of an existing merge request comment.
GitLab: Update Project
Update a project's settings. Only the fields you supply are changed. Use the body passthrough for any attribute not typed here.
GitLab: Update Release
Update a release's title, notes, milestones, or release date. The tag itself cannot be changed here.
Connecting GitLab takes one credential
GitLab authenticates with a personal, project, or group access token. Create one in GitLab under User Settings, then Access Tokens, with the api scope for read and write automations or read_api for a read-only one. Mattering sends it as the PRIVATE-TOKEN header, which is GitLab's own documented header for these tokens, and never places it in a URL where it could leak into access or proxy logs.
In GitLab, open User Settings, then Access Tokens, add a new token with the api scope, set an expiry you can live with, and copy it. GitLab shows the token once.
In Mattering Automations, open Connectors, click Add Connector, and choose GitLab.
Create a new credential, paste the token, and save. It is stored encrypted in Google Secret Manager and never appears in workflow logs.
Connect. All 82 GitLab nodes appear in the canvas palette.
Run GitLab: Get Current User as your first step. It takes no parameters, so a successful response naming your account confirms both the token and, on self-managed, the host.
On a self-managed or GitLab Dedicated instance, set the optional API base field on the node to your instance host, for example https://gitlab.example.com. Leave it blank for GitLab.com.
Common uses for the GitLab MCP
A review queue that chases itself
GitLab: List Group Merge Requests gives you every open merge request across a group and its subgroups, and GitLab: Get Merge Request Approvals says how many approvals are still outstanding on each one. Turn that into a daily digest, a nudge in chat, or tasks assigned to the reviewers who are holding things up.
CI failure triage without opening the pipeline view
When a pipeline fails, GitLab: List Pipeline Jobs finds the job that broke and GitLab: Get Job Log returns the trace, with the last 200 lines already split out for pasting into a message. An AI step reads it, says what failed in one paragraph, and the automation files the bug.
Agent-driven issue work
An assistant can search a project with GitLab: List Project Issues, open new ones with GitLab: Create Issue, edit labels and assignees with GitLab: Update Issue, comment with GitLab: Comment on Issue, and close with GitLab: Close Issue, using the same nodes the canvas uses.
Merge request review flow end to end
Read the change with GitLab: List Merge Request Diffs, post the review with GitLab: Comment on Merge Request, record a sign-off with GitLab: Approve Merge Request, and land it with GitLab: Merge a Merge Request once the pipeline is green.
Release automation on a branch you control
GitLab: Create Branch and GitLab: Create Commit prepare the change, GitLab: Run Pipeline starts the build, GitLab: Play Manual Job releases a gated deploy step, and GitLab: Create Release publishes notes assembled from the merge requests that shipped.
Engineering reporting across groups
On a schedule, pull GitLab: List Group Issues and GitLab: List Group Merge Requests and write the counts into a Mattering database, so cycle time and review load sit next to the rest of the team's work instead of in a separate tool.
Example: A failed pipeline becomes a tracked bug with the log already read
Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.
Trigger: a scheduled check runs GitLab: List Pipelines on your default branch, filtered to failed.
GitLab: List Pipeline Jobs returns the jobs in that pipeline, and the workflow picks the one that failed.
GitLab: Get Job Log fetches the trace, with the last 200 lines available on its own field.
An AI step reads the tail and writes a one paragraph diagnosis with the failing command.
Mattering Productivity creates an assigned task holding the diagnosis, the job link, and the commit, and GitLab: Comment on Merge Request posts the same summary onto the merge request that triggered the build.
GitLab MCP questions, answered
Can an AI agent triage issues and review merge requests through this MCP?
Yes. Matter and any MCP-connected assistant, including Claude and ChatGPT, can list and search issues, open and update them, comment, close them, read merge request diffs and commits, post review comments, approve or revoke an approval, and merge, using the same 82 nodes the automation canvas uses. Deleting is possible too, but the destructive nodes say so in the palette and are worth keeping behind a human approval step.
Does this work with Claude, ChatGPT, or other AI assistants?
Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant, including Claude and ChatGPT, can connect to your workspace and work with GitLab through them. Matter, the assistant built into the platform, uses the same nodes natively rather than being the only way in.
Does it work with self-managed GitLab and GitLab Dedicated?
Yes. Every node has an optional API base field. Leave it blank and the node calls GitLab.com; paste your instance host and it calls yours. Mattering handles the shape of what you paste, so gitlab.example.com, https://gitlab.example.com, and https://gitlab.example.com/api/v4 all resolve to the same API root. One workspace can hold a GitLab.com token and a self-managed token at the same time, because the host lives on the node rather than on the credential.
How do I tell a node which project to use?
Either way GitLab accepts. A numeric project id works, and so does the full path you read in the browser address bar, such as my-group/my-project or my-group/team/my-project for a subgroup. Calling GitLab's API directly, that slash has to be URL-encoded or the request returns a 404 that reads like a permissions problem; the connector encodes it for you, and it detects a path you already encoded so it never double-encodes. The same handling applies to branch names with slashes in them and to label names with spaces. One exception is flagged in its field description: the target of GitLab: Move Issue is a body field and takes a numeric id only.
What credential does the connector use?
A single GitLab access token, personal, project, or group, sent as the PRIVATE-TOKEN header that GitLab documents for exactly those tokens. It is one field, stored encrypted in Google Secret Manager. The token's own scope and the permissions of whoever created it decide what the automations can touch, so a read_api token gives you a strictly read-only connector.
Do I need a paid GitLab tier for this?
No. The REST API and access tokens are part of GitLab's Free tier, and approving, revoking an approval, and reading the approval state of a merge request are available on all tiers. Some individual fields on issues and merge requests are Premium or Ultimate features, and the ones that are say so in their field description; the rule-by-rule approval breakdown that is paid-only is deliberately not built.
How does the connector handle long lists and rate limits?
List nodes expose GitLab's page and per_page parameters and return one page per run, so a workflow that needs everything should loop over pages rather than expect it to happen by itself. There is no automatic paging and no retry backoff: if GitLab throttles a call, the node returns that status on its output so the workflow can decide to wait and try again. Rate limits differ between GitLab.com and self-managed instances, where an administrator can change them, so GitLab's own documentation is the source of truth for current numbers.
What is not covered by the 82 nodes?
The first pass spends its breadth on issues, merge requests, notes, branches, commits, pipelines, jobs, releases, labels, projects, groups, and members. Repository files, tags, milestones, wikis, snippets, epics, boards, webhooks, deploy keys, CI variables, environments, runners, and the registries are not typed yet. There are also no GitLab webhook trigger nodes, so workflows start from a schedule or from another trigger in Mattering rather than from a GitLab event. Where a documented filter or attribute is not typed, every node takes extra query parameters and every write node takes a free-form body, so those stay reachable without waiting on a connector update.
Put GitLab to work inside your workspace
Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.
All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. GitLab is a product of its respective owner; Mattering is an independent platform.