How do I create a Fly.io Personal Access Token?

Log in to the [**Fly.io Dashboard**](https://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.

Fly.io Alternative MCP Server for VS Code Copilot 13 tools — connect in under 2 minutes

Name: Fly.io Alternative
Availability: InStock
Author: Vinkius

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

Built by Vinkius GDPR 13 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 Alternative and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "flyio-alternative": {
      "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 Alternative MCP Server

Connect your Fly.io account to any AI agent and take full control of your edge compute infrastructure through natural conversation.

GitHub Copilot Agent mode brings Fly.io Alternative data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 13 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 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

The Fly.io Alternative MCP Server exposes 13 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 Alternative to VS Code Copilot via MCP

Follow these steps to integrate the Fly.io Alternative 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 Alternative

Ask Copilot: "Using Fly.io Alternative, help me...". 13 tools available

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

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Fly.io Alternative 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 Alternative + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Fly.io Alternative 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 Alternative MCP Tools for VS Code Copilot (13)

These 13 tools become available when you connect Fly.io Alternative to VS Code Copilot via MCP:

create_machine

io 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

create_volume

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

delete_machine

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

get_app

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

get_machine

Provide both the app_name and machine_id. Get details for a specific Fly.io machine

list_apps

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

list_certificates

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

list_machines

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

list_volumes

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

restart_machine

Useful for applying configuration changes or recovering from issues. Provide the app_name and machine_id. Restart a Fly.io machine

start_machine

The machine will boot and begin running its configured image. Provide the app_name and machine_id. Start a stopped Fly.io machine

stop_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

update_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

Example Prompts for Fly.io Alternative in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Fly.io Alternative immediately.

"Show me all machines running in my web-api app."

"Start the stopped machine in Tokyo and restart the one in Frankfurt."

"Create a new 10GB volume called 'data' for my database app in Virginia."

Troubleshooting Fly.io Alternative MCP Server with VS Code Copilot

Common issues when connecting Fly.io Alternative 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 Alternative + VS Code Copilot FAQ

Common questions about integrating Fly.io Alternative 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.