Appveyor MCP integration
Resolves builds by version, quotes job logs and artifacts, surfaces status badges, and answers who has access to the account.
14actions available
Three actions you can hand over today
Every action runs live through MCP. Nothing to build, nothing to maintain.
Get build artifacts
Lyro retrieves compiled binaries, packages, or release candidates from a specific build. You access deployment-ready outputs without logging into CI/CD systems.
Download build log
Lyro pulls the full build execution log for debugging failed or successful builds. Your team diagnoses issues without manual log navigation.
Get projects
Lyro lists all your projects and their CI/CD configurations in AppVeyor. You review your entire automation portfolio and build status at a glance.
How businesses use Appveyor + Lyro
Each card is one request a support team gets, and the Appveyor actions Lyro runs to close it.
Diagnose a build that just failed
Lyro resolves the build by its version number, downloads the log for the job that failed, and lists the artifacts it managed to produce, so the failing line is in the conversation rather than three clicks away.
Get Build By VersionDownload Build LogGet Build ArtifactsReport project status without the dashboard
Lyro enumerates the projects on the account and pulls the status badge for a project or a specific branch, so a green or red answer is backed by the image AppVeyor itself serves.
Get ProjectsGet Project Status BadgeGet Project Branch Status BadgeAnswer an access review question
Lyro lists every user on the account, the collaborators alongside them, and the roles available, so a question about who can reach what is answered from the account rather than from a spreadsheet.
Get UsersList CollaboratorsGet RolesClear out builds nobody needs
Lyro pulls the deployment environments and the build's own record first, then deletes the build once someone confirms, which AppVeyor acknowledges with a 204 No Content.
Get EnvironmentsDelete BuildGet Role
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 Appveyor actions it has and picks the ones a request needs.
- 01
Connect Appveyor
Authorize the Appveyor 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.
- 02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Appveyor actions that close it and chains as many as the request needs.
- 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
Everything else about Appveyor
Setup, permissions, and the limits of what Lyro can do inside Appveyor.
No. This toolkit reads builds rather than starting them: Get Build By Version, Get Build Artifacts, and Download Build Log all describe a run that already happened, and Delete Build is the only write. Kicking off a build stays with your existing CI triggers.
Every action available in Appveyor
All 14 actions your agent can call on Appveyor, straight from the live MCP connection.
Delete build
Delete a build by ID.
Download build log
Download the build log for a specific job.
Get build artifacts
Get the list of artifacts for a specific build job.
Get build by version
Get a specific project build by version number.
Get environments
Get a list of all deployment environments.
Get project branch status badge
Get a project branch status badge image.
Get projects
Get a list of all projects for the authenticated account.
Get project status badge
Get project status badge image.
Get public project status badge
Get status badge image for a project with a public repository.
Get role
Retrieve details of a specific role.
Get roles
Retrieve all roles in the account.
Get user invitations
Retrieve all pending user invitations in the account.
Get users
Retrieve all users in the account.
List collaborators
Retrieve all collaborators in the account.
The tools Appveyor sits next to
Same connection, same setup. Pick the next one your team already uses.
Bonsai
Returns a cluster's configuration and status by slug, reads a space by its path, and lists the spaces and regions open to the account.
Datadog
Searches logs and traces, reads and mutes monitors, schedules downtime for maintenance, and creates monitors, dashboards, and SLOs on request.
Grafana
Queries a public dashboard panel, ships OTLP logs into Loki, and reports health, ring and tenant status across Mimir and Loki.
Npm
Searches the registry, reads package metadata and dist-tags, pulls download counts by version or date range, and bulk-checks security advisories.
Sentry
Matches a reported error to a known Sentry issue, reads how far it has spread, updates issue status and links, and traces it back to the release that shipped it.
Veriphone
Validates the number a customer gives and shows a correctly formatted example for their country before it becomes a record.
Ready to connect Appveyor?
Authorize the account and your agent has all 14 actions from the first conversation.