# Fly.io

> Run `fly mcp server` to expose flyctl operations to AI agents.

[Canonical HTML page](https://top-mcps.com/mcp/fly-io) · [server.json](https://top-mcps.com/mcp/fly-io.json) · [methodology](https://top-mcps.com/about/methodology)

## Install

### Claude Desktop — `claude_desktop_config.json`

Paste under mcpServers. Fully quit and reopen Claude after editing.

```json
{
  "mcpServers": {
    "fly-io": {
      "command": "fly",
      "args": [
        "mcp",
        "server",
        "--claude"
      ]
    }
  }
}
```

### Claude Code — `CLI or .mcp.json`

Run from your repo. Commit .mcp.json to share with your team.

```shell
claude mcp add fly-io -- fly mcp server --claude
```

### Cursor — `.cursor/mcp.json`

Global path: ~/.cursor/mcp.json. Reload window after editing.

```json
{
  "mcpServers": {
    "fly-io": {
      "command": "fly",
      "args": [
        "mcp",
        "server",
        "--claude"
      ]
    }
  }
}
```

### VS Code — `.vscode/mcp.json`

VS Code uses the "servers" key (not "mcpServers").

```jsonc
{
  "servers": {
    "fly-io": {
      "command": "fly",
      "args": [
        "mcp",
        "server",
        "--claude"
      ]
    }
  }
}
```

### Windsurf — `~/.codeium/windsurf/mcp_config.json`

Open via Cascade → hammer icon → Configure.

```json
{
  "mcpServers": {
    "fly-io": {
      "command": "fly",
      "args": [
        "mcp",
        "server",
        "--claude"
      ]
    }
  }
}
```

### Cline — `cline_mcp_settings.json`

Open via the Cline sidebar → MCP Servers → Edit.

```json
{
  "mcpServers": {
    "fly-io": {
      "command": "fly",
      "args": [
        "mcp",
        "server",
        "--claude"
      ]
    }
  }
}
```

### Continue — `~/.continue/config.json`

Continue uses modelContextProtocolServers with a transport block.

```json
{
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "stdio",
          "command": "fly",
          "args": [
            "mcp",
            "server",
            "--claude"
          ]
        }
      }
    ]
  }
}
```

### Codex CLI — `~/.codex/config.toml`

Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.

```shell
# ~/.codex/config.toml
[mcp_servers.fly-io]
command = "fly"
args = [
  "mcp",
  "server",
  "--claude",
]
```

### Zed — `~/.config/zed/settings.json`

Zed calls them "context_servers". Settings live-reload on save.

```jsonc
{
  "context_servers": {
    "fly-io": {
      "command": {
        "path": "fly",
        "args": [
          "mcp",
          "server",
          "--claude"
        ]
      }
    }
  }
}
```

### ChatGPT — `ChatGPT → Apps directory`

Fly.io doesn't ship a hosted HTTPS endpoint today. ChatGPT supports remote MCP servers only — to use this server in ChatGPT you'll need to deploy it to a public HTTPS URL first (e.g. via Cloudflare Workers or Vercel) or wait for an official remote build.

```none

```

## At a glance

- **Maintainer:** Fly.io
- **Transport:** Streamable HTTP, SSE
- **Auth model:** API key
- **Required secrets:** None
- **Supported clients:** Claude, Cursor, VS Code, Zed, Neovim, Windsurf, Fly.io accounts
- **License:** Apache-2.0
- **Language:** Go
- **Latest version:** latest
- **Last verified:** 2026-05-27
- **GitHub stars:** 1,666 (fetched 2026-06-02T11:55:52.211Z)
- **Score:** 90/100 (rubric 2026-04 — see https://top-mcps.com/about/methodology)
- **Source:** https://github.com/superfly/flyctl
- **Homepage:** https://fly.io/docs/flyctl/mcp-server/

## Quick answer

**What it does.** Exposes flyctl operations (apps, Machines, deploys, secrets) as MCP tools via an HTTP server bundled with the official CLI.

**Best for:**
- Local flyctl users who want agent access
- Managing Fly Machines from chat
- Deploys, scaling, secret rotation
- Reusing existing fly auth — no new tokens
- IDE auto-config via `--claude`, `--cursor`, `--vscode` flags

**Not for:**
- Remote-only or team deployments (no hosted MCP)
- Stability-critical ops while the feature is experimental
- Cases where flyctl isn't already installed

## Description

Fly.io ships the MCP server built into flyctl. Running `fly mcp server` exposes the same operations a human runs at the terminal — apps, Machines, deploys, secrets — as MCP tools. Authentication reuses the existing `fly auth` session.

## Why it matters

No separate install, no extra credential — `fly mcp server` runs against the same auth your terminal uses. The MCP is as up-to-date as flyctl itself.

## Key features

- Built into flyctl — no separate install
- HTTP transport on port 8080 (configurable)
- SSE + streaming modes available
- Auto-config flags for Claude, Cursor, VS Code, Zed, Neovim, Windsurf
- `fly mcp inspector` for debugging

## FAQ

### Do I need a new API token?

No — the MCP reuses your existing `fly auth` session. You can also pass `--access-token` for explicit token auth.

### How do I wire it into Claude Desktop?

Run `fly mcp server --claude` and flyctl writes the config block for you.

### Is it stable?

Fly marks the feature as experimental. Expect occasional behavior changes; verify after flyctl updates.

## Changelog

- **2026-05-27** — Refreshed install snippets and fact sheet; verified for 2026.
- **2025-07-20** — Initial directory listing.