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 Headless Automation

Use the Fly.io CLI for headless automation with headless JSON commands, schema discovery, credentials, and permission controls.

7 functions 6 read 1 write Bearer token auth

Submit Fly.io feedback View package source

Fly.io CLI for Headless Automation

Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers.

Use headless automation when another tool needs a stable local command surface. The Fly.io CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Fly.io CLI for Headless Automation
kosmokrator integrations:configure fly-io --set access_token="$FLY_IO_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call fly-io.fly_io_list_apps '{}' --json

Discovery Before Execution

Agents and scripts can inspect Fly.io docs and schemas 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

Useful Fly.io CLI Functions

Function	Type	Parameters	Description
`fly-io.fly_io_list_apps`	Read	none	List all Fly.io apps in the organization. Returns app names, IDs, status, and network details.
`fly-io.fly_io_get_app`	Read	app_name	Get details for a specific Fly.io app, including status, network, and machine count.
`fly-io.fly_io_create_app`	Write	app_name, org_slug	Create a new Fly.io app. Requires an app name and optionally an organization ID.
`fly-io.fly_io_list_machines`	Read	app_name	List all machines for a Fly.io app. Returns machine IDs, state, region, and configuration.
`fly-io.fly_io_get_machine`	Read	app_name, machine_id	Get details for a specific Fly.io machine, including its state, config, and region.
`fly-io.fly_io_list_volumes`	Read	app_name	List all persistent volumes for a Fly.io app. Returns volume IDs, name, size, and region.
`fly-io.fly_io_get_current_user`	Read	none	Get the current authenticated Fly.io user information, including email and account details.

Automation Notes

Use --json for machine-readable output.
Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
Configure read/write policy before unattended runs; use --force only for trusted automation.
Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.

Related Fly.io CLI Pages

CI Fly.io CLI for CI. Cron Jobs Fly.io CLI for cron jobs. Shell Scripts Fly.io CLI for shell scripts. Coding Agents Fly.io CLI for coding agents.