Works with your agent. Yes, that one too.

Official Sprites plugins for every serious coding agent — plus SDKs, API connectors, and native integrations. Your agent builds, tests, and runs services on a real Linux box instead of your laptop.

Point any agent at

https://sprites.dev/mcp

OAuth in the browser. Nothing to install, nothing to run locally.

Which agent are you using?

Pick one and follow the steps below.

/

Set up Sprites for Claude Code

superfly/sprites-claude-plugin

1

Add the marketplace and install the plugin

/plugin marketplace add superfly/sprites-claude-plugin
2

Install it

/plugin install sprites@sprites
3

Reload so Claude picks up the new tools

/reload-plugins
4

Authorize the connector

/mcp

Pick the plugin-provided sprites server and complete browser OAuth for the Fly.io org you want. Restricted access with a name prefix such as mcp- is the safer default.
✓

Check the integration

/sprites:status

An empty Sprite list means you're authenticated and working. /sprites:smoke runs the full list → create → exec → cleanup pass.

Prefer the bare MCP server, without the plugin's skills and hooks?

claude mcp add --transport http sprites https://sprites.dev/mcp

Set up Sprites for Cursor

superfly/sprites-cursor-plugin

1

Install the Sprites plugin from the Cursor Marketplace

Cursor prompts you to authorize with Sprites over OAuth on first use.
2
Or wire up the MCP server by hand
~/.cursor/mcp.json
```
{
  "mcpServers": {
    "sprites": {
      "url": "https://sprites.dev/mcp"
    }
  }
}
```
Drop this in ~/.cursor/mcp.json for every project, or .cursor/mcp.json for just this one.
✓

Ask the agent to prove it's connected

List my sprites.

Set up Sprites for OpenCode

superfly/sprites-opencode-plugin

1
Add the plugin to your OpenCode config
opencode.json
```
{
  "$schema": "https://opencode.ai/config.json",
  "plugin": ["@flydotio/sprites-opencode-plugin"]
}
```
OpenCode 1.18.23 or newer. Plugins install automatically with Bun at startup, so restart OpenCode after saving. Until the package lands on npm, clone the repository and use an absolute file:///path/to/sprites-opencode-plugin entry instead.
2

Complete browser OAuth

/sprites-status

The first Sprites request starts OpenCode's browser OAuth flow. Pick the Fly.io org you want. If no browser opens, run opencode mcp auth sprites and retry.
✓

Ask OpenCode to prove it's connected

List my sprites.

An empty list is a successful, authenticated response. /sprites-smoke walks the full list → create → exec pass, and opencode mcp debug sprites diagnoses a bad connection.

Set up Sprites for Herdr

superfly/herdr-sprites-plugin

1

Log in with the Sprite CLI

sprite login

Linux or macOS, Node.js 22 or newer, Git, and Herdr 0.9.0 or newer. The plugin drives the sprite CLI you just authenticated, so there is no token to paste.
2

Install the plugin from GitHub

herdr plugin install superfly/herdr-sprites-plugin
3

Find the plugin's config directory

herdr plugin config-dir sprites
4
Choose an organization and an agent
config.json
```
{
  "org": "your-sprites-organization",
  "agent": "claude"
}
```
Save it in the directory printed above. agent is claude, codex, or opencode. Add a command array to run a different agent or pass arguments; namePrefix defaults to herdr-.
5

Start an agent from a Git worktree

herdr plugin action invoke start-agent --plugin sprites

Opens a split pane, creates a Sprite, uploads the worktree with its uncommitted edits, checkpoints it, and hands the terminal to the agent. start-claude, start-codex, and start-opencode pick a harness for one launch. Claude Code and Codex reuse your local login when one is available.

Optionally, bind it to a key

config.toml

[[keys.command]]
key = "prefix+shift+s"
type = "plugin_action"
command = "sprites.start-agent"
description = "start agent in a Sprite"

Herdr's own config file, so the action runs from a prefix key instead of the CLI.

✓

Show the pane's Sprite and sessions

herdr plugin action invoke info --plugin sprites

Info reports the Sprite, its checkpoint, and the remote session list. reconnect reattaches a detached agent, pull brings its edits back into your worktree, and stop, checkpoint, restore, and destroy round out the set.

Git history, .env files, and credentials never leave your machine; the Sprite gets a fresh baseline repository. Pull rejects overlapping local edits before touching anything, and reconnect keeps remote files and authentication in place.

