Reads issues, merge requests, and pipeline jobs, files new issues, cuts branches, and keeps project membership current.
58actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Ayro 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.
Ayro 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.
Ayro 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.
Each card is one request a support team gets, and the GitLab actions Ayro runs to close it.
Ayro 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.
When a conversation turns into a defect, Ayro 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.
Ayro 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.
Ayro 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.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Ayro reads the GitLab actions it has and picks the ones a request needs.
Authorize the GitLab account your team already uses — one consent screen, no API keys, no mapping tables. Ayro can only do what you granted that account, and you can disconnect it at any time.
Describe the job the way you would hand it to a teammate. Ayro maps it to the GitLab actions that close it and chains as many as the request needs.
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 freeGitLab · Ayro
What can you do in GitLab without me setting anything up?
These, right away:
Great, let's start with the first one.
FAQ
Setup, permissions, and the limits of what Ayro 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.
All 58 actions your agent can call on GitLab, straight from the live MCP connection.
Archive a project.
Create a new group in GitLab.
Create a new project in GitLab.
Create a new issue in a GitLab project.
Create a new branch in a project.
Delete a GitLab project by its ID.
Download a project's avatar image.
Erase the content of a specified job within a project.
Get all references (branches or tags) a commit is pushed to.
Get the sequence number of a commit in a project by following parent links from the given commit.
Retrieve information about a specific group by its ID.
Retrieve details for a specific group member.
Get Groups.
Retrieve details of a single job by its ID within a specified project.
Fetch comments on a merge request.
Get a single project by ID or URL-encoded path.
List programming languages used in a project with percentages.
Retrieve details for a specific project member.
Retrieve details for a specific project member (including inherited and invited members).
Fetch full details for a single merge request when the MR IID is known.
Get commits of a merge request.
Retrieve a list of merge requests for a specific project.
List all projects accessible to the authenticated user.
List all diff versions of a merge request.
Retrieve information about a specific branch in a project.
Retrieves a list of repository branches for a project.
Get a specific commit identified by the commit hash or name of a branch or tag.
Retrieve details of a single pipeline by its ID within a specified project.
Retrieve information about a specific user by their ID.
Get the current user's preferences.
Same connection, same setup. Pick the next one your team already uses.
Reads NFT metadata and floor prices, lists what a wallet holds across chains, verifies token-gated ownership, and reports sales and price history.
Triggers a named browser test, reports its status, timing and errors, and lists what the account actually covers.
Looks up repository and documentation data through Devin MCP and triggers updates directly from the conversation.
Searches a publication for the post that answers a question, publishes and edits articles, restructures docs sidebars, and replies to comments.
Lists uptime and transaction checks, traces which alert reached which contact, and runs an on-demand test from a chosen global probe.
Generates configured proxy endpoint strings, looks up endpoints and ports by type, and clears whitelisted IPs on request.

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