Fly.io Extended MCP. Control global infrastructure from conversation.
Fly.io Extended MCP connects your AI client directly to your cloud infrastructure. Provision apps, control machine lifecycles (start, stop, suspend), manage persistent volumes, and handle network certificates all from natural language commands.
Give Claude and any AI agent real-world access
Create, list, or delete entire applications hosted on Fly.io.
Start, stop, suspend, update, and wait for specific machines to reach a desired operational state.
Create new volumes, list existing ones, or increase the size of current persistent storage.
Request Let's Encrypt certificates or import custom PEM files for your services.
Get OpenID Connect tokens to verify secure workload identities across your infrastructure.
Ask an AI about this
Waiting for input…
What AI agents can do with Fly.io Extended MCP: 25 Tools
Use these tools to programmatically control every aspect of your cloud infrastructure, from deploying new apps to managing machine lifecycles and storage volumes.
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 MCPCheck Certificate
Triggers a DNS validation check to confirm a certificate's status.
Create Acme Certificate
Requests a new, valid Let's Encrypt SSL/TLS certificate for an application.
Create App
Creates and initializes a brand-new Fly.io application within your account.
Create Custom Certificate
Imports a certificate using its own PEM file, useful for internal services.
Create Lease
Creates temporary access leases for specific machines to manage resource usage.
Create Machine
Builds and deploys a new Fly machine instance using a specified configuration image.
Create Volume
Allocates and initializes a brand-new, persistent storage volume for your app.
Delete App
Permanently removes an entire Fly application from your account.
Delete Certificate
Removes both the hostname and the associated digital certificate records.
Delete Machine
Deletes a specific machine instance, taking it out of service entirely.
Delete Volume
Permanently deletes an allocated storage volume and its data.
Extend Volume
Increases the total available size of an existing persistent storage volume.
Get App
Retrieves all current operational details for a specific Fly application.
Get Certificate
Fetches detailed information about an existing certificate.
Get Machine
Retrieves the current status and configuration details for a specific machine.
Get Volume
Provides detailed metrics and metadata about an existing storage volume.
List Apps
Lists all applications currently deployed under your account namespace.
List Certificates
Retrieves a list of every certificate tied to a specific application.
List Machines
Lists all running and suspended machine instances within an app.
List Volume Snapshots
Shows you available snapshots of your persistent volumes for backup/rollback...
List Volumes
Retrieves a list of all storage volumes attached to an application.
Release Lease
Releases temporary access leases, freeing up allocated machine resources.
Request Oidc Token
Generates a secure OpenID Connect token needed for workload authentication.
Start Machine
Initiates the startup sequence, bringing a suspended or stopped machine back online.
Stop Machine
Gracefully stops a running machine, preserving its current state for later restart.
Suspend Machine
Temporarily suspends a machine to save compute resources without losing its...
Update Machine
Modifies the core configuration parameters of an existing machine instance.
Wait Machine
Pauses execution until a specified machine reaches a desired operational state...
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
Managing Cloud Infrastructure Today Is a Chore
Today, deploying or updating anything on Fly.io means context switching: checking the dashboard for machine status, running CLI commands to update configurations, manually requesting certificates in another tab, and then finally expanding storage via a separate console. It's a painful sequence of logins, copy-pasting IDs, and waiting for confirmation screens.
With this MCP, you tell your agent what you need done—for example, 'Scale up the database machine and renew its certificate.' The system handles the entire workflow: it checks the current state, calls update_machine, then runs create_acme_certificate. You just get a clean confirmation.
Fly.io Extended MCP Gives Full Control Over Your Stack
The manual steps that vanish include manually running `fly apps list`, then needing to find the machine ID to run `fly machines status`, and subsequently having to jump over to a different portal just to renew an SSL certificate.
Now, you can ask your agent to orchestrate all three actions in one prompt. You manage everything—app listing (list_apps), machine state transitions (start_machine/stop_machine), and security credentials (get_certificate)—without leaving the conversation.
What Fly.io Extended MCP does for your AI
Need to change something on your Fly.io setup? Instead of logging into a dashboard or running complex CLI scripts, you talk to your AI agent. This MCP gives your client full access to orchestrate global cloud resources through plain conversation. You can create new applications, scale up machines by changing their state, and even provision and expand storage volumes for your data.
It handles everything from managing custom network certificates to requesting OpenID Connect tokens for secure identity. If you're building complex systems, this kind of integrated control is a game changer. Vinkius makes connecting all these services simple; just subscribe and get started working with your global deployment stack.
019e3899-27c5-700d-9992-5117e2138543 How to set up Fly.io Extended MCP
The bottom line is you write what you need done; this MCP handles the complex, multi-step process of talking to your cloud provider's APIs.
Subscribe to this MCP on Vinkius and provide your Fly.io Personal Access Token.
Your AI client authenticates with the token, gaining full access to the global API endpoints.
You issue a natural language command (e.g., 'Stop the web frontend machine'). The agent translates that request into the necessary cloud operations.
Who uses Fly.io Extended MCP
This tool is for DevOps Engineers and SRE teams who get frustrated by context switching—the constant jumping between terminals, dashboards, and Git. If you spend time copying IDs or running sequential scripts just to manage a simple outage, this MCP saves your sanity.
Automating resource scaling, machine restarts, and volume management without ever leaving the chat interface.
Quickly inspecting infrastructure health, managing certificates during incident response, or updating machine configurations on the fly.
Deploying new app instances and checking machine statuses directly from their code editor without leaving their IDE workflow.
Benefits of connecting Fly.io Extended MCP
Speed up incident response. Instead of manually checking multiple dashboards, you can ask your agent to retrieve the status and metadata for a specific machine using get_machine or list_machines. This means immediate visibility into critical systems.
Simplify resource provisioning. Need more space? Use extend_volume to increase storage size on a volume without logging into a separate console. Then, use create_volume if you're starting fresh.
Manage the full lifecycle in one place. You can delete an entire app with delete_app, or granularly remove just a machine using delete_machine and then clear up related volumes.
Secure your service identity fast. When rolling out new services, use create_acme_certificate to automatically get necessary SSL credentials, avoiding manual certificate renewal steps entirely.
Maintain operational continuity. You can suspend an expensive development environment with suspend_machine when no one's using it, and then easily bring it back online later with start_machine.
Fly.io Extended MCP use cases
Debugging a production slowdown
An SRE notices high latency. Instead of SSHing into the server or clicking through monitoring tools, they ask their agent to run get_machine and list_volumes for that app. The response immediately provides detailed metadata on machine health and volume attachment points.
Rolling back a bad deployment
A full-stack developer pushes faulty code. They realize they need an older version of the data. They use list_volume_snapshots to see available backups, then initiate a restore process by calling create_volume with the snapshot ID.
Scaling for peak traffic
The DevOps team anticipates a massive user influx. Instead of manually increasing resource limits, they instruct their agent to use update_machine on multiple machines and then call start_machine across all nodes to ensure capacity is ready.
Decommissioning an old service
The team retires a legacy microservice. They don't want any remnants left behind, so they use delete_app first to wipe the app, followed by list_volumes and delete_volume for all associated storage.
Fly.io Extended MCP tradeoffs
What to watch out for, and the recommended way to handle each one.
Trying to guess IDs
The user knows a machine exists but doesn't remember its exact ID. They waste time searching through old logs or multiple tabs trying to find the right unique identifier.
First, use list_machines to see all available instances in your app. Then, you can reference the correct name or status when you run commands like stop_machine or get_machine.
Over-managing state
The user tries to start a machine that's already running and fails because they didn't check the current state. They end up manually trying multiple redundant API calls.
Always use get_machine first. This tool gives you the definitive, real-time status, letting your agent know if stop_machine or suspend_machine is even necessary.
Confusing resources
The user wants to increase storage but runs a command that only affects the application's network settings, leaving data unexpanded.
To expand storage capacity, you must use extend_volume. This tool specifically targets increasing the size of existing persistent volumes.
When to use Fly.io Extended MCP
Use this MCP if your daily work involves managing cloud infrastructure resources that require multiple steps or specific state transitions, like starting a machine, then updating its configuration, and finally verifying a certificate. You need control over the full lifecycle—from app creation (create_app) to deletion (delete_app). Don't use it if you simply need to read public data about Fly.io; for that, consult official documentation. If your goal is just basic code execution without infrastructure interaction, your AI client's native shell commands are fine. But if the task involves provisioning, scaling, or managing persistent state (volumes/certificates), this MCP is essential because it bundles all those complex actions into simple, natural language calls.
Frequently asked questions about Fly.io Extended MCP
How do I get a new SSL certificate using Fly.io Extended MCP? +
You use create_acme_certificate to request a fresh Let's Encrypt certificate for your application. The agent handles the validation process and attaches it automatically.
What is the difference between stop_machine and suspend_machine with Fly.io Extended MCP? +
Stop_machine gracefully shuts down the instance, preserving its state. Suspend_machine saves compute resources entirely, which is useful if you're just pausing development work.
Can I increase storage size using the Fly.io Extended MCP? +
Yes, use extend_volume to increase the allocated space of an existing volume without having to delete and recreate the entire data set.
Which tool should I use if I want to see all my deployed applications? +
Use list_apps. This single command retrieves a comprehensive overview of every application currently running under your account namespace.
Does Fly.io Extended MCP handle deleting the entire app and its data? +
Yes, delete_app removes the entire application container. Remember that you may still need to manually manage associated volumes using delete_volume for complete cleanup.