Fly.io connector for AI agents

Tools your platform agent reaches for on Fly.io, scoped per user.

CALL ANY TOOL

54 tools for app hosting on Fly.io: create apps and Machines, start, stop, suspend, and exec into Machines, manage volumes and snapshots, set secrets, assign IPs, and issue TLS certificates.

fly_assign_ip

Assign ip

Assign a new IP address to a Fly app. Returns the created assignment with its ip, type, region and creation time. An egress_pair request returns an ip_pair instead of a single ip. Use fly_list_ip_assignments to see existing addresses first.

Parameters

Name

Type

Required

Description

app_name

string

Required

Name of the Fly app, for example my-app. Use fly_list_apps to find app names.

type

string

Required

Type of address to allocate. Use v4 or v6 for a dedicated public address, shared_v4 for a shared IPv4, private_v6 for a private address, egress_v4 or egress_v6 for outbound addresses, or egress_pair for both outbound addresses. One of: `v4`, `v6`, `shared_v4`, `private_v6`, `egress_v4`, `egress_v6`, `egress_pair`.

network

string

Optional

Name of a custom private network for the address. Leave empty for the default network.

org_slug

string

Optional

Slug of the Fly organization, or personal for your personal organization.

region

string

Optional

Region code, for example iad, ams or syd. Use fly_list_regions to see valid codes.

service_name

string

Optional

Name of the service the address is assigned to. Leave empty for the whole app.

fly_check_certificate

Check certificate

fly_cordon_machine

Cordon machine

fly_create_app

Create app

fly_create_machine

Create machine

fly_create_volume

Create volume

fly_delete_app

Delete app

fly_delete_machine

Delete machine

fly_delete_secret

Delete secret

fly_extend_volume

Extend volume

fly_get_app

Get app

fly_get_certificate

Get certificate

fly_get_machine

Get machine

fly_get_machine_metadata

Get machine metadata

fly_get_secret

Get secret

fly_list_apps

List apps

fly_list_ip_assignments

List ip assignments

fly_list_machine_processes

List machine processes

fly_list_machines

List machines

fly_list_org_volumes

List org volumes

fly_list_secrets

List secrets

fly_remove_ip

Remove ip

fly_request_acme_certificate

Request acme certificate

fly_set_machine_metadata_value

Set machine metadata value

fly_signal_machine

Signal machine

fly_start_machine

Start machine

fly_stop_machine

Stop machine

fly_uncordon_machine

Uncordon machine

fly_update_machine

Update machine

fly_update_machine_metadata

Update machine metadata

For more tools, view docs.

Build your Agent

Same auth pattern across LangChain, OpenAI, Anthropic, and Google ADK.

import { ScalekitClient } from "@scalekit-sdk/node";
import { createReactAgent } from "@langchain/langgraph/prebuilt";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

// Fly.io tools scoped to this user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["fly"], toolNames: [
    "fly_list_machines",
    "fly_restart_machine",
    "fly_exec_machine"] },
  pageSize: 100,
});

const agent = createReactAgent({ llm, tools });
await agent.invoke({ messages: [{ role: "user", content: "List the stopped Machines in the checkout app" }] });

import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["fly"] }, pageSize: 100,
});

const res = await openai.chat.completions.create({
  model: "gpt-5",
  messages: [{ role: "user", content: "List the stopped Machines in the checkout app" }],
  tools,
});

// Execute the tool call with the user's vaulted Fly.io access token
await sk.tools.executeTool(res.choices[0].message.tool_calls[0], "user_123");

import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["fly"] }, pageSize: 100,
});

const msg = await anthropic.messages.create({
  model: "claude-sonnet-5",
  max_tokens: 1024,
  messages: [{ role: "user", content: "List the stopped Machines in the checkout app" }],
  tools,
});

// Tool call runs with the user's vaulted Fly.io access token
await sk.tools.executeTool(msg.content, "user_123");

import { Agent } from "@google/adk/agents";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["fly"] }, pageSize: 100,
});

const agent = new Agent({
  name: "platform_agent",
  model: "gemini-2.5-pro",
  instruction: "Fly.io tools scoped to this user",
  tools,
});

await agent.run("List the stopped Machines in the checkout app");

Try these prompts

Copy any prompt into your agent. Each maps directly to a Fly.io tool. Click to copy, paste into your agent, done.

Apps and Machines

Copy the prompt

Copied

List the Machines in the checkout app and their regions.

Copy the prompt

Copied

Restart Machine 3d8d9 in the checkout app.

Copy the prompt

Copied

Run df -h on the primary Machine in the api app.

Storage

Copy the prompt

Copied

List the volumes in the api app and their sizes.

Copy the prompt

Copied

Take a snapshot of volume vol_42 before the migration.

Copy the prompt

Copied

Extend volume vol_42 to 20 GB.

Secrets and certificates

Copy the prompt

Copied

List the secrets set on the api app.

Copy the prompt

Copied

Request a certificate for app.acme.com on the web app.

Copy the prompt

Copied

Check the DNS and certificate status for app.acme.com.

SEE HOW AUTH WORKS

Each user connects their own Fly.io access token once, and Scalekit sends it with every call. Tokens stay vaulted, every call is scope checked, and every action is logged.

Authorize

Your user connects

Fly.io

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

Store

Their

Fly.io

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

Resolve

When your agent calls a

Fly.io

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

Audit

Every

Fly.io

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

See the same per-user auth pattern across other developer tools and cloud connectors.

Engineering Teams

DevOps assistant agent

Polls GitHub for failing checks and stale PRs, opens Linear issues for the ones that need work, and posts a daily digest to Slack. It acts as the engineer, not a shared service account.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

01.

Shared tokens break per-user analytics

A shared Fly.io access token looks fine in a demo. In production every Machine restart looks like one service account, and you cannot tell which user triggered it. Scalekit resolves the credential of the actual user who triggered the agent, never a shared bot.

// shared token
audit → bot_service_account

// scalekit
audit → user_abc ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

Fly.io today. Ten connectors tomorrow.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access Fly.io as the user or through a shared access token?

As the user. Each user connects their own Fly.io access token once, and Scalekit sends it with every call. Machine changes, volume operations, and secret updates the agent makes are attributed to that user in your audit trail, not a shared service account.

Where is the Fly.io access token stored?

In Scalekit's managed AES-256 token vault, namespaced per tenant. To rotate it, the user reconnects with a new access token. Revocation is a single dashboard action. Credentials never appear in prompts, logs, or LLM context.

Can I limit what the agent does in Fly.io?

Yes. Filter by tool name in listScopedTools to expose only what you want, for example Machine and volume tools without fly_delete_app and fly_delete_volume, which remove an app's Machines and destroy volume data. Scalekit also enforces scope checks before every API call.

What happens when a user revokes Fly.io access?

The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Can the agent see the values of Fly app secrets?

No. fly_list_secrets and fly_get_secret return a secret's name, digest, and timestamps, never the value. fly_set_secret can create or overwrite a secret, and running Machines pick up the new value on their next update.