Back to MCP Servers
🧩

fly-io MCP Server

API key required

MCP server for managing Fly.io machines, apps, logs, and Docker images.

To add fly-io to Claude, run the install command below or copy the ready-made config for Claude Code, Claude Desktop, Cursor and VS Code further down. Restart your client after adding it and its tools show up in your next conversation. It needs 5 environment variables, listed below.

Cloud

Install

npx -y fly-io-mcp-server@0.1.7

Environment variables

FLY_IO_API_TOKENSet in your MCP config
FLY_IO_APP_NAMESet in your MCP config
ENABLED_TOOLGROUPSSet in your MCP config
SKIP_HEALTH_CHECKSSet in your MCP config
DISABLE_DOCKER_CLI_TOOLSSet in your MCP config

Install with your client

Terminal
claude mcp add fly-io --env FLY_IO_API_TOKEN=<YOUR_FLY_IO_API_TOKEN> --env FLY_IO_APP_NAME=<YOUR_FLY_IO_APP_NAME> --env ENABLED_TOOLGROUPS=<YOUR_ENABLED_TOOLGROUPS> --env SKIP_HEALTH_CHECKS=<YOUR_SKIP_HEALTH_CHECKS> --env DISABLE_DOCKER_CLI_TOOLS=<YOUR_DISABLE_DOCKER_CLI_TOOLS> -- npx -y fly-io-mcp-server@0.1.7

Run this in a terminal to add the server to Claude Code.

What this does

fly-io exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

FLY_IO_API_TOKEN
FLY_IO_APP_NAME
ENABLED_TOOLGROUPS
SKIP_HEALTH_CHECKS
DISABLE_DOCKER_CLI_TOOLS

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

Frequently asked questions

How do I install fly-io?

Run the Claude Code command in the install section to add fly-io to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with fly-io?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to fly-io as well.

Does fly-io need an API key?

Yes. Before it can run, set these environment variables: FLY_IO_API_TOKEN, FLY_IO_APP_NAME, ENABLED_TOOLGROUPS, SKIP_HEALTH_CHECKS, DISABLE_DOCKER_CLI_TOOLS. They go in the env block of your MCP config.

Imported from the Official MCP Registry. The details above come from the registry entry; the maker can claim this listing to correct them, add docs, and see its traffic.

Is this your MCP server?

Claim this listing to see its traffic, fix details yourself, and skip the review queue on future updates.

Listed on clauderules.net

Add this badge to your README

Show visitors this server is listed in the ClaudeRules directory. The badge links straight to this listing.

Markdown
[![Listed on clauderules.net](https://clauderules.net/api/badge/com-pulsemcp-fly-io)](https://clauderules.net/mcp/com-pulsemcp-fly-io)
HTML
<a href="https://clauderules.net/mcp/com-pulsemcp-fly-io" target="_blank" rel="noopener noreferrer"><img src="https://clauderules.net/api/badge/com-pulsemcp-fly-io" alt="Listed on clauderules.net" /></a>