Compatible with every major AI agent and IDE
What is the Fly.io Extended MCP Server?
Connect your Fly.io account to any AI agent to orchestrate your cloud infrastructure through natural language. This server provides full access to the Fly Machines API, allowing for granular control over global deployments.
What you can do
- App Management — Create, list, and delete Fly Apps across your organizations.
- Machine Lifecycle — Start, stop, suspend, and update individual Machines with precise configuration control.
- Storage & Volumes — Provision, extend, and manage persistent volumes and snapshots for your stateful applications.
- Network & Security — Manage ACME and custom certificates, and request OIDC tokens for secure workload identity.
- Real-time Monitoring — Wait for specific machine states and fetch detailed metadata for debugging and orchestration.
How it works
- Subscribe to this server
- Enter your Fly.io Personal Access Token
- Start deploying and managing your global infrastructure from Claude, Cursor, or any MCP client
Who is this for?
- DevOps Engineers — Automate scaling, machine restarts, and volume management without leaving the terminal or chat interface.
- Full-stack Developers — Deploy new app instances and check machine statuses directly from your code editor.
- SRE Teams — Quickly inspect infrastructure health and manage certificates during incident response.
Built-in capabilities (28)
Trigger DNS validation check for a certificate
Request a Let's Encrypt certificate
Create a new Fly App
Import a custom PEM certificate
Create a lease for a Machine
Requires a config object containing at least the image. Create a new Fly Machine
Create a new volume
Delete a Fly App
Remove hostname and certificates
Delete a Machine
Delete a volume
Increase volume size
Get details about a Fly App
Get certificate details
Get Machine details
Get volume details
List Fly Apps
List all certificates for an app
List all Machines in an app
List volume snapshots
List all volumes in an app
Release a lease for a Machine
Request an OpenID Connect (OIDC) token
Start a Machine
Stop a Machine
Suspend a Machine
Update Machine configuration
Wait for a specific Machine state
Why Cursor?
Cursor's Agent mode turns Fly.io Extended into an in-editor superpower. Ask Cursor to generate code using live data from Fly.io Extended and it fetches, processes, and writes. all in a single agentic loop. 28 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Fly.io Extended in Cursor
Fly.io Extended and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Fly.io Extended to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Fly.io Extended in Cursor
The Fly.io Extended 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. All 28 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor 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, zero maintenance.

* 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
How Vinkius secures
Fly.io Extended for Cursor
Every tool call from Cursor to the Fly.io Extended MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I start or stop a specific Fly Machine using this server?
Yes. You can use the start_machine and stop_machine tools by providing the app name and the specific Machine ID. You can also use suspend_machine for compatible workloads.
How do I create a new application in a specific organization?
Use the create_app tool. You will need to provide a unique app_name and the org_slug of the target organization where you want the app to be provisioned.
Is it possible to manage persistent storage volumes?
Absolutely. The server includes tools like create_volume, list_volumes, extend_volume, and delete_volume to handle the full lifecycle of your Fly Volumes.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.
Explore More MCP Servers
View all →
Auth0 Alternative
13 toolsManage identity and access via Auth0 — list users, create accounts, audit logs, manage clients and review connections from any AI agent.

Judge.me
10 toolsManage product reviews, questions, and ratings via Judge.me API.

Todoist
12 toolsOrganize your personal and team tasks with the productivity app that millions trust to stay on top of everything that matters.

Mistral AI (Frontier LLMs & Embeddings)
7 toolsManage AI inference via Mistral — execute chat completions, generate RAG embeddings, and audit frontier models.