Set up Sprites for Hermes Agent

NousResearch/hermes-plugin-sprites

1

Use a current Hermes installation with pluggable terminal backends

This plugin needs the terminal-backend extension introduced in Hermes PR #94400. The commands below assume the standard macOS/Linux install and default Hermes home.
2

Clone the plugin

git clone https://github.com/NousResearch/hermes-plugin-sprites.git ~/.hermes/plugins/sprites
3

Install the supported SDK in Hermes's Python environment

uv pip install --python ~/.hermes/hermes-agent/venv/bin/python 'sprites-py>=0.5.0,<0.6'

For a custom installation, use its Python environment instead. Do not install into an unrelated system Python.
4
Add a Sprites API token to Hermes's local secrets file
~/.hermes/.env
```
SPRITES_TOKEN=your-sprites-api-token
```
Create a token at sprites.dev/account for the intended organization. Edit the file locally; do not paste the token into an agent prompt or commit it.
5

Enable the plugin

hermes plugins enable sprites
6

Select the terminal backend

hermes config set terminal.backend sprites
7

Check configuration, then start a new Hermes session

hermes doctor

Doctor checks that the token and SDK are present, not that the API token works. Restart any running Hermes session or gateway before trying the backend.
✓

Ask Hermes to execute a command in the Sprite

Use the terminal tool to run uname -a and pwd.

Check the actual tool result and the Sprite in your Sprites dashboard. First use creates or resumes a Sprite and can incur usage charges.

Hermes stays on its host; shell commands run remotely. Sprites persist by default, and remote edits are not automatically copied back. Hermes can upload configured credential files, skills, and caches to the Sprite; review those before use.

Set up Sprites for Any MCP client

superfly/sprites-mcp

1
Add a remote server entry
mcp.json
```
{
  "mcpServers": {
    "sprites": {
      "url": "https://sprites.dev/mcp"
    }
  }
}
```
Streamable HTTP over JSON-RPC 2.0, authenticated with OAuth 2.1 (sprites:read / sprites:write). Nothing runs locally.

If your client only speaks stdio, bridge it

mcp.json

{
  "mcpServers": {
    "sprites": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://sprites.dev/mcp"]
    }
  }
}

mcp-remote handles the OAuth flow on the client's behalf.

3

Authorize in the browser on first use
✓

Ask your agent to prove it's connected

List my sprites.

Which language are you building in?

The same primitives the plugins are built on — create, exec, services, checkpoints, network policy.

Build with Python

superfly/sprites-py

1

Install from PyPI

pip install sprites-py
2

Point it at your Sprites account

export SPRITES_TOKEN='...'

Create a token from the Sprites dashboard.

Build with Elixir

superfly/sprites-ex

1
Add the dependency
mix.exs
```
{:sprites, "~> 0.2"}
```
2

Fetch it

mix deps.get
3

Point it at your Sprites account

export SPRITES_TOKEN='...'

Create a token from the Sprites dashboard.

Give your Sprite access to external APIs

Connect through the Sprites API gateway while keeping provider credentials outside your Sprite. Choose a service and grant access in the dashboard.

Available providers can vary by organization during rollout. Your dashboard shows which connectors you can enable.

Use Sprites with Meta (Muse Spark)

fly.io/dashboard

Call Muse Spark from a Sprite while keeping your Meta API key outside the environment.

1

Add Meta in your organization's Sprites Connectors

In the Fly.io dashboard, select your organization, open Sprites → Connectors → Add connector, and choose Meta. Availability is enabled per organization; Meta may not appear yet.
2

Bring your Meta API key

Enter your Meta developer team's API key in the connector form. The gateway stores it and adds it to upstream requests; do not copy it into your Sprite.
3

Grant your Sprite access

Turn off Allow all sprites before restricting access by name prefix or labels, then save the policy. If you set both prefix and labels, a Sprite must match both.
4

Try the API Usage example from your Sprite

Use the example on the connector's detail page. Check /v1/models through the connector for models available to your team.

Supports streaming and tool calls through OpenAI-compatible chat completions and responses, and Anthropic-compatible messages. The gateway also allows model discovery; other Meta API paths are blocked.

Open the dashboard Read connector docs

Use Sprites with your platform

Use Sprites as an execution environment for another platform's agents and tools. Pick your product and follow its setup guide.

