---
title: "Fly.io flyctl MCP: review, setup & limitations · Undominated.ai"
canonical: https://undominated.ai/mcp-servers/fly/
description: "Manage Fly apps, Machines, volumes, secrets and operational status through the MCP server built into flyctl."
---

# Fly.io flyctl MCP: review, setup & limitations · Undominated.ai

> Manage Fly apps, Machines, volumes, secrets and operational status through the MCP server built into flyctl.

[← Explore all mcp servers](/mcp-servers/)

CLOUD OPERATIONS / Fly.io

# Fly.io flyctl MCP

Manage Fly apps, Machines, volumes, secrets and operational status through the MCP server built into flyctl.

 See setup guidance ↓Original source ↗

SOURCE REVIEW

 Reviewed 2026-09-21
 Evidence 6 linked sources
 Publisher Fly.io
 Licence Apache-2.0 ↗
 Revision bfd8599f5bb6
 Read what was—and wasn’t—checked ↓

“flyctl provides an MCP server that you can use to provision your application.”

 Fly.io · upstream description ↗ Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - Uses the existing Fly CLI and account credentials rather than an unrelated third-party control plane.
- Combines runtime inspection with explicit infrastructure operations for Fly applications.

### A good fit for

 - Inspect Fly app status and logs.
- Provision or change Fly infrastructure with approved tool calls.

### Weigh up before choosing

 - Tools can change Machines, volumes, secrets and organization access; the granted Fly token determines the practical reach.
- A network listener can let other callers act on your account. The local default and remote authentication need deliberate configuration.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - Official flyctl MCP setup page.
- go.mod, LICENSE, internal/command/mcp/server.go and Machine, secret and organization tool definitions.

### Our findings

 - The CLI implements stdio plus SSE and streaming HTTP modes. Remote bind and authentication behaviour are configured explicitly.
- This is the Fly account administration server, separate from fly mcp launch for hosting somebody else’s MCP service.

### Not established by this review

 - Server launch, authenticated tool calls, and release-to-source parity were not tested.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Connect a server deliberately.

Upstream setup instructions ↗

DOCUMENTED COMMAND

 fly mcp server --claude Copy command ↗

Copying does not execute this command. It may retrieve a newer version than the reviewed source.

 - Install flyctl and authenticate to the intended Fly account.
- Run the documented --claude setup command for Claude Desktop, or choose the matching editor flag in the official guide.
- Inspect tool requests before changes to infrastructure or secrets; use a suitably scoped Fly token.

### Before you start

 - flyctl on PATH.
- A Fly account and an access token with permission for the resources you intend to manage.

### Compatibility

Claude Desktop · Cursor · VS Code · Windsurf · Zed

### Implementation

Go

### Transports

stdio · SSE · Streamable HTTP

### Local CLI with Fly credentials

 - Reads account resources and application logs.
- Can provision, modify or remove supported infrastructure and manage secrets and organization membership.

### Cost model

Fly infrastructure usage and the connected model client have their own charges.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - Fly.io flyctl MCP setup and scope ↗ Checked 2026-09-21 https://fly.io/docs/mcp/flyctl-server/ Supports: summary, upstreamDescription, whySelected, bestFor, limitations, install, access, compatibility, transports, review
- flyctl MCP transport and dispatch ↗ Checked 2026-09-21 https://raw.githubusercontent.com/superfly/flyctl/bfd8599f5bb68a1db6e07f6aa321219533e1b944/internal/command/mcp/server.go Supports: review, language, transports, access
- Fly Machine tools ↗ Checked 2026-09-21 https://raw.githubusercontent.com/superfly/flyctl/bfd8599f5bb68a1db6e07f6aa321219533e1b944/internal/command/mcp/server/machine.go Supports: access, review
- Fly secret tools ↗ Checked 2026-09-21 https://raw.githubusercontent.com/superfly/flyctl/bfd8599f5bb68a1db6e07f6aa321219533e1b944/internal/command/mcp/server/secrets.go Supports: access, review
- Fly organization tools ↗ Checked 2026-09-21 https://raw.githubusercontent.com/superfly/flyctl/bfd8599f5bb68a1db6e07f6aa321219533e1b944/internal/command/mcp/server/orgs.go Supports: access, review
- flyctl Apache licence ↗ Checked 2026-09-21 https://raw.githubusercontent.com/superfly/flyctl/bfd8599f5bb68a1db6e07f6aa321219533e1b944/LICENSE Supports: license

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### Netlify MCP ↗ Connect an agent to Netlify project, deployment and environment-variable operations through the hosted server.](/mcp-servers/netlify/)[### Render MCP ↗ Inspect Render services, logs and metrics, query Postgres, and perform supported deployment operations.](/mcp-servers/render/)[### Vercel MCP ↗ Search Vercel docs, inspect projects and runtime failures, and deploy a supplied file tree through the hosted endpoint.](/mcp-servers/vercel/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)
