Creates sandboxes with the repo cloned in, runs commands and returns logs, sets autostop intervals, and handles access from invite to SSH key.
114actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Ayro sends an organization invitation with the roles and permissions you name. A new engineer is in the right org with the right access without anyone opening the admin console.
Ayro checks whether the person asking actually has access to a given sandbox. Access questions get resolved on the spot, and Ayro stops before acting on a sandbox that is not theirs.
Ayro archives a sandbox that is no longer in use. Idle environments stop consuming resources without an engineer having to remember to clean them up.
Each card is one request a support team gets, and the Daytona actions Ayro runs to close it.
Ayro creates the sandbox, clones the repository into it, and checks out the branch the work sits on, so a developer or a reviewer gets a ready environment instead of setup instructions.
Ayro executes the command, opens a process session for anything longer running, and returns the session logs, so a build or a script is driven and reported on from the conversation.
Ayro sets the autostop and auto-delete intervals on a sandbox and archives the one that is finished but worth keeping, so idle environments stop quietly accumulating cost.
Ayro invites the person into the organization, defines the role their access should follow, and issues the SSH access they need, so onboarding is not held up waiting on someone with admin rights.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Ayro reads the Daytona actions it has and picks the ones a request needs.
Authorize the Daytona 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 Daytona 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 freeDaytona · Ayro
What can you do in Daytona 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 Daytona.
Yes. Create Snapshot captures a sandbox's state and Create Sandbox Backup preserves it, with List Snapshots and Get Snapshot Build Logs covering what exists and how it was built. Create Volume attaches persistent storage, so data outlives the sandbox it was created in.
All 114 actions your agent can call on Daytona, straight from the live MCP connection.
Archives a sandbox in the Daytona platform.
Cancels a pending organization invitation.
[DEPRECATED] Checkout a branch or commit in a git repository within a sandbox.
Clones a Git repository into a sandbox toolbox.
Creates a new API key for the organization.
Initiates a backup operation for an existing sandbox environment.
Creates a new folder inside a sandbox's filesystem.
Creates a new organization in Daytona.
Creates an invitation to join an organization with specified roles and permissions.
Creates a new organization role with specified permissions.
Creates a new session in the sandbox for process management.
Creates a new PTY (pseudo-terminal) session in a sandbox.
Creates a new Docker registry for the organization.
Creates a new sandbox environment for development or testing purposes.
Creates a new snapshot resource that can be used as a base image for sandboxes.
Creates SSH access credentials for a sandbox environment.
Creates a new volume for storing data that can be attached to sandboxes.
Deactivates a snapshot in the Daytona platform.
Deletes an API key by its name.
Deletes an API key for a specific user.
Deletes a file inside a sandbox by its path.
Deletes a branch from a git repository inside a sandbox by its name.
Deletes an organization.
Deletes the OpenTelemetry (OTEL) configuration for an organization.
Deletes an organization role.
Deletes a PTY session and terminates the associated process.
Deletes a recording from the Daytona platform by its ID.
Deletes a Docker registry from the Daytona platform.
Deletes a sandbox from the Daytona platform by its ID or name.
Deletes a session from the Daytona platform by its ID.
Same connection, same setup. Pick the next one your team already uses.
Maps workspace databases and tables, executes builder page data sources, reads form structures, and sends account verification mail.
Starts builds on a chosen workflow and branch, reads build history, updates variable groups, and clears application caches without opening the dashboard.
Stands up a form with its notification and webhook settings, pages through its submissions, and retires it when it is finished.
Runs blacklist checks, reads SPF, DKIM, DMARC, and BIMI records, and tests SMTP, DNS, and HTTP reachability on demand.
Pulls full incident detail, updates status and severity as things develop, and tracks the action items an incident leaves behind.
Checks the 2Captcha balance, submits a CAPTCHA as a solving task, and reports solutions the target site rejected.

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