Skip to directory

Fly.io flyctl MCP

Fly.io

stdio; Fly docs also describe SSE and Streamable HTTP patterns for deployed MCP servers.4+ documented tools0

About Fly.io flyctl MCP

The official flyctl MCP server exposes documented Fly.io CLI capabilities for inspecting and managing applications, machines, organizations, volumes, certificates, logs, secrets, and platform status.

What you can use it for

  • Inspect Fly.io platform status
  • List and manage apps and machines
  • Read application logs
  • Manage certificates, organizations, volumes, and secrets
Connection and setup
Hosting
Local flyctl process; Fly.io also documents deployment/proxy patterns for MCP servers.
Transport
stdio; Fly docs also describe SSE and Streamable HTTP patterns for deployed MCP servers.
Endpoint
Local process; no hosted endpoint documented
Authentication
Local flyctl authentication for account operations. When running this MCP on a separate machine, documented token sources are an Authorization bearer token, --access-token, or FLY_ACCESS_TOKEN.

Requirements

  • Install flyctl using the official Fly.io installation instructions.
  • Authenticate with a Fly.io account for account and application operations.
  • Use a trusted MCP client. The server can make changes to Fly.io resources under the account's permissions.

Setup steps

  1. Install flyctl and sign in with the Fly.io account that should govern access.
  2. Use the documented `fly mcp server --<client>` command to register the MCP for one of its listed clients; the documentation lists Claude, Cursor, Neovim, VS Code, Windsurf, and Zed.
  3. For a custom config file, the docs state that `--config` accepts a config path; check the selected client's format before using it.
  4. For a harmless smoke check, launch the documented inspector mode `fly mcp server -i`, connect to 127.0.0.1:6274, select List Tools, and call a read-only status tool such as fly-platform-status.
Tools 4+

flyctl builds the exposed surface from supported commands and subcommands, so the complete list changes with the installed flyctl version and available command set. Official docs provide example names including fly-platform-status, fly-orgs-list, fly-apps-list, and fly-machines-list.

  • fly-platform-status

    Example Fly platform status tool named in the official inspector walkthrough.

    01
  • fly-orgs-list

    Example organizations-list tool named in the official inspector walkthrough.

    02
  • fly-apps-list

    Example apps-list tool named in the official inspector walkthrough.

    03
  • fly-machines-list

    Example machines-list tool named in the official inspector walkthrough.

    04

This server’s available tools can vary by account, permissions, or configuration. The list shown is not its full runtime catalog.

Limitations and notes
  • The MCP tool surface is generated from flyctl command groups and may change with flyctl versions.
  • Several exposed operations can create, change, or delete Fly.io resources; access is bounded by the signed-in Fly.io account.
  • Remote deployment and proxy documentation is marked beta.
  • This record describes the local flyctl MCP server. Fly also launched a separate hosted Fly MCP beta in October 2026.
Original sources
  • official cli mcp documentation

    Documents flyctl MCP setup flags, supported command groups, example tool names, inspector procedure, and remote token handling.

  • official transport documentation

    Documents Fly.io MCP stdio proxy behavior and notes transport/deployment guidance is beta.

  • official publisher avatar

    Verified Superfly/Fly.io GitHub organization avatar downloaded, decoded, and visually reviewed; used fallback tier D.

  • official tool reference

    Fly docs for the local flyctl mcp server document example tool names and command families. The newer hosted Fly MCP at https://fly.io/mcp/ is a separate beta service.

Documentation checked 2026-10-28T00:00:00Z. Connection has not been runtime tested.