fly-mcp

What is fly-mcp?

fly-mcp is an open-source MCP (Model Context Protocol) server for managing Fly.io infrastructure. It enables AI-driven DevOps workflows through natural language interactions, providing tools to list, inspect, restart, and scale Fly.io applications.

How to use fly-mcp?

Set environment variables FLY_MCP_FLY_API_TOKEN and FLY_MCP_FLY_ORGANIZATION, then build and run the server with make build and make run (or make dev for hot reload). For production, deploy on Fly.io using fly mcp launch with required secrets. The server exposes an HTTP endpoint on port 8080; tools are invoked via JSON-RPC requests to that endpoint.

Key features of fly-mcp

• Fly.io API integration via MCP tools
• Security features: rate limiting, CORS, audit logging
• Real-time application status and scaling
• Configuration via YAML, env vars, or CLI flags
• Structured logging with audit trails
• List and manage Fly.io apps

Use cases of fly-mcp

• List all Fly.io applications with status filtering
• Get detailed information about a specific application
• Restart an application with explicit confirmation
• Check scaling status and get recommendations
• Test connectivity with the ping tool

FAQ from fly-mcp

What are the prerequisites to run fly-mcp?

Go 1.21 or later, a Fly.io account, and a Fly.io API token are required.

How is authentication handled?

Authentication is done via the FLY_MCP_FLY_API_TOKEN environment variable; all tools require proper authorization.

Which transport does fly-mcp use?

The server communicates over HTTP on port 8080, using JSON-RPC 2.0 for MCP protocol messages.

Where does configuration data live?

Configuration can come from YAML files (config.local.yaml, config.production.yaml), environment variables (prefixed with FLY_MCP_), or command-line flags.

Are all Fly.io management tools available yet?

Phase 2 is complete, providing six core tools (ping, list apps, app info, status, restart, scale). Additional tools for logs, secrets, volumes, and deployments are planned for Phase 3.