At a glance
- Availability: Experimental (how to enable).
- Authentication: API key.
- Connection: The key comes from
FLY_API_TOKEN. - Provider documentation: Authentication reference.
Credentials
Set these per environment. See Connect an integration.Setup
- Sign up for Fly.io: Go to https://fly.io and create an account (the pay-as-you-go plan with a small test app is sufficient; new accounts include trial credit).
- Create an access token: Run ‘fly tokens create org -o <org-slug>’ with flyctl, or create a token in the dashboard under Account > Access Tokens (https://fly.io/dashboard/personal/tokens). Org tokens are preferred over personal auth tokens.
- Set the environment variable: Add the token to your .env as FLY_API_TOKEN=…
- Verify access: Run List Apps with your org slug (use ‘personal’ for the default personal organization), then List Machines on one of the apps.
Provider notes
- The public Machines API endpoint is https://api.machines.dev; tokens are sent as ‘Authorization: Bearer <token>’
- org_slug is required when listing apps
- Tokens created with ‘fly tokens create’ may include a ‘FlyV1 ’ prefix in CLI output - store only the token value; the API accepts it after Bearer either way
Tools
Verify the connection
Call a read tool such asfly-io__list_apps with arguments for your account. Confirm that the result comes from the intended account or workspace before enabling write tools.