fly-mcp

- 🔒 Security: All tools require proper authentication and permissions
- 📝 Audit Logging: All operations are logged for compliance and debugging
- ⚡ Real-time: Status and machine information is fetched in real-time
- 🛡️ Safety: Destructive operations require explicit confirmation
- 📊 Rich Output: Human-readable responses with actionable recommendations

- ✅ Project structure and build system
- ✅ Configuration management (local/production environments)
- ✅ HTTP server with middleware (CORS, rate limiting, logging)
- ✅ MCP protocol handler with full request/response handling
- ✅ Structured logging with audit trails and security events
- ✅ Fly.io API integration (hybrid approach: fly-go + Machines API)
- ✅ Authentication & authorization with permissions and audit logging
- ✅ Core MCP tools:
- ping - Test tool for connectivity
- fly_list_apps - List all applications with filtering
- fly_app_info - Get detailed application information
- fly_status - Real-time application and machine status
- fly_restart - Restart applications with confirmation
- fly_scale - Scaling status and recommendations
- ✅ Health checks and metrics endpoints
- ✅ Comprehensive error handling and validation
- ✅ Security features (rate limiting, CORS, audit logging)

- Go 1.21 or later
- Fly.io account and API token
- Git

1. Clone the repository

   git clone https://github.com/brannn/fly-mcp.git

   cd fly-mcp

   

2. Set up environment variables

   export FLY_MCP_FLY_API_TOKEN="your_fly_api_token_here"

   export FLY_MCP_FLY_ORGANIZATION="your_fly_org_here"

   

3. Build and run

   make build

   make run

   

Or for development with hot reload:

   make dev

   

Deploy using Fly.io's MCP infrastructure:

fly mcp launch \
  "github.com/brannn/fly-mcp" \
  --claude --cursor --zed \
  --server fly-infrastructure \
  --secret FLY_API_TOKEN=fo1_your_token \
  --secret FLY_ORG=your-org-name

| Variable | Description | Required |
|----------|-------------|----------|
| FLY_MCP_FLY_API_TOKEN | Fly.io API token | Yes |
| FLY_MCP_FLY_ORGANIZATION | Fly.io organization name | Yes |
| FLY_MCP_ENVIRONMENT | Environment (local/production) | No |
| FLY_MCP_LOGGING_LEVEL | Log level (debug/info/warn/error) | No |

```bash

| Tool | Description | Example Usage |
|------|-------------|---------------|
| ping | Test connectivity and server response | {"name": "ping", "arguments": {"message": "Hello!"}} |

| Tool | Description | Example Usage |
|------|-------------|---------------|
| fly_list_apps | List all applications with filtering | {"name": "fly_list_apps", "arguments": {"status_filter": "running"}} |
| fly_app_info | Get detailed application information | {"name": "fly_app_info", "arguments": {"app_name": "my-app"}} |
| fly_status | Real-time application and machine status | {"name": "fly_status", "arguments": {"app_name": "my-app"}} |
| fly_restart | Restart applications with confirmation | {"name": "fly_restart", "arguments": {"app_name": "my-app", "confirm": true}} |
| fly_scale | Scaling status and recommendations | {"name": "fly_scale", "arguments": {"app_name": "my-app", "action": "status"}} |

- 🔒 Security: All tools require proper authentication and permissions
- 📝 Audit Logging: All operations are logged for compliance and debugging
- ⚡ Real-time: Status and machine information is fetched in real-time
- 🛡️ Safety: Destructive operations require explicit confirmation
- 📊 Rich Output: Human-readable responses with actionable recommendations