• TidioReply faster to tickets across all channels
  • LyroHire AI to handle customer servicecheck
  • Hubi AIRun on-brand marketing with an AI coworker
  • LabsTidio LabsGet a custom AI solution built by experts
  • Master AgentOrchestrates every channel
  • AI Voice AgentResolves calls on its own
  • Lyro for Zendesk
  • Lyro for Freshdesk
  • Lyro for Salesforce
  • Lyro for HubSpot
Browse all integrationsarrow_forward
  • Borrowell83% resolved
  • GameBoost86% automated
  • Cove Smart70% self-service
  • Secureframe59% automated
See all customer storiesarrow_forward
  • AI in E-Commerce in 2026Free report on the new shopping funnel
  • Shadow AIFree report on the hidden AI habit
  • AI in Insurance in 2026Free report on AI in insurance
See all reportsarrow_forward
  • Features
  • Pricing
Talk to salesGet started
Lyro wordmark

Product

  • Features
  • Master Agent
  • AI Voice Agent
  • Integrations
  • Pricing
  • Copilot

Resources

  • Blog
  • Customer Stories
  • Reports
  • AI in Ecommerce Report
  • Docs

Company

  • Contact
  • Book a Demo

Legal

  • Privacy Policy
  • Terms of Service
  • Data Processing Agreement

4.7/5on G2G2 logo

SOC 2 Type II · GDPR · CCPA

© 2026 Lyro by Tidio. All rights reserved.

GitLab

GitLab MCP integration

Reads issues, merge requests, and pipeline jobs, files new issues, cuts branches, and keeps project membership current.

Connect GitLabSee all integrations

58actions available

  1. Home/
  2. Integrations/
  3. GitLab

Three actions you can hand over today

Every action runs live through MCP. Nothing to build, nothing to maintain.

  • Create project issue

    Lyro opens a new issue in a GitLab project the moment a bug or request comes up in chat. Whoever's affected gets a tracked ticket instead of a message that disappears.

  • Get user

    Lyro looks up a GitLab user's profile to confirm who owns a project or issue. Support reps get the right contact without digging through GitLab themselves.

  • Share project with group

    Lyro shares a GitLab project with a team's group so the right people gain access instantly. New collaborators can start working without waiting on a manual invite.

See all 58 actions

How businesses use GitLab + Lyro

Each card is one request a support team gets, and the GitLab actions Lyro runs to close it.

  • search

    Answer where an issue or merge request stands

    Lyro reads the open issues on a project, pulls the merge request under discussion, and quotes the review notes on it, so a question about progress is answered from the live project rather than guessed.

    List Project IssuesGet Project Merge RequestGet Merge Request Notes
  • bolt

    File a bug and start the branch for it

    When a conversation turns into a defect, Lyro opens a project issue with the reporter's own steps and cuts the branch the fix will land on, so the work starts with a tracked record.

    Create Project IssueCreate Repository BranchCreate Project
  • insights

    Explain a red pipeline before anyone opens the UI

    Lyro finds the project's most recent pipeline, lists the jobs inside it, and reads the failing job's details, so the person asking hears which stage broke instead of a link to go look.

    List Project PipelinesList Pipeline JobsGet Job Details
  • group

    Keep project and group access current

    Lyro checks who is on a project or group, lists the invitations still pending, and shares a project with the group that needs it, so access questions do not queue behind an owner.

    List All Project MembersList Pending Group MembersShare Project With Group

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the GitLab actions it has and picks the ones a request needs.

  1. 01

    Connect GitLab

    Authorize the GitLab account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.

  2. 02

    Tell your agent what you need

    Describe the job the way you would hand it to a teammate. Lyro maps it to the GitLab actions that close it and chains as many as the request needs.

  3. 03

    Watch it work

    The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.

    Get started free

GitLab · Lyro

What can you do in GitLab without me setting anything up?

These, right away:

  • Create a merge request
  • Trigger a pipeline
  • Create an issue

Great, let's start with the first one.

Ask Lyro anything...

FAQ

Everything else about GitLab

