Fly.io MCP. Control edge compute and data state from chat.
Fly.io MCP lets your agent manage complex edge infrastructure and container orchestration through natural conversation. You can list apps, monitor machines globally, scale compute capacity dynamically, run remote commands inside containers, and handle persistent data volumes—all without touching the command line.
Give Claude and any AI agent real-world access
You can list the app spaces belonging to an organization or retrieve a list of individual microVM endpoints and their specific physical placement regions.
The system allows you to start, stop, scale up, or terminate machines dynamically based on current operational needs.
You can get the exhaustive runtime state of a machine, including its running image digest, or retrieve the operational baseline, such as anycast IPs and Wireguard network ranges for an app.
Your agent injects and runs standard shell commands inside active machines, bypassing the need for manual SSH connections.
You can list hardware NVMe Volumes attached to an app, ensuring stateful data like PostgreSQL or SQLite remains available even if compute instances fail.
Ask an AI about this
Waiting for input…
What AI agents can do with Fly.io: 10 Infrastructure Tools
These tools give your agent the power to list apps, control machine lifecycles, execute shell commands, and manage persistent storage for complex edge infrastructure.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Fly.io MCPCreate Machine
This tool provisions a new, highly available Edge Machine within an existing App space.
Delete Machine
It terminates and destroys a specific Fly Machine instance permanently.
Exec Machine
This function injects and runs shell or Bash commands inside an active machine.
Get App
It retrieves the operational baseline state of a distinct Fly App, including its...
Get Machine
This fetches the exhaustive runtime status for a single machine, detailing its...
List Apps
It lists all App spaces belonging to an organization, identifying their container and storage components.
List Machines
This function retrieves unique identifiers and explicit placement regions for individual machines within an app.
List Volumes
It lists persistent hardware NVMe Volumes attached to an App, crucial for stateful...
Start Machine
This tool boots up a Fly Machine that was previously stopped or suspended.
Stop Machine
It gracefully halts an active, running internal machine instance.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on each call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Fly.io, then connect any of our 5,200+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,200+ others, all in one place
- Add new capabilities to your AI anytime you want
- Connections are secured and governed automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog weekly
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Fly.io. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS CLOUD
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on each call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
The manual toil of global infrastructure monitoring.
Right now, checking on your services means jumping through hoops. You open the cloud console for App A to check its Anycast IPs, then switch tabs to run a `kubectl get pods` command on the cluster master, and finally log into an SSH client just to run `docker logs` on one specific machine. It's slow, it's error-prone, and you lose track of whether you checked every single region.
With this MCP, you tell your agent what you need: 'What is the status of App A in all regions?' Your agent handles the complexity, synthesizing data from multiple endpoints into a single, conversational answer. You get immediate visibility without ever leaving the chat window.
Fly.io MCP delivers comprehensive control over machine lifecycle.
The need to manually manage machine uptime—whether it's restarting a stopped worker or scaling up during peak load—requires juggling multiple commands (`start_machine`, `create_machine`) and monitoring the outcomes of each one. This is tedious, especially when you're on call.
Now, your agent handles that entire workflow conversationally. You tell it to scale capacity, and it provisions the new machines, confirming their status immediately. It’s instant control over distributed compute.
What Fly.io MCP does for your AI
This connector connects your account to Fly.io, giving you full control over distributed edge computing resources via any MCP-compatible client. Forget logging into separate dashboards or writing complex CLI scripts just to check machine health across global regions. Instead, talk to your agent and get real-time status updates on everything from active container assignments to persistent storage volumes.
You can ask the system to list all app spaces belonging to an organization or identify specific dedicated IPv4/IPv6 IPs assigned by the cluster master. Need more compute power? Your agent provisions new, highly available Edge Machines to scale capacity instantly. If something goes wrong, you don't have to SSH in; your agent runs shell commands directly inside active machines through the hypervisor API.
This means you can diagnose issues or run database migrations without manual intervention. All of this infrastructure control is managed seamlessly through Vinkius, making it one place for all your edge resources.
019d759c-a6d2-72d6-a076-39b0c01b1267 How to set up Fly.io MCP
The bottom line is that you manage complex global edge computing resources using plain conversation instead of platform CLIs.
Subscribe to this MCP and provide your Fly.io API Token.
Connect your agent from any MCP-compatible client, giving it access to the Fly.io infrastructure layer.
Use natural language commands to perform actions like listing apps or running diagnostics on machines.
Who uses Fly.io MCP
This MCP is essential for the Ops Engineer who gets tired of clicking through multiple dashboards just to check machine health across three different regions. It's built for people whose job is keeping critical, globally distributed services running 24/7.
Uses the MCP to monitor system execution logs and run diagnostic commands on active machines in real time, diagnosing failures without manual CLI interactions.
Manages machine health by listing all app spaces or provisioning new highly available Edge Machines when capacity starts running low.
Triggers restarts, runs database migrations, and verifies deployment digests directly from a chat interface rather than jumping into the terminal.
Benefits of connecting Fly.io MCP
You manage the entire lifecycle of your infrastructure—from listing apps using list_apps to ensuring machines are running via start_machine. This eliminates context switching between multiple cloud tools.
Never manually SSH into a machine again. Use exec_machine to run diagnostic commands like ps aux directly from your agent, giving you immediate shell output without complex terminal setup.
Data persistence is guaranteed. By using list_volumes, you can audit attached hardware NVMe Volumes and know exactly where critical stateful data lives, independent of any single machine's uptime.
Scaling compute capacity becomes conversational. Instead of following a multi-step deployment process, your agent provisions new Edge Machines instantly with the create_machine tool.
You maintain visibility into global networking. The system can provide the operational baseline using get_app, identifying active Anycast IPs and Wireguard ranges in one query.
Fly.io MCP use cases
Debugging a service outage in a remote region
A backend developer notices high latency. They ask their agent to run get_machine on the primary web-api machine. The agent returns that the status is 'suspended.' The developer then instructs the agent to use start_machine, restoring the service and confirming connectivity via a follow-up command.
Verifying data integrity before deployment
A DevOps engineer needs to migrate user data. They first call list_volumes for the app, confirm the existence of the necessary NVMe storage. Then, they use exec_machine to run a specific database migration script inside the target machine.
Scaling up during peak traffic hours
The SRE team sees CPU spikes approaching limits. Instead of waiting for automated scaling policies, they instruct their agent to use create_machine, provisioning a new Edge Machine instantly in the busiest region and balancing load across the cluster.
Auditing network topology changes
A cloud architect needs to confirm which IPs are active for compliance. They run get_app on the service, receiving an immediate report detailing all assigned Anycast IP ranges and internal Wireguard assignments.
Fly.io MCP tradeoffs
What to watch out for, and the recommended way to handle each one.
Mistaking local state for persistent data
Assuming that running a temporary script via exec_machine will save the results or changes, leading to data loss when the machine restarts.
Always verify statefulness by using list_volumes first. If you need data to survive reboots, confirm it's saved on an attached NVMe volume rather than just in the ephemeral container layer.
Manually listing everything for a full audit
Running separate commands for every machine and then having to manually compile a list of their statuses (started, stopped, suspended) into a spreadsheet.
Use list_machines followed by get_machine on the specific endpoints. This provides an immediate, compiled view of all execution states in one chat response.
Over-relying on single machine status
Assuming that if a primary machine is 'started,' the entire application is healthy and available to users.
Check get_app first. This tool provides the holistic operational baseline, confirming not only the machines but also the global Anycast IP routing assignments for the entire service.
When to use Fly.io MCP
Use this MCP when your primary pain point is controlling infrastructure that lives across multiple physical locations (edge computing) and requires constant state management. You need to interact with a complex, containerized deployment layer without logging into a dedicated console or running boilerplate CLI scripts.
Don't use it if you just need simple messaging capabilities, file storage access outside of an app volume, or basic CRUD operations on user records; those are better handled by general API connectors. If your goal is simply to list all available apps and get a quick overview, list_apps is the starting point. But if you're doing more—like scaling capacity (create_machine) or running diagnostics (exec_machine)—this MCP gives you the necessary depth.
Frequently asked questions about Fly.io MCP
How does Fly.io MCP handle data integrity? +
The system helps manage stateful applications by allowing you to list hardware NVMe Volumes using list_volumes, which keeps persistent data separate from the compute layer.
Can I run diagnostics on a machine without SSH? +
Yes. You use the exec_machine tool, which injects and runs shell commands like ls -la directly inside an active machine via the hypervisor API, bypassing traditional SSH methods.
What if I need to scale capacity quickly? +
Use create_machine. This tool provisions new highly available Edge Machines dynamically, letting you adjust horizontal scaling without waiting for a full platform deployment cycle.
Does Fly.io MCP show me the network IPs? +
Yes. You can run get_app to retrieve the operational baseline, which includes identifying anycast assignments and internal Wireguard ranges assigned to your app.
How do I shut down a machine safely? +
Use stop_machine. This tool gracefully halts a running Fly.io internal Machine instance, minimizing potential latency issues during idle cycles.
Powerful workflows you can unlock today
MCP Workflow for Serverless Database Operations
Your staging database diverged from production three weeks ago because nobody tracks branch schemas , now the migration that works perfectly in staging fails catastrophically in production
Monitor Auto-Scaling Events Using MCP Servers
Machines monitored, cache hit rates measured, cold starts counted, scaling decisions documented , run your distributed backend from one prompt