Use Sprites with TanStack AI

tanstack.com

Sprites as a sandbox provider for TanStack AI agents.

Read the setup guide

Straight to the source

Integration	Ships	Auth	Repository
Claude Code	MCP Skills Hooks	Browser OAuth	superfly/sprites-claude-plugin
Codex	MCP Skills	Browser OAuth	superfly/sprites-codex-plugin
Cursor	MCP Skills	Browser OAuth	superfly/sprites-cursor-plugin
Antigravity	MCP Skills Commands Hooks	Browser OAuth	superfly/sprites-antigravity-plugin
Grok Build	MCP Skills	Browser OAuth	superfly/sprites-grok-plugin
Cortex Code	MCP Skills Commands Hooks	Browser OAuth	superfly/sprites-cortex-plugin
DeepSeek Harness	MCP Skills	Browser OAuth	superfly/sprites-deepseek-plugin
OpenCode	MCP Skills Commands Hooks	Browser OAuth	superfly/sprites-opencode-plugin
Pi	SDK Skills	API token	superfly/pi-sprites
VS Code	Filesystem	API token	superfly/sprites-vscode-ext
Herdr	Sandbox Commands Filesystem	Sprite CLI	superfly/herdr-sprites-plugin
Hermes Agent	Sandbox	API token	NousResearch/hermes-plugin-sprites
Any MCP client	MCP	Browser OAuth	superfly/sprites-mcp
Agent Plugins v1	MCP Skills	Browser OAuth	superfly/sprites-agent-plugin

What your agent can do with it

Run the risky stuff somewhere else

Builds, migrations, dependency upgrades, and whole test suites run on the Sprite. Your laptop stays clean and stays yours.

Checkpoint before it breaks things

A checkpoint snapshots the whole filesystem in about a second. If the agent wrecks the environment, restore and carry on.

Keep services running between sessions

Dev servers, workers, and databases live on as Sprite services, with a URL you can open. Closing your editor doesn't kill them.

Confirm before anything destructive

Confirmation behavior varies by plugin. Check its safety controls before destructive work; terminal backends such as Hermes do not provide Sprites-specific confirmation hooks.

$30 in trial credits. Create, like, 500 Sprites free.

Play with Sprites

Which agent are you using?

Set up Sprites for Claude Code

Set up Sprites for Codex

Set up Sprites for Cursor

Set up Sprites for Antigravity

Set up Sprites for Grok Build

Set up Sprites for Cortex Code

Set up Sprites for DeepSeek Harness

Set up Sprites for OpenCode

π Set up Sprites for Pi

Set up Sprites for VS Code

Set up Sprites for Herdr

Set up Sprites for Hermes Agent

Set up Sprites for Any MCP client

Set up Sprites for Agent Plugins v1

Which language are you building in?

Build with Python

Build with JavaScript

Build with Go

Build with Elixir

Build with Google ADK

Build with OpenAI Agents SDK

Build with OpenRouter Agent SDK

Give your Sprite access to external APIs

Use Sprites with Meta (Muse Spark)

Use Sprites with OpenAI

Use Sprites with TypeSafeAI

Use Sprites with Anthropic

Use Sprites with OpenRouter

Use Sprites with Ollama Cloud

Use Sprites with GitHub

Use Sprites with Slack (User)

Use Sprites with Slack (Bot)

Use Sprites with Discourse

Use Sprites with S3-compatible Object Store

Use Sprites with Fly.io Machines

Use Sprites with Custom API

Use Sprites with Steel Browser Tools

Use Sprites with Linkup

Use Sprites with Firecrawl

Use Sprites with Deepgram

Use Sprites with Fireworks

Use Sprites with Parasail

Use Sprites with Depot build insights

Use Sprites with Upstash Redis

Use Sprites with Tigris

Use Sprites with AgentMail

Use Sprites with Blotato

Use Sprites with Keenable

Use Sprites with LemonSlice

Use Sprites with Mnemom

Use Sprites with Era

Use Sprites with Composio Tools

Use Sprites with Supabase Database

Use Sprites with Usable

Use Sprites with Exa

Use Sprites with your platform

Use Sprites with TanStack AI

Use Sprites with Claude Managed Agents

Use Sprites with Anthropic Connectors Directory

QM Use Sprites with QM

Use Sprites with Cursor Cloud Agents