Fly.io
Arcade tools designed for LLMs to interact with Fly.io
1.0.2Fly.io toolkit for Arcade enables LLMs to manage the full lifecycle of Fly.io applications, machines, volumes, networking, secrets, and TLS certificates via the Fly.io API.
Capabilities
- App & release management: list apps and organizations, inspect app status, view release history, and deploy new container images across all machines.
- Machine lifecycle: create, start, stop, restart, and permanently destroy machines; scale machine count; resize VM size and memory; inspect individual machine configuration and health.
- Storage & networking: create, extend, and destroy persistent volumes; allocate and release dedicated IP addresses; list all assigned IPs including shared IPv4.
- TLS certificates: add custom-domain certificates, retrieve required DNS validation records, check certificate status, list, and remove certificates.
- Secrets management: set, unset, and list app secret names (values are never returned by Fly.io); roll secrets out to running machines immediately or on next deploy.
- Logs & observability: read recent historical log entries with optional filtering; log access requires a token with explicit log-read permission — check the
statusfield in the response rather than assuming logs are present.
Secrets
FLYIO_ACCESS_TOKEN — A Fly.io personal access token or deploy token used to authenticate all API requests. To create one, sign in to the Fly.io dashboard and generate a new token under Access Tokens. For log reading (Flyio.GetLogs) the token must additionally have log-read access; tokens scoped only to app management will return a no_access result for log calls. If you use flyctl, you can also run fly auth token to retrieve your current session token, but prefer a dedicated token with the minimum required permissions for production use.
For guidance on configuring secrets in Arcade, see the Arcade secrets docs. You can manage your secrets at https://api.arcade.dev/dashboard/auth/secrets.
Available tools(30)
| Tool name | Description | Secrets | |
|---|---|---|---|
Add a TLS certificate for a hostname and return the DNS records to set. | 1 | ||
Allocate a new IP address for an app. | 1 | ||
Check a certificate's validation status and any pending DNS records. | 1 | ||
Create a new Machine for an app from a container image. | 1 | ||
Create a new persistent volume for an app. | 1 | ||
Roll a new container image out to all of an app's Machines. | 1 | ||
Permanently destroy a Machine. Stop it first unless force is set. | 1 | ||
Permanently destroy a volume and the data it holds. | 1 | ||
Grow a volume to a larger size. Volumes cannot be shrunk. | 1 | ||
Get the current status of a single Fly.io app. | 1 | ||
Read recent historical log entries for an app, optionally filtered.
Reading logs requires a token granted log-read access, which is a capability
separate from app management; a token without it cannot read logs at all. When
that access is missing this returns a ``no_access`` result rather than raising,
so prefer branching on the result's ``status`` over assuming logs are present. | 1 | ||
Get the configuration, state, and health of a single Machine. | 1 | ||
List Fly.io apps, optionally scoped to a single organization.
Apps are returned in Fly.io's own ordering, with pagination metadata so a
caller can tell when more apps exist beyond the returned window. | 1 | ||
List the custom-domain TLS certificates configured on an app. | 1 | ||
List the IP addresses assigned to an app, including the shared IPv4. | 1 | ||
List the Machines that belong to an app. | 1 | ||
List the Fly.io organizations the configured token can access. | 1 | ||
List the Fly.io regions available for deploying apps and volumes. | 1 | ||
List an app's release history, newest first. | 1 | ||
List an app's secret names. Secret values are never returned by Fly.io. | 1 | ||
List the persistent volumes that belong to an app. | 1 | ||
Release a dedicated IP address so it is no longer assigned to the app. | 1 | ||
Remove a custom-domain TLS certificate from an app. | 1 | ||
Restart a Machine and report its settled state. | 1 | ||
Scale an app to a target Machine count by adding or removing Machines. | 1 |