---
title: "Kiwi for Fly.io"
description: "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."
canonical: "https://kiwiflow.io/integrations/fly-io"
---

# 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

### 1. Connect your agent to Kiwi

Add Kiwi's hosted MCP server, `https://kiwiflow.io/mcp`, to your coding agent.

- [Coding agents](https://kiwiflow.io/integrations#agent)
- [Quickstart](https://docs.kiwiflow.io/quickstart#connect-your-agent)

### 2. Connect your agent to Fly.io

Run the Fly.io MCP server where your agent runs. The credentials stay with your agent.

```
fly mcp server
```

- [Fly.io documentation](https://docs.fly.io/model-context-protocol/flyctl-server)

### 3. Example 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.
```

## More deployment and hosting integrations

- [Kiwi for AWS](https://kiwiflow.io/integrations/aws.md): Have the agent on a Kiwi step call AWS APIs under the IAM permissions it signs in with and read the AWS documentation, through the AWS MCP Server.
- [Kiwi for Microsoft Azure](https://kiwiflow.io/integrations/microsoft-azure.md): Have the agent on a Kiwi step check a Microsoft Azure App Service app and query Azure Monitor, through the Azure MCP Server.
- [Kiwi for Cloudflare](https://kiwiflow.io/integrations/cloudflare.md): Have the agent on a Kiwi step read and change Workers, DNS records and other Cloudflare settings, through the Cloudflare API MCP server.
- [Kiwi for Google Cloud](https://kiwiflow.io/integrations/google-cloud.md): Have the agent on a Kiwi step deploy a container to Cloud Run and read the service back, through Google Cloud's remote MCP server for Cloud Run.
- [Kiwi for Vercel](https://kiwiflow.io/integrations/vercel.md): Have the agent on a Kiwi step check a Vercel preview deployment and read its runtime logs, through Vercel's MCP server.
- [Kiwi for DigitalOcean](https://kiwiflow.io/integrations/digitalocean.md): Have the agent on a Kiwi step update a DigitalOcean App Platform app and follow its deployment, through DigitalOcean's MCP server.
- [Kiwi for Supabase](https://kiwiflow.io/integrations/supabase.md): Have the agent on a Kiwi step apply a database migration to a Supabase project and run the advisors afterwards, through Supabase's MCP server.
- [Kiwi for Netlify](https://kiwiflow.io/integrations/netlify.md): Have the agent on a Kiwi step deploy a site to Netlify and set its environment variables, through Netlify's MCP server.
- [Kiwi for Heroku](https://kiwiflow.io/integrations/heroku.md): Have the agent on a Kiwi step check a Heroku app's dynos, logs and Postgres database, through Heroku's MCP server.
- [Kiwi for Render](https://kiwiflow.io/integrations/render.md): Have the agent on a Kiwi step trigger a Render deploy, filter the service's logs and read its metrics, through Render's MCP server.
- [Kiwi for Railway](https://kiwiflow.io/integrations/railway.md): Have the agent on a Kiwi step redeploy a Railway service in a non-production environment, through Railway's MCP server.

- [Get started](https://kiwiflow.io/get-started)
- [Read the setup guide](https://docs.kiwiflow.io/other-tools)