Skip to content
Fly.io

Fly.ioMCP Server

by Fly.io
Added to Onei
Docs
Developer ToolsCloud & Infrastructure

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: Railway

by Railway

Railway's official MCP server, bundled with the Railway CLI — 40+ tools for projects, services, deployments, variables, domains and observability, with destructive actions gated behind explicit confirmation.

Cloud & Infrastructure

MCP: Netlify

by Netlify

Netlify's official MCP server, wrapping the Netlify API and CLI so agents can create projects, deploy, manage secrets, extensions and access controls.

Cloud & Infrastructure

MCP: Vercel

by Vercel

Vercel's official remote MCP server — search docs, manage projects and deployments, read build logs, and query Web Analytics.

Cloud & Infrastructure

MCP: Cloudsmith MCP

by Cloudsmith

Cloudsmith's official MCP server, built into its CLI: manage artifact repositories, packages and policies through an agent, with write operations off by default.

Developer Tools
Browse all MCP servers →