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.
3actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Ayro retrieves details for a single Bonsai cluster by slug. Infrastructure status is available instantly in support chat.
Ayro retrieves all available spaces. Agents see which spaces are configured without switching to infrastructure dashboards.
Ayro fetches configuration for a specific space. Details appear in chat for faster troubleshooting.
Each card is one request a support team gets, and the Bonsai actions Ayro runs to close it.
Ayro lists the spaces available to the account, reads a single space by its path to check its server group and region, and returns a named cluster's configuration and status from its slug.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Ayro reads the Bonsai actions it has and picks the ones a request needs.
Authorize the Bonsai 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 Bonsai 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 freeBonsai · Ayro
What can you do in Bonsai 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 Bonsai.
No. All three connected actions are reads - Get Bonsai Cluster Details, Retrieve Space Details and List Spaces - so Ayro can report what exists and where a cluster could be provisioned, while creating, resizing or removing one stays a deliberate action taken in Bonsai.
All 3 actions your agent can call on Bonsai, straight from the live MCP connection.
Retrieve details for a single bonsai cluster by slug.
Retrieve details for a single space by its path.
Retrieve a list of all available spaces.
Same connection, same setup. Pick the next one your team already uses.
Resolves builds by version, quotes job logs and artifacts, surfaces status badges, and answers who has access to the account.
Explains which analysis tools and patterns cover a language, reports enabled repositories, and issues or revokes an account API token.
Verifies an address the moment it is given, pushes a full list through as one batch, and follows the job until its results are ready.
Checks flag status by environment, evaluates what a specific user is actually served, and routes flag changes through approval instead of flipping them directly.
Finds the right table, reads a row by primary key or filter, writes the correction back, and exports a filtered table as CSV.
Lists the machines and commands on a TriggerCMD account, then fires a named command or panel button on the computer you specify.

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