# Fly.io MCP server

> Manage Fly.io apps, Machines, volumes, secrets, Managed Postgres and Sprites from your AI client

- Listing: https://mcp.tc/i/fly-io-2
- Connect: use the server's own URL `https://mcp.fly.io` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: OAuth sign-in
- Category: [Cloud & DevOps](https://mcp.tc/c/cloud-devops)
- Vendor: Fly.io
- Homepage: <https://mcp.fly.io>

## About

Connects an AI client to Fly.io so it can build, run and manage apps, Machines, volumes, secrets, Managed Postgres and Sprites. Permissions are scoped, and destructive actions such as deleting apps or destroying Machines require explicit authorization.

Runs as a hosted remote endpoint over streamable HTTP at https://mcp.fly.io. Users sign in through fly.io in the browser with OAuth, choose an organization and review the requested access. No API token needs to be pasted. Access can be revoked from the Fly.io account's MCP Clients page.

## What it can do

- Manage Fly apps and Machines, including start, stop and create
- Work with Sprites
- Manage volumes and secrets
- Manage Managed Postgres
- Read certificates and app context
- Scoped OAuth permissions for destructive actions

## Example prompts

- "List the Sprites I can access on Fly.io"
- "Show the Machines running in my Fly app"
- "Stop the Machine in my staging app on Fly.io"
- "Inspect the configuration of my Fly app before I delete it"

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http fly-io-2 https://mcp.fly.io
```

2. Start Claude Code, type `/mcp`, pick **fly-io-2** and choose **Authenticate**. A browser window opens for the Fly.io sign-in.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.

2. Name it **Fly.io** and paste this URL:

```url
https://mcp.fly.io
```

3. Click **Add**, then **Connect**, and sign in when Fly.io asks.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Fly.io&connectorUrl=https%3A%2F%2Fmcp.fly.io>) (opens connector settings)

2. Check that the URL reads `https://mcp.fly.io` and click **Add**.

3. Click **Connect** and sign in when Fly.io asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, go to **Plugins**, select **+**, then **Add custom MCP server**.

2. Enter a name for the server.

3. Under **Connection**, paste `https://mcp.fly.io` as the server URL, then for authentication choose **OAuth**. ChatGPT sends you to Fly.io to sign in.

4. Check **I understand and want to continue**, then select **Create as a plugin**.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=fly-io-2&config=eyJ1cmwiOiJodHRwczovL21jcC5mbHkuaW8ifQ%3D%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "fly-io-2": {
      "url": "https://mcp.fly.io"
    }
  }
}
```

Cursor shows **Needs authentication** next to the server. Click the button beside it to sign in.

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=fly-io-2&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.fly.io%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"fly-io-2","type":"http","url":"https://mcp.fly.io"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "fly-io-2": {
      "type": "http",
      "url": "https://mcp.fly.io"
    }
  }
}
```

VS Code asks you to sign in the first time the server starts.

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "fly-io-2": {
      "serverUrl": "https://mcp.fly.io"
    }
  }
}
```

2. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add fly-io-2 --url https://mcp.fly.io
codex mcp login fly-io-2
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.fly-io-2]
url = "https://mcp.fly.io"
```

### Gemini CLI

```bash
gemini mcp add --transport http fly-io-2 https://mcp.fly.io
```

Then, inside Gemini CLI, run `/mcp auth fly-io-2` to sign in.

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "fly-io-2": {
      "type": "http",
      "url": "https://mcp.fly.io"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://mcp.fly.io`.

## Details

- Server version: 0.1.0
- Last checked: 2026-11-18 (reachable, asks for credentials)
- Listed: 2026-11-03
- Updated: 2026-11-03

---
Source: https://mcp.tc/i/fly-io-2 (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
