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 VS Code Copilot 10 tools — connect in under 2 minutes

Name: Fly.io
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 10 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

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.

GitHub Copilot Agent mode brings Fly.io data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 tools — Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

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 VS Code Copilot 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 VS Code Copilot via MCP

Follow these steps to integrate the Fly.io MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using Fly.io

Ask Copilot: "Using Fly.io, help me..." — 10 tools available

Why Use VS Code Copilot with the Fly.io MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Fly.io through the Model Context Protocol.

VS Code is used by over 70% of developers — adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Fly.io + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Fly.io MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Fly.io MCP Tools for VS Code Copilot (10)

These 10 tools become available when you connect Fly.io to VS Code Copilot 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 VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot 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 VS Code Copilot

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

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Fly.io + VS Code Copilot FAQ

Common questions about integrating Fly.io MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.