Setup, permissions, and the limits of what Lyro can do inside GitLab.

  • No. The repository and CI surface is read-only apart from Create Repository Branch: commits, merge requests, and pipelines come back through List Repository Commits, List Merge Request Diffs, and List Project Pipelines, and there is no action that pushes a commit, opens a merge request, or triggers a run. Issues are the write surface, through Create Project Issue and Update Project Issue.

  • Exactly the ones the GitLab account you connect can see. Lyro calls List User Projects, Get Project, and Get Project Member as that user, so a private project the account is not a member of stays invisible, and its access level also decides whether a write like Update Project Issue succeeds.

  • Yes. List Billable Group Members returns who is consuming seats in a group, List Pending Group Members shows invitations that have not been accepted, and List All Group Members covers inherited membership from parent groups, so a licensing question can be answered without an owner exporting a report.

  • Those run a fixed workflow when a trigger fires. Lyro decides which GitLab calls to make while the conversation is still open, so one exchange can list a project's issues, read the failing job behind them, and create the issue that captures it, rather than following a single predefined path.

Every action available in GitLab

All 58 actions your agent can call on GitLab, straight from the live MCP connection.

  • Archive project

    Archive a project.

  • Create gitlab group

    Create a new group in GitLab.

  • Create project

    Create a new project in GitLab.

  • Create project issue

    Create a new issue in a GitLab project.

  • Create repository branch

    Create a new branch in a project.

  • Delete project

    Delete a GitLab project by its ID.

  • Download project avatar

    Download a project's avatar image.

  • Erase job

    Erase the content of a specified job within a project.

  • Get commit references

    Get all references (branches or tags) a commit is pushed to.

  • Get commit sequence

    Get the sequence number of a commit in a project by following parent links from the given commit.

  • Get group details

    Retrieve information about a specific group by its ID.

  • Get group member

    Retrieve details for a specific group member.

  • Get groups

    Get Groups.

  • Get job details

    Retrieve details of a single job by its ID within a specified project.

  • Get merge request notes

    Fetch comments on a merge request.

  • Get project

    Get a single project by ID or URL-encoded path.

  • Get project languages

    List programming languages used in a project with percentages.

  • Get project member

    Retrieve details for a specific project member.

  • Get project member all

    Retrieve details for a specific project member (including inherited and invited members).

  • Get project merge request

    Fetch full details for a single merge request when the MR IID is known.

  • Get merge request commits

    Get commits of a merge request.

  • Get project merge requests

    Retrieve a list of merge requests for a specific project.

  • Get projects

    List all projects accessible to the authenticated user.

  • List merge request diffs

    List all diff versions of a merge request.

  • Get repository branch

    Retrieve information about a specific branch in a project.

  • Get repository branches

    Retrieves a list of repository branches for a project.

  • Get single commit

    Get a specific commit identified by the commit hash or name of a branch or tag.

  • Get single pipeline

    Retrieve details of a single pipeline by its ID within a specified project.

  • Get user

    Retrieve information about a specific user by their ID.

  • Get user preferences

    Get the current user's preferences.

The tools GitLab sits next to

Same connection, same setup. Pick the next one your team already uses.

  • Alchemyarrow_outward

    Alchemy

    Reads NFT metadata and floor prices, lists what a wallet holds across chains, verifies token-gated ownership, and reports sales and price history.

  • Bugbugarrow_outward

    Bugbug

    Triggers a named browser test, reports its status, timing and errors, and lists what the account actually covers.

  • Devin MCParrow_outward

    Devin MCP

    Looks up repository and documentation data through Devin MCP and triggers updates directly from the conversation.

  • Hashnodearrow_outward

    Hashnode

    Searches a publication for the post that answers a question, publishes and edits articles, restructures docs sidebars, and replies to comments.

  • Pingdomarrow_outward

    Pingdom

    Lists uptime and transaction checks, traces which alert reached which contact, and runs an on-demand test from a chosen global probe.

  • Smartproxyarrow_outward

    Smartproxy

    Generates configured proxy endpoint strings, looks up endpoints and ports by type, and clears whitelisted IPs on request.

Browse every integration
Support agent working at a laptop next to the Lyro mascot

Ready to connect GitLab?

Authorize the account and your agent has all 58 actions from the first conversation.

Connect GitLabTalk to sales
Connect GitLabTalk to sales
Support agent working at a laptop next to the Lyro mascot