com.pulsemcp/fly-iocloud

fly-io

Verified · 29 days ago

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

Install

claude mcp add fly-io -- npx -y [email protected]

Requires: FLY_IO_API_TOKEN, FLY_IO_APP_NAME, ENABLED_TOOLGROUPS, SKIP_HEALTH_CHECKS, DISABLE_DOCKER_CLI_TOOLS

Our take

Full-surface Fly.io management from the PulseMCP monorepo: two dozen tools covering app and machine CRUD, start/stop/suspend/restart, log retrieval with region and machine filters, Docker image updates, and direct registry.fly.io push/pull — plus machine_exec for running arbitrary commands on live machines. Authentication is your FLY_IO_API_TOKEN and it shells out to the fly CLI, so a sensible ENABLED_TOOLGROUPS permission system (readonly/write/admin, per-feature) is included and worth using, since exec-on-production-VMs is the sharpest tool an agent can hold. It sits in the monorepo's experimental/ directory — explicitly not graduated to their productionized set — with the monorepo's shared traits (72 stars, MIT, two maintainers, actively pushed) and light adoption (~54 npm downloads/week). For teams already on Fly.io who want agents doing deploys and debugging; run it readonly until you trust the loop. The registry category 'media' is wrong — this is cloud infrastructure tooling.

reviewed by hand · 2026-07-05

Something wrong or dead here? Report it