How to Use the Fly.io MCP in VS Code Copilot

Q: How do we share the Fly.io MCP Server config in VS Code Copilot?

Commit a .vscode/mcp.json file to your team's Git repository with the server settings. Every developer on the team gets automatic access to the MCP tools as soon as they open the workspace.

Q: Can VS Code Copilot scale Fly.io instances horizontally?

Yes, the assistant uses createmachine to provision new microVMs on demand. Developers trigger this action using simple natural language commands in the Copilot Chat interface.

Q: How does VS Code Copilot verify Fly.io app health via MCP?

Copilot runs getmachine to pull the exact execution state and active Docker image digest. It reports whether instances are running, stopped, or suspended directly to your team.

Q: Does VS Code Copilot support remote command execution on Fly.io?

Yes, it utilizes execmachine to run diagnostic commands inside your active containers. This allows your team to troubleshoot production bugs directly from the editor.

Deploy and monitor Fly.io microVMs across your engineering team using VS Code Copilot and MCP.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Fly.io MCP to VS Code Copilot

Create your Vinkius account to connect Fly.io to VS Code Copilot and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Fly.io with VS Code Copilot

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Control edge deployments inside VS Code Copilot

This Fly.io MCP Server integrates your edge deployment pipeline directly into VS Code Copilot. Team members can run `list_apps` from the VS Code Copilot chat window to inspect active Fly.io organizational spaces. Your developers can check the status of staging and production Fly Machines without leaving their primary VS Code workspace. When a Fly.io service needs to scale, the developer commands Copilot to execute `create_machine` to spin up additional Firecracker VMs. This standardizes Fly.io infrastructure commands across the entire engineering team through a shared VS Code configuration file.

Run team-wide diagnostics via VS Code Copilot

The `exec_machine` tool allows VS Code Copilot to run secure shell commands inside production Fly Machines. When an incident occurs, any authorized developer can ask Copilot to inspect Fly.io logs or check process memory. Copilot executes the commands securely inside the Fly Machine and prints the results directly in the VS Code editor chat. To verify the fix, developers run `get_machine` to check if the target Fly.io VM returned to a healthy state. This workflow keeps your entire team aligned on real-time Fly.io infrastructure status during active VS Code debugging sessions.

Manage database storage in VS Code Copilot

The `list_volumes` tool exposes physical Fly.io NVMe volume states directly to the VS Code Copilot interface. When developers collaborate on stateful Fly.io services, they query the active volume mounts to prevent data loss during scale-down events. Before running `delete_machine` in VS Code Copilot, the tool checks this volume list to verify if a persistent disk is attached. This safety check prevents accidental destruction of database nodes and ensures smooth Fly.io state transitions.

Setup guide

Set up Fly.io MCP in VS Code Copilot

Prerequisites

VS Code 1.99 or later with GitHub Copilot extension
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and run "MCP: Add Server". Select HTTP (Streamable) as the server type. VS Code will create .vscode/mcp.json in your workspace.
2

Add the Fly.io MCP

Paste the JSON snippet shown on the right into your .vscode/mcp.json. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Switch to Agent mode

Open Copilot Chat (Cmd+Shift+I / Ctrl+Shift+I) and switch to Agent mode using the dropdown. MCP tools are only available in Agent mode — they do not appear in Edit or Ask modes.
4

Verify the connection

In the Copilot Chat input, type # to list available tools. You should see the Fly.io tools listed. Try asking: "List my recent Fly.io transactions" and Copilot will invoke them automatically.

.vscode/mcp.json

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

Get your connection token →

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.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Fly.io now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Fly.io MCP in VS Code Copilot

Commit a `.vscode/mcp.json` file to your team's Git repository with the server settings. Every developer on the team gets automatic access to the MCP tools as soon as they open the workspace.

Yes, the assistant uses `create_machine` to provision new microVMs on demand. Developers trigger this action using simple natural language commands in the Copilot Chat interface.

Copilot runs `get_machine` to pull the exact execution state and active Docker image digest. It reports whether instances are running, stopped, or suspended directly to your team.

Yes, it utilizes `exec_machine` to run diagnostic commands inside your active containers. This allows your team to troubleshoot production bugs directly from the editor.

Access is secured using individual Vinkius tokens that map to your organization's Fly.io API keys. The server only transmits operational metadata and machine states, ensuring your proprietary application code remains confidential.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript