Kiwi for Fly.io
Have the agent on a Kiwi step check a Fly.io app's status, Machines and logs, through the MCP server in Fly.io's flyctl CLI.
- Your agent works in Fly.io through its own connection. Kiwi does not call Fly.io and never holds its credentials.
- A workflow skill can list Fly.io among the tools it requires. When you supply your agent's available tools to a skill check and Fly.io is not among them, the check reports
SK15-UNSUPPORTED-TOOL. - A project Admin can add links to Fly.io, with notes, under Connections and bind them to the steps that use them. The agent reads them with
list_connections. - The agent can report the tools and plugins it ran with, including its Fly.io connection, with
report_configuration. - The agent submits links to its work in Fly.io as the step's outputs. People review them, and sign-off stays with the people your workflow names.
What your agent can do in Fly.io
- Read an app's status and its recent logs.
- Work with an app's Machines and volumes.
- Manage an app's secrets and certificates.
- List the apps and organizations the signed-in account can see.
- Fly.io marks the flyctl MCP server as experimental.
Set up
Connect your agent to Kiwi
Add Kiwi's hosted MCP server,
https://kiwiflow.io/mcp, to your coding agent.Connect your agent to Fly.io
Run the Fly.io MCP server where your agent runs. The credentials stay with your agent.
fly mcp serverExample skill
Publish instructions like these as a workflow skill that lists Fly.io among its required tools.
Read the Fly.io app name and the expected image from the step's inputs. Use flyctl to read the app's status and its most recent logs. Compare the running image with the expected one and note any mismatch. Submit the status output and the log excerpt as the step's outputs. Leave deploys, secrets and scaling to the run's Owner. If flyctl cannot reach the app, report a blocker.