# Your Agent Speaks MCP. Give It a Computer.

DevFeed: [Your Agent Speaks MCP. Give It a Computer.](<https://devfeed.tech/articles/your-agent-speaks-mcp-give-it-a-computer-1717.md>)

Original publisher: [Read original article](<https://fly.io/blog/sprites-mcp/>)

Published: 2026-09-03T00:00:00Z

Content type: article

Language: en

Sources: [The Fly Blog](<https://devfeed.tech/sources/the-fly-blog.md>)

Topics: [MSP MCP](<https://devfeed.tech/topics/msp-mcp.md>), [AI Bots](<https://devfeed.tech/topics/ai-bots.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [api](<https://devfeed.tech/tags/api.md>), [auth](<https://devfeed.tech/tags/auth.md>), [cdn](<https://devfeed.tech/tags/cdn.md>), [claude](<https://devfeed.tech/tags/claude.md>), [claude-code](<https://devfeed.tech/tags/claude-code.md>), [cli](<https://devfeed.tech/tags/cli.md>), [close-to-users](<https://devfeed.tech/tags/close-to-users.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [codex](<https://devfeed.tech/tags/codex.md>), [cursor](<https://devfeed.tech/tags/cursor.md>), [deploy-app-servers](<https://devfeed.tech/tags/deploy-app-servers.md>), [docker](<https://devfeed.tech/tags/docker.md>), [elixir](<https://devfeed.tech/tags/elixir.md>), [filesystems](<https://devfeed.tech/tags/filesystems.md>), [fly](<https://devfeed.tech/tags/fly.md>), [fly-io](<https://devfeed.tech/tags/fly-io.md>), [gemini](<https://devfeed.tech/tags/gemini.md>), [heroku-alternative](<https://devfeed.tech/tags/heroku-alternative.md>), [heroku-competitor](<https://devfeed.tech/tags/heroku-competitor.md>), [hosting](<https://devfeed.tech/tags/hosting.md>), [i](<https://devfeed.tech/tags/i.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-server](<https://devfeed.tech/tags/mcp-server.md>), [networking](<https://devfeed.tech/tags/networking.md>), [postgresql-clusters](<https://devfeed.tech/tags/postgresql-clusters.md>), [servers](<https://devfeed.tech/tags/servers.md>), [skills](<https://devfeed.tech/tags/skills.md>)

## AI overview

The article presents Sprites as disposable cloud computers for coding agents and explains using their API through MCP. It argues that MCP transport and progressive capability disclosure can work together, including through plugins and skills.

## Source excerpt

Sprites are disposable cloud computers. They appear instantly, always include durable filesystems, and cost practically nothing when idle. They're the best and safest place on the Internet to run agents and we want you to create dozens of them. Sprites are a place to run agents; the first thing you should think to do with a new Sprite is to type claude (or gemini or codex). We've put a lot of effort into making sure coding agents feel safe and happy when they're on Sprites, because, to (probably) quote John von Neumann, "happy agents are productive agents." What's less obvious about Sprites is that they're great tools for agents. Want three different versions of a new feature? A test environment? An ensemble of cooperating services? It's super handy to be able to start your prompts, "On a new Sprite, do...". The Sprites API is simple, discoverable, and designed for this use case. The only real question is how your agent reaches it. For most of you the answer is MCP, and the setup is already written. You Don't Have To Pick There's an argument going around that MCP is the wrong way to extend an agent, and that command line tools and discoverable APIs are the Right Way. Half of that argument is correct, and it's the important half, so let's take it seriously. Dumping thirty tool descriptions into a context window is a bad way to teach anything. Not every Sprite command matters in every session, and cramming them all in signals to the model that they all matter to you. If you're not using network policies, gemini shouldn't burn a single token learning to configure them. Capabilities should reveal themselves progressively, the way they do when an agent works out a CLI one subcommand at a time. The wrong half is treating that as a case against MCP. Progressive disclosure is a question of what you say to the model. MCP is a question of how the bytes get there: transport, auth, structured results, a tool the model can call instead of a command whose flags it has to guess. Tho