Fly Io
Manage Fly.io apps, machines, logs, SSH, and Docker registry actions from your agent with grouped, scope-limited tools.
Overview
com.pulsemcp/fly-io is a MCP server for the Operate phase that lets agents manage Fly.io apps, machines, logs, SSH, and container images via grouped API tools.
What is this MCP server?
- Nine tool group namespaces: readonly, write, admin, apps, machines, logs, ssh, images, registry
- FLY_IO_API_TOKEN required; optional single-app lock via FLY_IO_APP_NAME
- ENABLED_TOOLGROUPS comma filter for least-privilege agent access
- Optional SKIP_HEALTH_CHECKS and DISABLE_DOCKER_CLI_TOOLS for constrained environments
- fly-io-mcp-server on npm with stdio npx transport
- Server version 0.1.6; npm package fly-io-mcp-server
- 9 named ENABLED_TOOLGROUPS categories in server metadata
- Stdio transport; optional DISABLE_DOCKER_CLI_TOOLS defaults false
Community signal: 70 GitHub stars.
What problem does it solve?
Debugging Fly deployments means constantly alt-tabbing to flyctl and the dashboard for logs, machine state, and registry tasks your agent could handle in one thread.
Who is it for?
Solo builders hosting on Fly.io who want agent-assisted ops—logs, machine status, SSH, and image tooling—with token-scoped tool groups.
Skip if: Teams on Vercel-only or raw Kubernetes without Fly, or anyone who should not expose write/admin Fly tools to an autonomous agent.
What do I get? / Deliverables
After adding FLY_IO_API_TOKEN and chosen ENABLED_TOOLGROUPS, your agent can run scoped Fly.io operations inline with your deploy workflow.
- Grouped Fly.io API tools for apps, machines, logs, ssh, images, and registry
- Optional single-app scoped configuration for production assistants
- Agent-accessible deploy and ops actions without manual flyctl for every step
Recommended MCP Servers
Journey fit
Fly.io control surfaces matter most once apps are deployed and you need logs, scaling, and image operations day to day. Infra is the primary shelf for machine and platform MCP tools that keep production Fly workloads healthy.
How it compares
Fly.io platform MCP integration, not a generic PaaS abstraction or Terraform skill.
Common Questions / FAQ
Who is com.pulsemcp/fly-io for?
Developers deploying on Fly.io with MCP-enabled coding agents who want safer, grouped access to apps, machines, logs, and registry tools.
When should I use com.pulsemcp/fly-io?
Use it when shipping or operating Fly apps—for launch verification, log investigation, machine changes, and image work—while limiting tools via ENABLED_TOOLGROUPS.
How do I add com.pulsemcp/fly-io to my agent?
Register npx -y fly-io-mcp-server with FLY_IO_API_TOKEN, optionally FLY_IO_APP_NAME and ENABLED_TOOLGROUPS, then restart your MCP client.