Fly.io
Arcade tools designed for LLMs to interact with Fly.io
1.0.1Fly.io Toolkit
Provides Arcade tools that let LLMs manage Fly.io infrastructure programmatically — apps, Machines, volumes, networking, secrets, certificates, and deployments.
Capabilities
- App & release management: list, inspect, and deploy apps across organizations; query release history and current status.
- Machine lifecycle: create, start, stop, restart, and destroy Machines; scale Machine count or VM size/memory; inspect 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 and remove custom-domain certificates; check validation status and retrieve required DNS records.
- Secrets management: list secret names, set new secrets, and unset existing ones — with optional immediate rollout; secret values are never returned by Fly.io.
- Logs & observability: read filtered historical log entries per app; log access requires a token with explicit log-read permission — tools return a
no_accessstatus (not an error) when that permission is absent, so callers should branch onstatus.
Secrets
FLYIO_ACCESS_TOKEN — A Fly.io personal access token or deploy token used to authenticate all API calls. Obtain it from the Fly.io dashboard under Account → Access Tokens, or generate one via the CLI with fly tokens create. For log reading (Flyio.GetLogs) the token must additionally have log-read access; create a scoped token with fly tokens create --expiry 8760h and confirm log permissions are included. Deploy tokens (scoped to a single app) can be created with fly tokens create deploy -a <app-name> and are preferred for least-privilege deployments.
For general guidance on configuring secrets in Arcade, see https://docs.arcade.dev/en/guides/create-tools/tool-basics/create-tool-secrets. You can also manage secrets directly 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 |