Fly.io MCP Server

Fly.io's MCP server allows AI agents to deploy global application containers, configure hardware machines, manage persistent storage volumes, and scale applications on Fly.io. It enables agents to inspect app status across regions, review operational logs, and create, clone, start, or stop Machines in the regions they choose.

Start for free

Fly.io MCP Server

Benefits with Ory + Fly.io MCP Server

Fly.io's MCP server, built into the flyctl command-line tool, lets your agents manage apps, Machines, volumes, secrets, and logs on Fly.io. Scaling, restarting, or reconfiguring Machines changes production right away. Ory Agent Security lets agents check status and logs while changes to your apps stay with the deployment agents you approve.

View documentation

Use Cases

— 01 use case

Agent IAM

Incident agents read logs at Read, app creators work at Write, exec, secrets and restarts stay with Admin agents, and Block covers the rest.

Explore Agent IAM

Core Functionality

— 04 capabilities

Read, write, admin, or no access
Ory Agent Security classifies every tool on the Fly.io MCP server as read, write, or admin, so you can give each user, team, or agent type only the level it needs: read for agents checking status and logs, write for agents creating new apps and volumes, admin for deployment agents, and no access for agents with no deployment role.
Enforced before execution
Ory Agent Security checks each tool call against the user, the agent acting for them, and any sub-agent inside the agent harness, so a denied secret change stops before it reaches Fly.io, with nothing to roll back and no gateway to deploy.
Observe, then enforce
Observe mode shows which agents change Machines or secrets and for whom without blocking anything, so you can apply Ory's pre-built policy for the Fly.io MCP server and enforce it on your own schedule.
Complete audit trail
Every allow and deny decision on the Fly.io MCP server streams to your SIEM through OpenTelemetry with the user, agent, and action attached, so you can show which agent restarted or reconfigured an app, and for which user.