Claude Sprites connectorWhat Claude can do in your Sprites account.
The Claude Sprites connector exposes 18 tools. 8 read the state of your Sprites, 10 change something, and none is left undescribed. Below: what Claude starts, what it can wipe for good, and the restricted token that fences it all in.
Verified Trustpilot reviews · AI, automation & growth agency
What changes for your coding experiments
A Sprite is an isolated, persistent Linux environment that Fly.io hosts for you. With this connector, you ask Claude to spin up a machine, run a command in it or save its state, and it does so from the conversation. Fly.io presents Sprites as the simple answer to the question of where to run a piece of code.
Test in an isolated environment. create_sprite opens a fresh environment, then exec runs the command you ask for, such as checking which runtime version is installed. Fly.io gives this kind of request among its own examples.
Undo a bad move. checkpoint_create freezes the filesystem before a change; if an install goes wrong, checkpoint_restore rewinds the Sprite to that point.
Run a service and keep an eye on it. Claude creates, starts or stops a background service, then reads its recent logs through service_logs.
Worth knowing first: destroy_sprite deletes a Sprite and its data with no way back, and a restore wipes out everything done after the chosen point. By default, the token only allows Sprites named with the mcp- prefix, and only a limited number of them. Nothing runs by itself either: Claude fires no command on a schedule. That's an automation tool's job, a different trade; the Integrations hub covers that side.
The vocabulary in one minute
Five words you'll meet while connecting Sprites.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
- Tool
- One named action a connector opens to Claude. Claude picks the ones it needs on its own, and the directory sheet lists them by name.
- Authorization
- The service's own sign-in screen, where you hand Claude the access it will use. Granted once per person, and you can take it back later.
- Approval
- The confirmation Claude waits for before it goes through with something that changes your account, shown in the chat when it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service in the first place.
Connect Sprites to Claude in three steps
- 01
Find Sprites in Claude
In Claude's settings, open Customize, then Connectors, and look for Sprites in the list. On a Team or Enterprise workspace, an Owner or Primary Owner enables the connector first, and each member can then connect with their own account.
- 02
Start the connection
Click Connect on its row, sign in with your Fly.io account in the window the service opens itself, and pick the organisation to use. If the link breaks, use Disconnect and connect it again.
- 03
Read the authorization screen
Read the authorization screen before accepting: it belongs to Fly.io, not Claude, and it sets what the access covers, token restrictions included. Whatever you grant there can also be withdrawn from your Fly.io account.
The 18 tools, grouped by what they do
Sprites gives Claude 18 tools: 8 that read your account, 10 that change something in it.
Two groups: what Claude reads, and what it changes in your Fly.io organisation. Names stay exactly as Claude shows them.
- 8 read
- 10 write
What Claude reads (8)
8 toolsEight tools that look at your Sprites, their checkpoints, services and network rules.
checkpoint_get
Shows the details of one specific checkpoint on a Sprite, so you know which state it captures before deciding anything. Fly.io names inspecting as one of the checkpoint gestures, separate from listing them.
checkpoint_list
Lists the checkpoints that exist on a Sprite, with their IDs, so Claude can then inspect or restore one of them later on.
exec_list
Shows the exec sessions open in a Sprite without interrupting any of them. Fly.io groups it under exec, next to running a command and killing a session.
list_sprites
Lists the Sprites visible to the connected organisation, within the token's policy. It's the right first step whenever a name doesn't respond.
policy_network_get
Reads a Sprite's outbound network rules, so you know where it's allowed to connect and what is blocked.
service_get
Inspects one background service inside a Sprite to see where it stands, without starting or stopping it. Fly.io names inspecting a service as its own gesture, apart from listing services.
service_list
Lists the background services defined in a Sprite, the starting point before inspecting, starting or stopping one. Fly.io generates these Sprite tools from the environment’s public API, so the set can evolve with new versions.
service_logs
Pulls the recent logs of a background service, so you can see what the service reported. Fly.io describes this gesture as reading a service’s recent logs, nothing older.
What Claude changes (10)
10 toolsTen tools that act on your Sprites. No source gives a per-tool confirmation, so the general rule below applies.
checkpoint_create
Approval: see the ruleFreezes a Sprite's current filesystem into a checkpoint you can return to later.
checkpoint_restore
Approval: see the ruleRewinds a Sprite to the filesystem state of an earlier checkpoint. Everything done since that point is gone.
create_sprite
Approval: see the ruleOpens a new Sprite in the organisation chosen at connection time, ready to take commands and services.
destroy_sprite
Approval: see the rulePermanently deletes a Sprite and all its data. Fly.io is blunt about it: there is no undo.
exec
Approval: see the ruleRuns a command inside a Sprite. Per Fly.io, a command can modify files, install packages, start services or use whatever network access the Sprite's policy allows.
exec_kill
Approval: see the ruleEnds an exec session running inside a Sprite.
policy_network_update
Approval: see the ruleUpdates a Sprite's outbound network rules, to allow or block access to the outside.
service_create
Approval: see the ruleDeclares a new background service inside a Sprite, which can then be started, stopped or inspected.
service_start
Approval: see the ruleLaunches a background service already declared in a Sprite so it begins running.
service_stop
Approval: see the ruleStops a background service running in a Sprite without removing its definition.
What Claude asks you before acting
By default, Claude stops and asks for your go-ahead before every action it takes on an account for you. The request shows up in the conversation, right when it matters.
Fly.io annotates its tools as read-only or destructive, and notes that the client may ask for extra confirmation before a destructive tool, depending on its settings. On a Team or Enterprise workspace, owners decide whether a member may let some actions through without being asked again, and they can cap the connector for the whole organisation. Finally, Claude acts with the token you approved and nothing more.
Which plans it's available on
Of the 819 sheets in the official directory, none shows availability by plan. For Sprites as for the rest, the connector-by-connector answer isn't published anywhere.
The general rule, though, is published: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner turns the connector on for the organisation before each member can connect. For the current state, check the connector's sheet in the official directory.
Where this connector stops
A connector isn't an automation: Claude calls these tools while it answers you, and nothing starts on its own inside a Sprite. Only the publisher, Fly.io, documents this connector.
The tool list is an observed floor, not a promise, and Fly.io warns that the Sprite-level tools can change as new versions of the environment ship. The partner badge isn't a security audit, and Anthropic says so on every sheet: it doesn't choose a publisher's tools or vouch for how they behave. Connect only what comes from a publisher you know, here Fly.io. Other connectors are listed on the Claude integrations page.
Need help connecting Sprites to Claude?
A person reads every message.