Loading post…
Fly.ioAnnouncement
Your Agent Speaks MCP. Give It a Computer.
Summary
Sprites are presented as disposable cloud computers for running coding agents and as tools agents can create for testing, debugging, benchmarking, and multi-service work. The post describes MCP as the transport and authorization layer, while progressive disclosure comes from plugins and skills that reveal capabilities only when needed; CLI, REST, and machine-readable /.sprite/llm.txt remain available. The hosted MCP server returns file reads as MCP resources and attaches safety annotations, marking read-only and destructive operations and flagging exec and service_start as crossing the Sprite boundary. Agents connect through sprites.dev/mcp and authenticate to a specific Fly.io organization, with configurable scoping, a default five-Sprite cap, and an mcp- name prefix. The design emphasizes durable filesystems, real networks, and near-zero idle cost instead of stateless sandboxes, while the post argues these properties make disposable computers practical for agent workflows.
Context
Agents need disposable computers for tasks such as reproducing bugs, benchmarking code, testing dependency updates, running load generators, and coordinating multiple services. The post also argues that stateless sandboxes are insufficient because agents benefit from real filesystems and real networks.
Approach / What changed
Sprites expose a hosted MCP server at sprites.dev/mcp, with client plugins and skills for progressive capability disclosure. The same underlying API remains accessible through the sprite CLI and REST, while /.sprite/llm.txt provides machine-readable documentation inside each Sprite. Sessions can be scoped to a Fly.io organization and constrained by Sprite count and name prefix.
Takeaways
Plugins combine a hosted MCP server with skills, so agents receive a short contextual capability description and retrieve details progressively.
MCP file reads use resources; safety annotations distinguish read-only and destructive operations and flag exec and service_start as reaching beyond the Sprite boundary.
Sessions authenticate to one Fly.io organization and default to five Sprites with an mcp- name prefix; both the cap and prefix can be changed.
Source and freshness
- Source
- fly.io
- Published
- Added to Yomu
- Last updated
Summaries are generated from the original by a language model. Check the original before relying on it.
Keep reading
Related reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
The best engineering reads, once a week
One useful email. Unsubscribe anytime.