Can my agent scale up my application by creating more machines in a specific region?

Yes. Use the 'create_machine' tool. You can specify the region (e.g., 'iad', 'gru') and the Docker image. The agent will command the Fly.io orchestrator to boot up new VM instances instantly to handle increased demand.

How do I run a database migration or shell command on a live machine via chat?

Use the 'exec_machine' tool. Provide the machine ID and the command. The agent bypasses SSH entirely by interacting directly with the hypervisor API to run your binary alongside the running container securely.

Can I check the health and image version of my active machines through the agent?

Absolutely. The 'get_machine' tool retrieves exhaustive runtime states, including container health, current executing status (started/stopped), and the precise docker image digest actively booted into memory.

Fly.io MCP Server for AutoGen 10 tools — connect in under 2 minutes

Name: Fly.io
Availability: InStock
Author: Vinkius

microsoft.github.io/autogen/docs/tools/mcp-tools

Built by Vinkius GDPR 10 Tools Framework

Microsoft AutoGen enables multi-agent conversations where agents negotiate, delegate, and execute tasks collaboratively. Add Fly.io as an MCP tool provider through Vinkius and every agent in the group can access live data and take action.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

import asyncio
from autogen_agentchat.agents import AssistantAgent
from autogen_ext.tools.mcp import McpWorkbench

async def main():
    # Your Vinkius token. get it at cloud.vinkius.com
    async with McpWorkbench(
        server_params={"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"},
        transport="streamable_http",
    ) as workbench:
        tools = await workbench.list_tools()
        agent = AssistantAgent(
            name="flyio_agent",
            tools=tools,
            system_message=(
                "You help users with Fly.io. "
                "10 tools available."
            ),
        )
        print(f"Agent ready with {len(tools)} tools")

asyncio.run(main())

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Fly.io MCP Server

Connect your Fly.io account to any AI agent and take full control of your edge computing and container orchestration through natural conversation.

AutoGen enables multi-agent conversations where agents negotiate, delegate, and collaboratively use Fly.io tools. Connect 10 tools through Vinkius and assign role-based access. a data analyst queries while a reviewer validates, with optional human-in-the-loop approval for sensitive operations.

What you can do

App Space Orchestration — List logical parent containers (Apps) spanning the Fly Edge network, identifying anycast assignments and dedicated IPv4/IPv6 IPs natively
Machine Runtime Management — Navigate and control individual MicroVM (Machine) endpoints, fetching unique IDs and explicit placement regions flawlessly
Autonomous Scaling — Provision new highly available Edge Machines to scale horizontal capacities dynamically without waiting on full platform deployments
Live Health Auditing — Examine exhaustive runtime states, returning dynamic executing statuses (started, stopped, suspended) and docker image digests in real-time
Remote Command Execution — Inject and run shell commands inside active Machines bypassing SSH by interacting directly with the hypervisor API securely
Persistent Storage Control — List hardware NVMe Volumes attached to your apps to manage stateful data like PostgreSQL or SQLite independent of compute
Network DNA Extraction — Retrieve the operational baseline of Fly Apps, identifying Wireguard ranges and cluster master regions synchronously

The Fly.io MCP Server exposes 10 tools through the Vinkius. Connect it to AutoGen in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Fly.io to AutoGen via MCP

Follow these steps to integrate the Fly.io MCP Server with AutoGen.

Install AutoGen

Run pip install "autogen-ext[mcp]"

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

Integrate into workflow

Use the agent in your AutoGen multi-agent orchestration

Explore tools

The workbench discovers 10 tools from Fly.io automatically

Why Use AutoGen with the Fly.io MCP Server

AutoGen provides unique advantages when paired with Fly.io through the Model Context Protocol.

Multi-agent conversations: multiple AutoGen agents discuss, delegate, and collaboratively use Fly.io tools to solve complex tasks

Role-based architecture lets you assign Fly.io tool access to specific agents. a data analyst queries while a reviewer validates

Human-in-the-loop support: agents can pause for human approval before executing sensitive Fly.io tool calls

Code execution sandbox: AutoGen agents can write and run code that processes Fly.io tool responses in an isolated environment

Fly.io + AutoGen Use Cases

Practical scenarios where AutoGen combined with the Fly.io MCP Server delivers measurable value.

Collaborative analysis: one agent queries Fly.io while another validates results and a third generates the final report

Automated review pipelines: a researcher agent fetches data from Fly.io, a critic agent evaluates quality, and a writer produces the output

Interactive planning: agents negotiate task allocation using Fly.io data to make informed decisions about resource distribution

Code generation with live data: an AutoGen coder agent writes scripts that process Fly.io responses in a sandboxed execution environment

Fly.io MCP Tools for AutoGen (10)

These 10 tools become available when you connect Fly.io to AutoGen via MCP:

create_machine

Scales horizontal capacities dynamically without waiting on full platform deployments. Provision a new highly available Edge Machine inside an App

delete_machine

The Firecracker VM is dropped, compute billing ceases immediately, and any ephemeral disk state dissolves. Fails safely if persistent volumes are explicitly attached without the force flag. Terminate and destroy a Fly Machine forever (Scale Down)

exec_machine

Useful for `ls`, `ps aux`, `top`, or running internal database diagnostic migrations. Inject and run a shell/Bash command inside an active Fly Machine

get_app

Identifies the primary Region holding the cluster master, internal Wireguard network ranges assigned, and any active Anycast IPs actively routing inbound user traffic globally. Retrieve the operational baseline state of a distinct Fly App

get_machine

Returns dynamic executing states ("started", "stopped", "suspended"), the precise docker image digest/SHA actively booted into RAM, and any mapped volume points tying persistent SQLite/Postgres logs. Get exhaustive runtime states attached to a single Fly Machine

list_apps

Apps are fundamentally distinct collections of individual microVMs (Machines), dedicated IPv4/IPv6 anycast assignments, and persistent storage volumes. List Fly.io App spaces belonging to an Organization

list_machines

Retrieves unique identifiers and explicit placement Regions (e.g., iad, ams, nrt). List individual MicroVM (Machine) endpoints inside a Fly App

list_volumes

Crucial identifier for managing stateful applications (PostgreSQL, SQLite, persistent cache) safely independent of compute instances. List persistent hardware NVMe Volumes attached to an App

start_machine

Utilized extensively when recovering paused batch processors or restarting crashed worker nodes dynamically across edge points of presence. Boot a previously stopped or suspended Fly Machine

stop_machine

Drastically reduces latency bills during idle cycles outside typical user ingress bands. Gracefully halt a running Fly.io internal Machine

Example Prompts for Fly.io in AutoGen

Ready-to-use prompts you can give your AutoGen agent to start working with Fly.io immediately.

"List all machines in my 'web-api' app"

"Run 'ls -la /app' on machine '918572b0' in app 'web-api'"

"Show me the persistent volumes for 'web-api'"

Troubleshooting Fly.io MCP Server with AutoGen

Common issues when connecting Fly.io to AutoGen through the Vinkius, and how to resolve them.

McpWorkbench not found

Install: pip install "autogen-ext[mcp]"

Fly.io + AutoGen FAQ

Common questions about integrating Fly.io MCP Server with AutoGen.

How does AutoGen connect to MCP servers?

Create an MCP tool adapter and assign it to one or more agents in the group chat. AutoGen agents can then call Fly.io tools during their conversation turns.

Can different agents have different MCP tool access?

Yes. AutoGen's role-based architecture lets you assign specific MCP tools to specific agents, so a querying agent has different capabilities than a reviewing agent.