fly.io
Fly.io is a cloud platform for running applications on Firecracker-based virtual machines across global regions. It also offers Sprites, persistent Linux sandbox environments for AI agents and exploratory code execution.
fly.io exposes the Fly Machines REST API at `api.machines.dev`, the `flyctl` CLI, plus Sprites surfaces under the Fly ecosystem: a Sprites REST API at `api.sprites.dev/v1` and a hosted MCP server at `https://sprites.dev/mcp` authenticated via OAuth.
- Sprites MCP serverdetected
- Sprites REST APIdiscovered
- Fly Machines APIdiscovered
- flyctldiscovered
$ fly auth loginAcquired by the CLI — running fly auth login opens the auth flow and stores the credential.
Create a Sprites token from the Sprites developer workflow/docs, then send it as Authorization: Bearer <token>. The REST reference at Sprites API shows this header and its quick start uses the SPRITES_TOKEN environment variable. I could confirm consumption but not a dedicated token-minting page URL.
Point your MCP client at the server URL and approve access in the browser. The server accepts a Client ID Metadata Document (CIMD), so the client authenticates with its own hosted URL as the client_id — nothing to register.
conventions · 3/8 published
- integrations.json✗
/.well-known/integrations.json - llms.txt✓https://fly.io/llms.txt
- API catalog✓https://fly.io/.well-known/api-catalog
- OpenAPI document✗
/api/schema/, /openapi.json, /swagger.json, /api/openapi.json, or /v1/openapi.json - MCP server card✗
/.well-known/mcp/server-card.json - OAuth protected resource✗
/.well-known/oauth-protected-resource - Agent card✗
/.well-known/agent-card.json - Agent skills✓https://fly.io/.well-known/agent-skills/index.json
Publish these signals → /publishing