Unfortunately, Sprites Now Speak MCP

Source: fly.io Date: 2026-03-20 URL: https://fly.io/blog/unfortunately-mcp/

Summary

Release announcement, with accompanying essay expressing aesthetic ambivalence, for Sprites’ MCP integration at sprites.dev/mcp. Agents can now create and manage Sprites (persistent cloud VMs) through MCP tool calls. The post is notable for its hedged tone: Fly considers CLI-driven discoverable APIs the “right” approach but ships MCP because that’s what the ecosystem expects. User-controlled caps and name-prefix guardrails ship alongside the integration.

Implications

MCP integration / Machines API as agent-runtime substrate. This is the most direct entry in the “Sprites speak MCP” thread — the phrase itself is the post’s title, with “unfortunately” reflecting genuine ambivalence about MCP’s design. The Fly team’s critique (CLI tools reveal capabilities progressively; MCP tool descriptions don’t) is technically coherent and worth tracking — it represents a dissenting view within the MCP adoption wave. Meanwhile, shipping it anyway demonstrates that ecosystem momentum overrides aesthetic preferences. The guardrails (creation caps, name prefixes) are the right safety primitives for multi-agent workloads and will likely become table stakes for any MCP-connected infrastructure provider.