Searches issues and pull requests, files new ones from a conversation, labels and assigns them, and reads repository docs to ground an answer.
846actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Ayro searches a repository's code and file paths to find the exact function or config a developer is asking about. Support no longer has to dig through the codebase by hand to answer a technical question.
Ayro removes a label from a GitHub issue the moment its status changes during a conversation. The issue board stays accurate without anyone editing tags manually after the fact.
Ayro updates an existing comment on a GitHub issue or pull request to reflect new information from a conversation. Developers see the latest context in one place instead of scrolling through duplicate comments.
Each card is one request a support team gets, and the GitHub actions Ayro runs to close it.
Ayro searches open issues and pull requests for the behaviour a customer just described, opens the closest match, and reports whether a fix is merged or still in review.
When the report is genuinely new, Ayro opens a GitHub issue in the customer's own wording, adds the reproduction steps as a comment, and assigns the maintainer who owns that area.
Ayro reads the label set a repository already uses, applies the ones your triage rota filters on, and links a duplicate report as a sub-issue of the tracking issue instead of leaving two threads open.
Ayro reads a repo's README, walks its file tree, and pulls the notes attached to a tagged release, so a question about supported versions comes back from the source rather than a stale doc page.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Ayro reads the GitHub actions it has and picks the ones a request needs.
Authorize the GitHub 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 GitHub 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 freeGitHub · Ayro
What can you do in GitHub 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 GitHub.
Only the ones the GitHub account or app installation you connect has access to. Find Repositories and Get A Repository return exactly what those credentials return in the UI, so a private repo stays invisible unless the connection was granted it.
All 846 actions your agent can call on GitHub, straight from the live MCP connection.
Abort a repository migration that is queued or in progress.
Accepts a PENDING repository invitation that has been issued to the authenticated user.
Adds GitHub Apps to the list of apps allowed to push to a protected branch.
Adds a GitHub user as a repository collaborator, or updates their permission if already a collaborator; permission applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation may be created or permissions updated directly.
Adds assignees to a GitHub issue.
Adds one or more email addresses (which will be initially unverified) to the authenticated user's GitHub account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the current user is accepted.
Add a custom field to a user-owned GitHub Projects V2 project.
Add an issue or pull request to a user-owned GitHub project.
Adds labels (provided in the request body) to a repository issue; labels that do not already exist are created.
Adds new custom labels to an existing self-hosted runner for an organization; existing labels are not removed, and duplicates are not added.
Adds a GitHub user to a team or updates their role (member or maintainer), inviting them to the organization if not already a member; idempotent, returning current details if no change is made.
Adds a classic project to a team or updates the team's permission on it.
Sets or updates a team's permission level for a repository within an organization; the team must be a member of the organization.
Adds a repository to a GitHub App installation, granting the app access; requires authenticated user to have admin rights for the repository and access to the installation.
Adds a repository to an existing organization-level GitHub Actions secret that is configured for 'selected' repository access.
Grants an existing repository access to an existing organization-level Dependabot secret when the secret's visibility is set to 'selected'; the repository must belong to the organization, and the call succeeds without change if access already exists.
Adds and appends custom labels to a self-hosted repository runner, which must be registered and active.
Adds a repository to an organization secret's access list when the secret's visibility is 'selected'; this operation is idempotent.
Grants a repository access to an organization-level GitHub Actions variable, if that variable's visibility is set to 'selected_repositories'.
Grants a specified repository access to an authenticated user's existing Codespaces secret, enabling Codespaces created for that repository to use the secret.
Adds one or more social media links (which must be valid, full URLs for platforms supported by GitHub) to the authenticated user's public GitHub profile.
Adds status check contexts to a protected branch's required status checks.
Add a sub-issue to a parent GitHub issue using GraphQL.
Adds teams to the list of teams with push access to a protected branch.
Adds users to the list of people allowed to push to a protected branch in an organization repository.
Adds organization members to the list of users granted Codespaces access billed to the organization.
Retrieves a map of all top-level GitHub REST API resource URLs and their templates.
Approves a workflow run from a forked repository's pull request; call this when such a run requires manual approval due to workflow configuration.
Assigns an existing organization-level role (identified by role_id) to a team (identified by team_slug) within a GitHub organization (org), provided the organization, team, and role already exist.
Assigns a specific organization role to a user who is a member or an outside collaborator in a GitHub organization, using a valid role ID.
Same connection, same setup. Pick the next one your team already uses.
Answers from your own search index, keeps records current, adds the synonyms and rules that fix bad matches, and surfaces zero-result queries.
Confirms token details, lists the organizations and connected agents a token reaches, and returns the webhook IPs a firewall needs to allow.
Lists certificate orders, surfaces upcoming expiries, runs domain validation, manages organizations and containers, and rotates API keys.
Inspects delivery attempts and raw payloads, replays failed events in bulk, wires up sources and destinations, and resolves delivery issues.
Finds the collection or spec behind a question, stands up mock servers, runs monitors and reports the result, and routes changes through forks and pull requests.
Brings domains under Certificate Transparency monitoring, lists unexpired issuances, inspects a single event, and silences known certificates.

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