Can Lyro trigger a Buildkite build or fetch job logs?

No. The connected toolkit is read-only and covers Get Current Access Token, Get Meta, Get User, List Organizations, and List Pipeline Agents. There is no action that starts a build, cancels one, or downloads job logs, so Lyro confirms the account, the organizations it reaches, and the connected agents, then hands the conversation to an engineer for anything that changes state.

What does Lyro need to reach a Buildkite organization?

An API access token for the account. List Organizations returns only the organizations the authenticated user is a member of, and the slugs it returns are what List Pipeline Agents takes as input, so a token scoped to a single organization limits every lookup Lyro can run to that organization.

Can Lyro check more than one Buildkite organization in the same conversation?

Yes, as long as the token reaches them. List Organizations returns every organization the authenticated user belongs to, and List Pipeline Agents takes an organization slug as a parameter, so Lyro can run the same agent check across each one in turn rather than being pinned to a default.

What happens if the Buildkite API token is revoked?

Get Current Access Token is the check for that, so Lyro can confirm the connection before running a lookup. Once a token is revoked the calls fail and Lyro reports the connection problem instead of returning stale data, and a new token has to be added in the connection settings before the other actions work again.

Buildkite MCP integration

Confirms token details, lists the organizations and connected agents a token reaches, and returns the webhook IPs a firewall needs to allow.

Connect Buildkite See all integrations

5actions available

Three actions you can hand over today

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

Get user
Lyro retrieves details about the current authenticated user in Buildkite. Support agents verify account permissions and access levels instantly.
List organizations
Lyro lists all organizations the current user is a member of. Agents quickly navigate multi-org environments and route conversations to the right team.
List pipeline agents
Lyro lists connected agents for an organization in Buildkite. Support agents monitor build infrastructure health and deployment capacity in real time.

See all 5 actions

How businesses use Buildkite + Lyro

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

Confirm what the connected Buildkite token can reach
Lyro reads the current access token's details and the user account that owns it, so a question about validity or scope gets a live answer rather than a guess about which permissions were granted.
Get Current Access TokenGet UserList Organizations
Check which agents are connected to an organization
Lyro lists the agents currently attached to an organization, with filtering and pagination for large fleets, so a question about whether build capacity is online is answered from the API.
List Pipeline AgentsList OrganizationsGet User
Pull the webhook IPs a firewall has to allow
Lyro returns Buildkite API metadata including the webhook source IP addresses, so a firewall or allowlist change is made from current values instead of a runbook nobody has updated.
Get MetaGet Current Access TokenGet User
Resolve the organization slug another lookup needs
Lyro lists every organization the authenticated user belongs to and returns the slugs the other Buildkite actions take as input, so nobody has to hunt for them in the dashboard first.
List OrganizationsGet UserList Pipeline Agents

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

01
Connect Buildkite
Authorize the Buildkite 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 Buildkite 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

Buildkite · Lyro

Everything else about Buildkite

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

No. The connected toolkit is read-only and covers Get Current Access Token, Get Meta, Get User, List Organizations, and List Pipeline Agents. There is no action that starts a build, cancels one, or downloads job logs, so Lyro confirms the account, the organizations it reaches, and the connected agents, then hands the conversation to an engineer for anything that changes state.