Can I use Fly.io as a CLI?

Yes. KosmoKrator exposes a Fly.io CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Fly.io through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Fly.io tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Fly.io credentials stored?

Fly.io credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Fly.io MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

productivity

Fly.io CLI for AI Agents

Use the Fly.io CLI from KosmoKrator to call Fly.io tools headlessly, return JSON, inspect schemas, and automate workflows from coding agents, scripts, and CI.

7 functions 6 read 1 write Bearer token auth

Submit Fly.io feedback View package source

Fly.io CLI Setup

Fly.io can be configured headlessly with `kosmokrator integrations:configure fly-io`.

# Install KosmoKrator first if it is not available on PATH.
curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash

# Configure and verify this integration.
kosmokrator integrations:configure fly-io --set access_token="$FLY_IO_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmokrator integrations:doctor fly-io --json
kosmokrator integrations:status --json

Credentials

Authentication type: Bearer token bearer_token. Configure credentials once, then use the same stored profile from scripts, coding CLIs, Lua code mode, and the MCP gateway.

Key	Env var	Type	Required	Label
`access_token`	`FLY_IO_ACCESS_TOKEN`	Secret `secret`	yes	Access Token
`url`	`FLY_IO_URL`	URL `url`	no	API Base URL

Call Fly.io Headlessly

Use the generic call form when another coding CLI or script needs a stable universal interface.

kosmo integrations:call fly-io.fly_io_list_apps '{}' --json

Use the provider shortcut form for shorter human-facing commands.

kosmo integrations:fly-io fly_io_list_apps '{}' --json

Agent Discovery Commands

These commands return structured output for coding agents that need to inspect capabilities before choosing a function.

kosmo integrations:docs fly-io --json
kosmo integrations:docs fly-io.fly_io_list_apps --json
kosmo integrations:schema fly-io.fly_io_list_apps --json
kosmo integrations:search "Fly.io" --json
kosmo integrations:list --json

All CLI Functions

Every function below can be called headlessly. The generic form is stable across all integrations; the provider shortcut is shorter but specific to Fly.io.

`fly-io.fly_io_list_apps`

Read read

List all Fly.io apps in the organization. Returns app names, IDs, status, and network details.

Parameters: none

Generic CLI call

kosmo integrations:call fly-io.fly_io_list_apps '{}' --json

Provider shortcut

kosmo integrations:fly-io fly_io_list_apps '{}' --json

`fly-io.fly_io_get_app`

Read read

Get details for a specific Fly.io app, including status, network, and machine count.

Parameters: app_name

Generic CLI call

kosmo integrations:call fly-io.fly_io_get_app '{"app_name":"example_app_name"}' --json

Provider shortcut

kosmo integrations:fly-io fly_io_get_app '{"app_name":"example_app_name"}' --json

`fly-io.fly_io_create_app`

Write write

Create a new Fly.io app. Requires an app name and optionally an organization ID.

Parameters: app_name, org_slug

Generic CLI call

kosmo integrations:call fly-io.fly_io_create_app '{"app_name":"example_app_name","org_slug":"example_org_slug"}' --json

Provider shortcut

kosmo integrations:fly-io fly_io_create_app '{"app_name":"example_app_name","org_slug":"example_org_slug"}' --json

`fly-io.fly_io_list_machines`

Read read

List all machines for a Fly.io app. Returns machine IDs, state, region, and configuration.

Parameters: app_name

Generic CLI call

kosmo integrations:call fly-io.fly_io_list_machines '{"app_name":"example_app_name"}' --json

Provider shortcut

kosmo integrations:fly-io fly_io_list_machines '{"app_name":"example_app_name"}' --json

`fly-io.fly_io_get_machine`

Read read

Get details for a specific Fly.io machine, including its state, config, and region.

Parameters: app_name, machine_id

Generic CLI call

kosmo integrations:call fly-io.fly_io_get_machine '{"app_name":"example_app_name","machine_id":"example_machine_id"}' --json

Provider shortcut

kosmo integrations:fly-io fly_io_get_machine '{"app_name":"example_app_name","machine_id":"example_machine_id"}' --json

`fly-io.fly_io_list_volumes`

Read read

List all persistent volumes for a Fly.io app. Returns volume IDs, name, size, and region.

Parameters: app_name

Generic CLI call

kosmo integrations:call fly-io.fly_io_list_volumes '{"app_name":"example_app_name"}' --json

Provider shortcut

kosmo integrations:fly-io fly_io_list_volumes '{"app_name":"example_app_name"}' --json

`fly-io.fly_io_get_current_user`

Read read

Get the current authenticated Fly.io user information, including email and account details.

Parameters: none

Generic CLI call

kosmo integrations:call fly-io.fly_io_get_current_user '{}' --json

Provider shortcut

kosmo integrations:fly-io fly_io_get_current_user '{}' --json

Function Schemas

Use these parameter tables when building CLI payloads without calling integrations:schema first.

`fly-io.fly_io_list_apps`

List all Fly.io apps in the organization. Returns app names, IDs, status, and network details.

Operation: Read read
Schema command: kosmo integrations:schema fly-io.fly_io_list_apps --json

Parameter	Type	Required	Description
No parameters.

`fly-io.fly_io_get_app`

Get details for a specific Fly.io app, including status, network, and machine count.

Operation: Read read
Schema command: kosmo integrations:schema fly-io.fly_io_get_app --json

Parameter	Type	Required	Description
`app_name`	string	no	The name of the Fly.io app.

`fly-io.fly_io_create_app`

Create a new Fly.io app. Requires an app name and optionally an organization ID.

Operation: Write write
Schema command: kosmo integrations:schema fly-io.fly_io_create_app --json

Parameter	Type	Required	Description
`app_name`	string	no	The desired name for the new app.
`org_slug`	string	no	The organization slug to create the app in (optional, uses default org if omitted).

`fly-io.fly_io_list_machines`

List all machines for a Fly.io app. Returns machine IDs, state, region, and configuration.

Operation: Read read
Schema command: kosmo integrations:schema fly-io.fly_io_list_machines --json

Parameter	Type	Required	Description
`app_name`	string	no	The name of the Fly.io app.

`fly-io.fly_io_get_machine`

Get details for a specific Fly.io machine, including its state, config, and region.

Operation: Read read
Schema command: kosmo integrations:schema fly-io.fly_io_get_machine --json

Parameter	Type	Required	Description
`app_name`	string	no	The name of the Fly.io app.
`machine_id`	string	no	The machine ID.

`fly-io.fly_io_list_volumes`

List all persistent volumes for a Fly.io app. Returns volume IDs, name, size, and region.

Operation: Read read
Schema command: kosmo integrations:schema fly-io.fly_io_list_volumes --json

Parameter	Type	Required	Description
`app_name`	string	no	The name of the Fly.io app.

`fly-io.fly_io_get_current_user`

Get the current authenticated Fly.io user information, including email and account details.

Operation: Read read
Schema command: kosmo integrations:schema fly-io.fly_io_get_current_user --json

Parameter	Type	Required	Description
No parameters.

Permissions

Headless calls still follow the integration read/write permission policy. Configure read/write defaults with integrations:configure. Add --force only for trusted automation that should bypass that policy.