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.

data

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.

Fly.io CLI Setup

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

Install, configure, and verify

# 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 reuse the same stored profile from scripts, coding CLIs, Lua, and MCP.

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

Command Patterns

The generic command is stable across every integration. The provider shortcut is shorter for humans.

Generic CLI call

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

Provider shortcut

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

Discovery

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

Discovery commands

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

Automation Contexts

The same configured command surface works in these environments. The command does not change unless the host wrapper, credentials, or permissions change.

CI Run integration calls from CI jobs with JSON output, explicit credentials, and predictable exit status. Cron Jobs Schedule repeatable integration workflows from cron while keeping credentials in KosmoKrator config. Shell Scripts Call integration functions from shell scripts with stable JSON input and output. Headless Automation Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers. Coding Agents Let coding agents discover schemas and execute integration functions through CLI commands or MCP.

CLI Functions

Every function below can be called headlessly. Commands are highlighted, copyable, and scroll horizontally when payloads are long.

`fly-io.fly_io_list_apps`

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

Read read

Parameters: none

Generic call

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

Shortcut

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

`fly-io.fly_io_get_app`

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

Read read

Parameters: app_name

Generic call

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

Shortcut

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

`fly-io.fly_io_create_app`

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

Write write

Parameters: app_name, org_slug

Generic call

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

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`

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

Read read

Parameters: app_name

Generic call

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

Shortcut

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

`fly-io.fly_io_get_machine`

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

Read read

Parameters: app_name, machine_id

Generic call

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

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`

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

Read read

Parameters: app_name

Generic call

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

Shortcut

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

Function Schemas

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

fly-io.fly_io_list_apps 0 parameters

Schema command

kosmo integrations:schema fly-io.fly_io_list_apps --json

Parameter	Type	Required	Description
No parameters.

fly-io.fly_io_get_app 1 parameters

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 2 parameters

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 1 parameters

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 2 parameters

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 1 parameters

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.

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.