Skip to content

Summary

Fly.io's MCP server, built into flyctl — provision and inspect Fly apps from an agent, with subcommands that also deploy and proxy other MCP servers onto Fly machines.

Features

  • `fly mcp server` exposes flyctl itself, reusing your existing Fly authentication
  • --claude, --cursor, --vscode, --zed, --neovim and --windsurf write the client config for you
  • stdio by default; --sse and --stream switch transports, --bind-addr and --port set the listener
  • `fly mcp launch` deploys an npx / uv / go run / Docker stdio server onto a Fly machine
  • `fly mcp wrap`, `proxy`, `add` and `remove` turn a local stdio server into a reachable one
  • `list`, `logs`, `inspect` and `destroy` manage servers launched on Fly
  • --inspector launches the MCP inspector for debugging a server

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

  1. Open your agent's MCP configuration file.
  2. Merge the snippet below into it.
  3. Restart the agent — the "Fly.io" tools will be available.
{
  "mcpServers": {
    "fly-mcp": {
      "command": "fly",
      "args": [
        "mcp",
        "server"
      ]
    }
  }
}

Description

Fly.io runs applications as Firecracker microVMs close to users. Its MCP support ships inside flyctl, the Fly CLI, rather than as a separate package: fly mcp server starts a flyctl MCP server that an agent can drive to provision and inspect your Fly applications, reusing the authentication flyctl already holds.

Setup is a flag, not a config file. fly mcp server --claude writes the entry into Claude Desktop's configuration for you; --cursor, --vscode, --zed, --neovim and --windsurf do the same for those clients, and --config takes explicit config paths when your client is not on the list. --server names the entry. For transports other than stdio, --sse and --stream switch to Server-Sent Events or HTTP streaming, with --bind-addr (default 127.0.0.1) and --port (default 8080) controlling where it listens. -i / --inspector launches the MCP inspector for debugging, and -t / --access-token supplies a Fly API token in place of an interactive login.

The other half is hosting other people's servers. fly mcp launch takes an npx, uv, go run or Docker stdio MCP server and puts it on a Fly machine, so a server designed to run on your laptop becomes something your team — or a remote agent — can reach. fly mcp wrap wraps a stdio program, fly mcp proxy starts a proxy client, and add / remove manage the proxy entry in a client's config. list, logs, inspect and destroy cover the lifecycle of servers you have launched this way.

Every fly mcp subcommand is marked experimental, so expect the surface to move. You will need flyctl installed and authenticated; Node.js is required only if you want the MCP inspector.

Related MCP Servers

MCP: Engram

by Gentleman Programming

New

Persistent memory for coding agents as a single Go binary — SQLite and FTS5 behind MCP, an HTTP API, a CLI and a TUI, with no Node, Python or Docker required.

MCP: agent-device

by Callstack

New

Give a coding agent a live feedback loop on real mobile, TV and desktop apps — inspect, tap, type and capture evidence on iOS, Android and HarmonyOS over MCP or a CLI.

New

The official W&B MCP server: query experiment runs, Weave LLM traces, artifacts and registries in natural language, and write findings back as a W&B report.

New

Replicate's official MCP server: search thousands of hosted models, read their schemas, and run predictions on image, video, audio and language models from inside an agent.

Browse all MCP servers →