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 Cline 13 tools — connect in under 2 minutes

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

cline.bot/docs/mcp

Built by Vinkius GDPR 13 Tools IDE

Cline is an autonomous AI coding agent inside VS Code that plans, executes, and iterates on tasks. Wire Fly.io Alternative through Vinkius and Cline gains direct access to every tool. from data retrieval to workflow automation. without leaving the terminal.

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.

Cline operates autonomously inside VS Code. it reads your codebase, plans a strategy, and executes multi-step tasks including Fly.io Alternative tool calls without waiting for prompts between steps. Connect 13 tools through Vinkius and Cline can fetch data, generate code, and commit changes in a single autonomous run.

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 Cline 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 Cline via MCP

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

Open Cline MCP Settings

Click the MCP Servers icon in the Cline sidebar panel

Add remote server

Click "Add MCP Server" and paste the configuration above

Enable the server

Toggle the server switch to ON

Start using Fly.io Alternative

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

Why Use Cline with the Fly.io Alternative MCP Server

Cline provides unique advantages when paired with Fly.io Alternative through the Model Context Protocol.

Cline operates autonomously. it reads your codebase, plans a strategy, and executes multi-step tasks including MCP tool calls without step-by-step prompts

Runs inside VS Code, so you get MCP tool access alongside your existing extensions, terminal, and version control in a single window

Cline can create, edit, and delete files based on MCP tool responses, enabling end-to-end automation from data retrieval to code generation

Transparent execution: every tool call and file change is shown in Cline's activity log for full visibility and approval before committing

Fly.io Alternative + Cline Use Cases

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

Autonomous feature building: tell Cline to fetch data from Fly.io Alternative and scaffold a complete module with types, handlers, and tests

Codebase refactoring: use Fly.io Alternative tools to validate live data while Cline restructures your code to match updated schemas

Automated testing: Cline fetches real responses from Fly.io Alternative and generates snapshot tests or mocks based on actual payloads

Incident response: query Fly.io Alternative for real-time status and let Cline generate hotfix patches based on the findings

Fly.io Alternative MCP Tools for Cline (13)

These 13 tools become available when you connect Fly.io Alternative to Cline 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 Cline

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

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

Server shows error in sidebar

Click the server name to see logs. Verify the URL and token are correct.

Fly.io Alternative + Cline FAQ

Common questions about integrating Fly.io Alternative MCP Server with Cline.

How does Cline connect to MCP servers?

Cline reads MCP server configurations from its settings panel in VS Code. Add the server URL and Cline discovers all available tools on initialization.