Download PDFMarkdown Version
ClaudeChatGPTPerplexityGeminiMicrosoft CopilotRaycastMeta AIGrokZ.aiQwenKimi
DeepSeekMistralCursorVS CodeWindsurfJetBrainsClineLovableVercel AI SDKLangChain

Use Fly.io with your AI.

Connect your account once and let the AI you already use work with it, without building another integration. Manage edge compute infrastructure via Fly.io. list apps, control machines (VMs), manage volumes and certificates from any AI agent.

Included with plan

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Complete set · 13 capabilities

The complete Fly.io capability set.

These are the exact actions your AI can choose when you ask it to work with Fly.io.

Capability set01 / 04

01-04

4 capabilities in this set.

Part of 13 available through Fly.io.

  1. 01

    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

  2. 02

    Get machine

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

  3. 03

    List apps

    Io account. Each app is a collection of machines (VMs) running your code across Fly.io's globalThis 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

  4. 04

    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

Capability set02 / 04

05-07

3 capabilities in this set.

Part of 13 available through Fly.io.

  1. 05

    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

  2. 06

    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

  3. 07

    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

Capability set03 / 04

08-10

3 capabilities in this set.

Part of 13 available through Fly.io.

  1. 08

    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

  2. 09

    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

  3. 10

    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

Capability set04 / 04

11-13

3 capabilities in this set.

Part of 13 available through Fly.io.

  1. 11

    Restart machine

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

  2. 12

    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

  3. 13

    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

Observed, not estimated

923ms average. Fast in production.

Fly.io is checked daily against the live service.

Daily averagePeak 1118ms
Aug 20Today
Fastest day
744ms
Slowest day
1118ms
14-day trend
Slowing+12%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 13 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Fly.io, so you can see the experience inside your AI.

It does not authenticate your account with Fly.io. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Fly.io Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_dpmA9VGlYfKEyJ7rmW4BBpIY4hqdhZJNSHXzxXP5/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Fly.io capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "flyio-alternative-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_dpmA9VGlYfKEyJ7rmW4BBpIY4hqdhZJNSHXzxXP5/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

FAQ

Questions Fly.io owners ask.

  • 01

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

    Log in to the 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.

  • 02

    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.

  • 03

    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.

  • 04

    How do I deploy a machine in a specific region?

    Use the create_machine capability 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.

Explore

More in Loved By Devs

Suggestions