Can my agent scale up my application by creating more machines in a specific region?

Yes. Use the 'create_machine' tool. You can specify the region (e.g., 'iad', 'gru') and the Docker image. The agent will command the Fly.io orchestrator to boot up new VM instances instantly to handle increased demand.

How do I run a database migration or shell command on a live machine via chat?

Use the 'exec_machine' tool. Provide the machine ID and the command. The agent bypasses SSH entirely by interacting directly with the hypervisor API to run your binary alongside the running container securely.

Can I check the health and image version of my active machines through the agent?

Absolutely. The 'get_machine' tool retrieves exhaustive runtime states, including container health, current executing status (started/stopped), and the precise docker image digest actively booted into memory.

Fly.io MCP Server for Cursor 10 tools — connect in under 2 minutes

Name: Fly.io
Availability: InStock
Author: Vinkius

docs.cursor.com/context/model-context-protocol

Built by Vinkius GDPR 10 Tools IDE

Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Fly.io and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "flyio": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

About Fly.io MCP Server

Connect your Fly.io account to any AI agent and take full control of your edge computing and container orchestration through natural conversation.

Cursor's Agent mode turns Fly.io into an in-editor superpower. Ask Cursor to generate code using live data from Fly.io and it fetches, processes, and writes — all in a single agentic loop. 10 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.

What you can do

App Space Orchestration — List logical parent containers (Apps) spanning the Fly Edge network, identifying anycast assignments and dedicated IPv4/IPv6 IPs natively
Machine Runtime Management — Navigate and control individual MicroVM (Machine) endpoints, fetching unique IDs and explicit placement regions flawlessly
Autonomous Scaling — Provision new highly available Edge Machines to scale horizontal capacities dynamically without waiting on full platform deployments
Live Health Auditing — Examine exhaustive runtime states, returning dynamic executing statuses (started, stopped, suspended) and docker image digests in real-time
Remote Command Execution — Inject and run shell commands inside active Machines bypassing SSH by interacting directly with the hypervisor API securely
Persistent Storage Control — List hardware NVMe Volumes attached to your apps to manage stateful data like PostgreSQL or SQLite independent of compute
Network DNA Extraction — Retrieve the operational baseline of Fly Apps, identifying Wireguard ranges and cluster master regions synchronously

The Fly.io MCP Server exposes 10 tools through the Vinkius. Connect it to Cursor in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Fly.io to Cursor via MCP

Follow these steps to integrate the Fly.io MCP Server with Cursor.

Open MCP Settings

Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"

Add the server config

Paste the JSON configuration above into the mcp.json file that opens

Save the file

Cursor will automatically detect the new MCP server

Start using Fly.io

Open Agent mode in chat and ask: "Using Fly.io, help me..." — 10 tools available

Why Use Cursor with the Fly.io MCP Server

Cursor AI Code Editor provides unique advantages when paired with Fly.io through the Model Context Protocol.

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 + Cursor Use Cases

Practical scenarios where Cursor combined with the Fly.io MCP Server delivers measurable value.

Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP

Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically

Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates

Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data

Fly.io MCP Tools for Cursor (10)

These 10 tools become available when you connect Fly.io to Cursor via MCP:

create_machine

Scales horizontal capacities dynamically without waiting on full platform deployments. Provision a new highly available Edge Machine inside an App

delete_machine

The Firecracker VM is dropped, compute billing ceases immediately, and any ephemeral disk state dissolves. Fails safely if persistent volumes are explicitly attached without the force flag. Terminate and destroy a Fly Machine forever (Scale Down)

exec_machine

Useful for `ls`, `ps aux`, `top`, or running internal database diagnostic migrations. Inject and run a shell/Bash command inside an active Fly Machine

get_app

Identifies the primary Region holding the cluster master, internal Wireguard network ranges assigned, and any active Anycast IPs actively routing inbound user traffic globally. Retrieve the operational baseline state of a distinct Fly App

get_machine

Returns dynamic executing states ("started", "stopped", "suspended"), the precise docker image digest/SHA actively booted into RAM, and any mapped volume points tying persistent SQLite/Postgres logs. Get exhaustive runtime states attached to a single Fly Machine

list_apps

Apps are fundamentally distinct collections of individual microVMs (Machines), dedicated IPv4/IPv6 anycast assignments, and persistent storage volumes. List Fly.io App spaces belonging to an Organization

list_machines

Retrieves unique identifiers and explicit placement Regions (e.g., iad, ams, nrt). List individual MicroVM (Machine) endpoints inside a Fly App

list_volumes

Crucial identifier for managing stateful applications (PostgreSQL, SQLite, persistent cache) safely independent of compute instances. List persistent hardware NVMe Volumes attached to an App

start_machine

Utilized extensively when recovering paused batch processors or restarting crashed worker nodes dynamically across edge points of presence. Boot a previously stopped or suspended Fly Machine

stop_machine

Drastically reduces latency bills during idle cycles outside typical user ingress bands. Gracefully halt a running Fly.io internal Machine

Example Prompts for Fly.io in Cursor

Ready-to-use prompts you can give your Cursor agent to start working with Fly.io immediately.

"List all machines in my 'web-api' app"

"Run 'ls -la /app' on machine '918572b0' in app 'web-api'"

"Show me the persistent volumes for 'web-api'"

Troubleshooting Fly.io MCP Server with Cursor

Common issues when connecting Fly.io to Cursor through the Vinkius, and how to resolve them.

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.

Fly.io + Cursor FAQ

Common questions about integrating Fly.io MCP Server with Cursor.

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.