GitHub

GitHub MCP integration

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

Three actions you can hand over today

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

  • Search code

    Lyro 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.

  • Remove a label from an issue

    Lyro 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.

  • Update an issue comment

    Lyro 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.

See all 846 actions

How businesses use GitHub + Lyro

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

  • Tell a reporter whether their bug is already tracked

    Lyro 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.

    Search Issues And Pull RequestsGet An IssueGet A Pull Request
  • File an issue straight from the conversation

    When the report is genuinely new, Lyro 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.

    Create An IssueCreate An Issue CommentAdd Assignees To An Issue
  • Keep the incoming issue queue labelled

    Lyro 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.

    Add Labels To An IssueSearch LabelsAdd Sub-Issue To An Issue
  • Answer from the repository, not from memory

    Lyro 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.

    Get A Repository ReadmeList Repository FilesGet A Release By Tag Name

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 GitHub actions it has and picks the ones a request needs.

  1. 01

    Connect GitHub

    Authorize the GitHub 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 GitHub 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
GitHub · Lyro

Everything else about GitHub

Setup, permissions, and the limits of what Lyro 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.

Every action available in GitHub

All 846 actions your agent can call on GitHub, straight from the live MCP connection.

  • Abort repository migration

    Abort a repository migration that is queued or in progress.

  • Accept a repository invitation

    Accepts a PENDING repository invitation that has been issued to the authenticated user.

  • Add app access restrictions

    Adds GitHub Apps to the list of apps allowed to push to a protected branch.

  • Add a repository collaborator

    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.

  • Add assignees to an issue

    Adds assignees to a GitHub issue.

  • Add email for auth user

    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 field to user project

    Add a custom field to a user-owned GitHub Projects V2 project.

  • Add item to user project

    Add an issue or pull request to a user-owned GitHub project.

  • Add labels to an issue

    Adds labels (provided in the request body) to a repository issue; labels that do not already exist are created.

  • Add org runner labels

    Adds new custom labels to an existing self-hosted runner for an organization; existing labels are not removed, and duplicates are not added.

  • Add or update team membership for a user

    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.

  • Add or update team project permissions

    Adds a classic project to a team or updates the team's permission on it.

  • Add or update team repository permissions

    Sets or updates a team's permission level for a repository within an organization; the team must be a member of the organization.

  • Add a repository to an app installation

    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.

  • Add repo to org secret with selected access

    Adds a repository to an existing organization-level GitHub Actions secret that is configured for 'selected' repository access.

  • Add selected repo to org secret

    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.

  • Add runner labels

    Adds and appends custom labels to a self-hosted repository runner, which must be registered and active.

  • Add selected repository to an organization secret

    Adds a repository to an organization secret's access list when the secret's visibility is 'selected'; this operation is idempotent.

  • Add selected repository to an organization variable

    Grants a repository access to an organization-level GitHub Actions variable, if that variable's visibility is set to 'selected_repositories'.

  • Add a selected repository to a user secret

    Grants a specified repository access to an authenticated user's existing Codespaces secret, enabling Codespaces created for that repository to use the secret.

  • Add social accounts for the authenticated user

    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.

  • Add status check contexts

    Adds status check contexts to a protected branch's required status checks.

  • Add sub-issue to an issue

    Add a sub-issue to a parent GitHub issue using GraphQL.

  • Add team access restrictions

    Adds teams to the list of teams with push access to a protected branch.

  • Add user access restrictions

    Adds users to the list of people allowed to push to a protected branch in an organization repository.

  • Add users to codespaces access for an organization

    Adds organization members to the list of users granted Codespaces access billed to the organization.

  • Get github API root

    Retrieves a map of all top-level GitHub REST API resource URLs and their templates.

  • Approve a workflow run for a fork pull request

    Approves a workflow run from a forked repository's pull request; call this when such a run requires manual approval due to workflow configuration.

  • Assign an organization role to a team

    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.

  • Assign an organization role to a user

    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.

Ready to connect GitHub?

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

Support agent working at a laptop next to the Lyro mascot