Fly.io Alternative MCP Server
Manage edge compute infrastructure via Fly.io — list apps, control machines (VMs), manage volumes and certificates from any AI agent.
Ask AI about this MCP Server
Vinkius supports streamable HTTP and SSE.

* 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
What is the Fly.io MCP Server?
The Fly.io MCP Server gives AI agents like Claude, ChatGPT, and Cursor direct access to Fly.io via 13 tools. Manage edge compute infrastructure via Fly.io — list apps, control machines (VMs), manage volumes and certificates from any AI agent. Powered by the Vinkius - no API keys, no infrastructure, connect in under 2 minutes.
Built-in capabilities (13)
Tools for your AI Agents to operate Fly.io
Ask your AI agent "Show me all machines running in my web-api app." and get the answer without opening a single dashboard. With 13 tools connected to real Fly.io data, your agents reason over live information, cross-reference it with other MCP servers, and deliver insights you would spend hours assembling manually.
Works with Claude, ChatGPT, Cursor, and any MCP-compatible client. Powered by the Vinkius - your credentials never touch the AI model, every request is auditable. Connect in under two minutes.
Why teams choose Vinkius
One subscription gives you access to thousands of MCP servers - and you can deploy your own to the Vinkius Edge. Your AI agents only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure and security, zero maintenance.
Build your own MCP Server with our secure development framework →Vinkius works with every AI agent you already use
…and any MCP-compatible client


















Fly.io Alternative MCP Server capabilities
13 toolsio app. Requires the Docker image reference (e.g. "registry.fly.io/myapp:latest"). Optionally set the region (e.g. "iad", "sjc", "nrt"), CPU cores (1-16), memory in MB (256-8192), guest CPU kind (shared, performance) and services config. Machines start in stopped state — use start_machine after creation. Create a new machine in a Fly.io app
Requires the volume name and size in gigabytes. Optionally set the region. The volume must be attached to a machine via the machine config mounts. Create a persistent volume for a Fly.io app
The machine cannot be recovered. Optionally set force=true to delete even if the machine has an attached volume. Provide the app_name and machine_id. WARNING: this action is irreversible. Delete a Fly.io machine permanently
io app including its name, status, regions, organization and network configuration. Provide the app name (not ID). Get details for a specific Fly.io app
Provide both the app_name and machine_id. Get details for a specific Fly.io machine
io account. Each app is a collection of machines (VMs) running your code across Fly.io's global edge network. Returns app name, status, region and creation date. Use the app name for all subsequent machine, volume and certificate operations. List all Fly.io apps
io app. Each certificate has a hostname, status (issued, pending, failed) and source (lets_encrypt, self_signed, acme). Use this to audit HTTPS certificate status for your app's domains. List TLS/SSL certificates for a Fly.io app
io app. Each machine has an ID, name, state (started, stopped, created, destroyed), region, image reference, CPU/memory config and IP addresses. Machines are the fundamental compute units on Fly.io. List machines (VMs) for a Fly.io app
io app. Each volume has an ID, name, state, size in GB, region and the machine it is attached to. Volumes provide persistent storage that survives machine restarts. List persistent volumes for a Fly.io app
Useful for applying configuration changes or recovering from issues. Provide the app_name and machine_id. Restart a Fly.io machine
The machine will boot and begin running its configured image. Provide the app_name and machine_id. Start a stopped Fly.io machine
The machine will stop and release its compute resources but retains its configuration and data. Provide the app_name and machine_id. Stop a running Fly.io machine
You can modify the Docker image, CPU/memory allocation, services config, mounts and more. Provide the app_name, machine_id and a JSON body with the fields to update. Update a Fly.io machine configuration
What the Fly.io Alternative MCP Server unlocks
Connect your Fly.io account to any AI agent and take full control of your edge compute infrastructure through natural conversation.
What you can do
- App Management — List all apps and retrieve their configuration details including regions, status and organization
- Machine Lifecycle — Create, start, stop, restart, update and delete machines (VMs) with full control over CPU, memory, region and image
- Machine Inspection — View machine state, configuration, services, health checks and IP addresses
- Persistent Volumes — List and create persistent storage volumes that survive machine restarts and redeployments
- Certificate Management — Review TLS/SSL certificates and their issuance status for app domains
- Global Deployment — Deploy machines across Fly.io's global regions (iad, sjc, nrt, fra, syd, etc.) for low-latency access
How it works
1. Subscribe to this server
2. Enter your Fly.io Personal Access Token
3. Start managing your edge infrastructure from Claude, Cursor, or any MCP-compatible client
Stop using the CLI or web dashboard to manage individual VMs. Your AI acts as a dedicated edge infrastructure engineer.
Who is this for?
- Platform Engineers — provision and manage VMs across multiple regions, scale services and monitor machine health without SSH
- DevOps Teams — inspect machine configurations, review deployments, manage persistent storage and track certificate status
- Full-Stack Developers — quickly check machine status, restart problematic VMs and verify image versions directly from chat
Frequently asked questions about the Fly.io Alternative MCP Server
How do I create a Fly.io Personal Access Token?
Log in to the Fly.io Dashboard, go to Settings > Personal Access Tokens, click Create, name your token and copy it immediately — it won't be shown again. Alternatively, use fly tokens create from the CLI after authenticating with fly auth login.
What is a Fly.io Machine and how does it work?
A Machine is a Fly.io VM (micro-VM) that runs your Docker container image. Each machine has its own CPU, memory, storage and IP address. Machines can be started, stopped, restarted and updated independently. They can run in any of Fly.io's 30+ global regions and are the fundamental compute unit of the platform.
Can I start and stop machines to save costs?
Yes! Use stop_machine to halt a machine and release its compute resources, and start_machine to boot it again. Stopped machines don't incur compute charges. This is perfect for development/staging environments that don't need to run 24/7. Persistent volumes attached to stopped machines retain all data.
How do I deploy a machine in a specific region?
Use the create_machine tool with the region parameter set to your desired Fly.io region code. Common regions include: iad (Virginia, US), sjc (San Jose, US), nrt (Tokyo, Japan), fra (Frankfurt, Germany), syd (Sydney, Australia). The full list is available in the Fly.io documentation.
More in this category
You might also like
Connect Fly.io Alternative with your favorite client
Step-by-step setup guides for every MCP-compatible client and framework:
Anthropic's native desktop app for Claude with built-in MCP support.
AI-first code editor with integrated LLM-powered coding assistance.
GitHub Copilot in VS Code with Agent mode and MCP support.
Purpose-built IDE for agentic AI coding workflows.
Autonomous AI coding agent that runs inside VS Code.
Anthropic's agentic CLI for terminal-first development.
Python SDK for building production-grade OpenAI agent workflows.
Google's framework for building production AI agents.
Type-safe agent development for Python with first-class MCP support.
TypeScript toolkit for building AI-powered web applications.
TypeScript-native agent framework for modern web stacks.
Python framework for orchestrating collaborative AI agent crews.
Leading Python framework for composable LLM applications.
Data-aware AI agent framework for structured and unstructured sources.
Microsoft's framework for multi-agent collaborative conversations.
Give your AI agents the power of Fly.io MCP Server
Production-grade Fly.io Alternative MCP Server. Verified, monitored, and maintained by Vinkius. Ready for your AI agents — connect and start using immediately.






