The Sprites ecosystem — set up your coding agent · Fly
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.
/
Claude Code Anthropic
Plugin marketplace + hosted MCP, browser OAuth, safety hooks.
Codex OpenAI
Marketplace plugin wrapping the hosted MCP server.
Cursor Anysphere
Marketplace plugin, or a two-line MCP entry you paste yourself.
Antigravity Google
One-line install into the agy CLI, with workflow slash commands.
Grok Build xAI
Install and enable from the CLI, then finish OAuth in the browser.
Cortex Code Snowflake
Run Cortex Code builds, tests, and previews in persistent Linux environments, with browser OAuth.
DeepSeek Harness DeepSeek
Adds a layer to the dsh profile you already run.
OpenCode Anomaly
One opencode.json entry; Bun installs it at the next start.
π Pi Pi
First-class Sprites extensions, installed from Git.
VS Code Microsoft
Mount a Sprite's filesystem straight into your workspace.
Herdr Herdr
Each agent pane gets its own Sprite, with the worktree uploaded and a checkpoint to roll back to.
Hermes Agent Nous Research
Run Hermes Agent's shell commands in persistent Sprites with API-token authentication.
Any MCP client Standard
No plugin for your agent yet? Point it at the hosted server.
Agent Plugins v1 Portable
One portable package for clients that speak the v1 format.
No integration matches that — but any MCP client can use the generic path above.
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 Codex
- 1
Install the Sprites plugin from the Codex plugin marketplace
Codex distributes this one through its own marketplace UI, so there's no install one-liner to copy.
- 2
Or add this repository as a marketplace from a local checkout
$
codex plugin marketplace add .
Then restart Codex, open the plugin directory, choose the Sprites marketplace, and install Sprites.
- 3
Authenticate when Codex prompts you
The plugin talks to the hosted MCP server at https://sprites.dev/mcp.
- ✓
Ask Codex to prove it's connected
›
List my sprites.
An empty list is a successful, authenticated response.
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 Antigravity
superfly/sprites-antigravity-plugin
- 1
Install straight from the repository
$
agy plugin install https://github.com/superfly/sprites-antigravity-plugin
- 2
Authenticate the sprites server
›
/mcp
Use restricted access unless your workflow genuinely needs broader organization control.
- ✓
List what you've got
›
/sprites:list
The plugin also ships /sprites:new, /sprites:run, /sprites:checkpoint, /sprites:service, and /sprites:cleanup.
Set up Sprites for Grok Build
- 1
Install the plugin
$
grok plugin install superfly/sprites-grok-plugin --trust
- 2
Enable it
$
grok plugin enable sprites
- 3
Reload plugins, or restart Grok
›
/plugins
Then press r to reload.
- 4
Complete browser OAuth
The consent screen defaults to the restricted mcp- name prefix. Full access allows bare names but grants unrestricted access to every sprite in the org.
- ✓
Run the status check
›
/sprites-status
Empty list means you're authenticated. /sprites-smoke does the full list → create → exec → confirm-before-destroy pass, and grok mcp doctor sprites diagnoses a bad install.
Set up Sprites for Cortex Code
superfly/sprites-cortex-plugin
- 1
Install from GitHub
$
cortex plugin install superfly/sprites-cortex-plugin
- 2
Enable the plugin
$
cortex plugin enable sprites
- 3
Reload inside your session, or restart Cortex Code
›
/plugin reload
- 4
Authorize Sprites when requested
›
/mcp
Complete browser OAuth and select the intended Fly.io organization. No Sprites CLI or pasted API token is required.
- ✓
Check the connection
›
/sprites-status
An empty Sprite list still means authentication succeeded.
The plugin includes skills, commands, safety hooks, and a runner for long builds and tests. It does not copy Snowflake credentials or sessions into Sprites.
Set up Sprites for DeepSeek Harness
superfly/sprites-deepseek-plugin
- 1
Add the plugin to your profile
$
npx @deepseek-ai/dsh plugin --profile web add github:superfly/sprites-deepseek-plugin
Swap web for whichever profile you actually use.
- 2
Start that profile
$
npx @deepseek-ai/dsh --profile web
- 3
Complete browser OAuth and pick your Fly.io organization
Restart Harness once if the first tool sync timed out while you were authorizing.
- ✓
Confirm the layer loaded
$
npx @deepseek-ai/dsh --profile web --dump-config
Output should include the dsh-sprites-plugin layer, sprites-mcp, and sprites-skill-filesystem.
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 Pi
- 1
Install from GitHub
$
pi install git:github.com/superfly/pi-sprites
Not on npm yet. Node.js 24 or later is required by the Sprites SDK.
- 2
Export a Sprites token into Pi's environment
$
export SPRITES_TOKEN='...'
This integration authenticates with a token, not browser OAuth.
- ✓
Ask Pi to list your environments
›
List my sprites.
Set up Sprites for VS Code
- 1
Install the Sprites extension
- 2
Set your API token
›
Sprites: Set API Token
Run it from the Command Palette and paste your Sprites.dev API token.
- 3
Open a Sprite
›
Sprites: Open Sprite
Its filesystem appears in your workspace, editable in place.
- ✓
Open a shell on the box
›
Sprites: Open Terminal
Sprites: Create Sprite, Sprites: Delete Sprite, and a right-click Download to Local round out the command set.
Set up Sprites for Herdr
- 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.
- 6
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
- 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.
- 2
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.
Set up Sprites for Agent Plugins v1
- 1
Install the package with any Agent Plugins v1 client
The client discovers plugin.json, the children of skills/, and mcp.json at fixed locations. Agent Plugins standardizes package contents, not the install UI, so follow your client's own local, Git, workspace, or marketplace flow.
- 2
Complete browser OAuth on first MCP use
Restricted connector tokens may enforce a sprite-name prefix, creation cap, label, or expiry.
- ✓
Ask your agent to prove it's connected
›
List my sprites.
Claude Code, Grok, and Antigravity are not on the current compatible-client list. Use their dedicated packages above, which also carry hooks the portable format has no equivalent for.
Which language are you building in?
The same primitives the plugins are built on — create, exec, services, checkpoints, network policy.
Python Fly.io
The official Python SDK.
JavaScript Fly.io
The official TypeScript/JavaScript SDK.
Go Fly.io
The official Go SDK.
Elixir Fly.io
The official Elixir SDK.
Google ADK Google
Sandboxes as ADK agent tools, with checkpoint/restore.
OpenAI Agents SDK OpenAI
A Sprite as the sandbox an agent run executes its tools inside.
OpenRouter Agent SDK OpenRouter
Experimental workspace adapter. Not published to npm yet.
Build with Python
- 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 JavaScript
- 1
Install from npm
$
npm install @fly/sprites
- 2
Point it at your Sprites account
$
export SPRITES_TOKEN='...'
Create a token from the Sprites dashboard.
Build with Go
- 1
Add the module
$
go get github.com/superfly/sprites-go
- 2
Point it at your Sprites account
$
export SPRITES_TOKEN='...'
Create a token from the Sprites dashboard.
Build with Elixir
- 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.
Build with Google ADK
- 1
Install from PyPI
$
pip install sprites-adk
- 2
Point it at your Sprites account
$
export SPRITES_TOKEN='...'
Create a token from the Sprites dashboard.
Build with OpenAI Agents SDK
- 1
Install from PyPI
$
pip install sprites-openai-agents
- 2
Point it at your Sprites account
$
export SPRITES_API_TOKEN='...'
This adapter reads SPRITES_API_TOKEN rather than SPRITES_TOKEN. The Agents SDK still wants OPENAI_API_KEY of its own.
- 3
Know what you're pinning
The Agents SDK's sandbox APIs are beta, so each release of the adapter supports a deliberately narrow openai-agents version range. The source lives in sprites-py under integrations/openai-agents.
Build with OpenRouter Agent SDK
superfly/sprites-openrouter-sdk
- 1
Build from the repository
Not on npm yet, and the API may change before the first stable release.
- 2
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.
Meta (Muse Spark) Meta
Connector · BYOK
Call Muse Spark from a Sprite while keeping your Meta API key outside the environment.
OpenAI OpenAI
API key · BYOK
Call OpenAI's Responses, Chat Completions and Embeddings APIs from a Sprite without an OpenAI key inside it.
TypeSafeAI TypeSafeAI
API key · BYOK
Ask Jev typed questions about your data from a Sprite while keeping your TypeSafeAI key outside it.
Anthropic Anthropic
API key · BYOK
Call Claude models from a Sprite without storing your Anthropic API key inside it.
OpenRouter OpenRouter
API key · BYOK or managed
Access models through OpenRouter with your own key or a Sprites-managed connection.
Ollama Cloud Ollama
API key · BYOK
Use Ollama's cloud-hosted models from a Sprite through the gateway.
GitHub GitHub
OAuth
Give Sprites access to GitHub repositories, issues, and pull requests.
Slack (User) Slack
OAuth · user
Let a Sprite read and post in Slack on your behalf.
Slack (Bot) Slack
OAuth · bot
Let a Sprite work in Slack as a bot rather than as your user.
Discourse Discourse
User API key
Read or post on a Discourse forum from a Sprite with your forum permissions.
S3-compatible Object Store S3-compatible
Access key + secret
Access an S3-compatible bucket without keeping its storage credentials in a Sprite.
Fly.io Machines Fly.io
Fly.io token · preset
Call the Fly Machines API from a Sprite using an organization-scoped token.
Custom API Custom
Token + endpoint
Connect a token-authenticated HTTP API through the Sprites gateway.
Steel Browser Tools Steel
API key · BYOK
Stateless scraping, screenshots, and PDFs without storing your key on a Sprite.
Linkup Linkup
API key · BYOK
Search the web and fetch pages without putting your key on a Sprite.
Firecrawl Firecrawl
API key · BYOK
Scrape, search, and map websites without putting your key on a Sprite.
Deepgram Deepgram
API key · BYOK
Prerecorded speech recognition and HTTP text-to-speech with your own Deepgram key.
Fireworks Fireworks
API key · BYOK
OpenAI-compatible inference without storing your Fireworks key on a Sprite.
Parasail Parasail
API key · BYOK
OpenAI-compatible inference without storing your Parasail key on a Sprite.
Depot build insights Depot
API token · BYOK · read-only
Read container-build status and project metadata without storing a Depot token on a Sprite.
Upstash Redis Upstash
REST URL + token · BYOK
Read and write Redis data over HTTP without placing your database token on a Sprite.
Tigris Tigris
Access-key ID + secret · BYOK
Create private Tigris buckets without placing an admin key on your Sprite.
AgentMail AgentMail
API key · BYOK
Send and receive email from a Sprite without exposing your AgentMail key.
Resend Resend
API key · BYOK
Send email from a Sprite through Resend without putting your API key on it.
Neon Neon
API key · BYOK
Create and branch Neon Postgres databases from a Sprite without putting your API key on it.
ElevenLabs ElevenLabs
API key · BYOK
Build and run ElevenLabs voice agents from a Sprite without putting your API key on it.
SenseLab SenseLab
API key · BYOK
Share agent memory, briefings and outcomes across disposable Sprites.
Blotato Blotato
API key · BYOK
Publish to existing social accounts through Blotato without exposing its API key.
Keenable Keenable
API key · BYOK
Search with Keenable without placing its key on a Sprite.
LemonSlice LemonSlice
API key · BYOK
Read the history and status of existing LemonSlice sessions.
Mnemom Mnemom
API key · BYOK
Read Mnemom trust and agent information without storing the API key on a Sprite.
Era Era
API key · BYOK
Read linked banking data through Era without exposing a banking API key.
Composio Tools Composio Tools
API key · BYOK
Discover and execute tools against existing Composio connected accounts.
Supabase Database Supabase Database
Project URL + secret key · BYOK
Access a hosted Supabase project's REST database API without exposing its secret key.
Usable Usable
API key · BYOK
Use your Usable workspace knowledge through its authenticated MCP service.
Exa Exa
API key · BYOK
Search the web and retrieve page contents without storing your Exa key on a Sprite.
Use Sprites with Meta (Muse Spark)
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 OpenAI
Call OpenAI's Responses, Chat Completions and Embeddings APIs from a Sprite without an OpenAI key inside it.
- 1
Open your organization's Sprites Connectors
In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector.
- 2
Enter your OpenAI API key
Choose OpenAI in Add connector and enter a project API key from platform.openai.com. The gateway stores it and adds it to upstream requests; do not copy it into your Sprite.
- 3
Grant your Sprite access
Open access settings and turn off Allow all sprites before restricting access by name prefix or labels. If you set both, a Sprite must match both. Save the policy. A connector with no access policy denies all Sprites.
- 4
Test from your Sprite
Run the API Usage example from the connector's detail page inside an authorized Sprite. The gateway attaches the stored credential; do not copy it into the Sprite.
The OpenAI SDKs work unchanged with OPENAI_BASE_URL set to the connector URL. The Codex CLI needs a model_provider entry in its config instead. Files, fine-tuning and organization paths are blocked.
Open the dashboard Read connector docs
Use Sprites with TypeSafeAI
Ask Jev typed questions about your data from a Sprite while keeping your TypeSafeAI key outside it.
- 1
Open your organization's Sprites Connectors
In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector.
- 2
Enter your TypeSafeAI API key
Choose TypeSafeAI in Add connector and enter an API key from console.typesafe.ai. The gateway stores it and adds it to upstream requests; do not copy it into your Sprite.
- 3
Grant your Sprite access
- 4
Test from your Sprite
Jev is a decision model, not a chat model: it answers yes/no, choice and score questions with probabilities and confidence. The Python and JavaScript SDKs and the TypeSafeAI agent skill work unchanged with TYPESAFE_BASE_URL set to the connector URL. Only /v1/systemone and /v1/models are forwarded.
Open the dashboard Read connector docs
Use Sprites with Anthropic
Call Claude models from a Sprite without storing your Anthropic API key inside it.
- 1
Open your organization's Sprites Connectors
In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector.
- 2
Enter your Anthropic API key
Choose Anthropic in Add connector and enter your API key in the dashboard.
- 3
Grant your Sprite access
- 4
Test from your Sprite
This is access to the Anthropic API through the gateway, not the Sprites listing in the Anthropic Connectors Directory.
Open the dashboard Read connector docs
Use Sprites with OpenRouter
Access models through OpenRouter with your own key or a Sprites-managed connection.
- 1
Open your organization's Sprites Connectors
In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector.
- 2
Choose your own key or managed access
Use your own key instead accepts an OpenRouter API key. Where managed access is enabled, choose Enable OpenRouter and buy prepaid credits before making requests.
- 3
Grant your Sprite access
- 4
Test from your Sprite
Managed access availability varies by organization. This connector is separate from the OpenRouter Agent SDK in the SDKs tab.
Open the dashboard Read connector docs
Use Sprites with Ollama Cloud
Use Ollama's cloud-hosted models from a Sprite through the gateway.
- 1
Open your organization's Sprites Connectors
In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector.
- 2
Add your Ollama API key
Choose Ollama in Add connector and enter your Ollama Cloud API key. Availability varies by organization; Ollama may not appear yet.
- 3
Grant your Sprite access
- 4
Test from your Sprite
Connects to Ollama Cloud, not an Ollama server running on your laptop.
Open the dashboard Read connector docs
Use Sprites with GitHub
Give Sprites access to GitHub repositories, issues, and pull requests.
- 1
Open your organization's Sprites Connectors
In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector.
- 2
Authorize GitHub
Choose GitHub, continue to GitHub, and approve the requested access. Review the account and permissions before returning to the dashboard.
- 3
Grant your Sprite access
- 4
Test from your Sprite
Access follows the authorizing user's permissions and granted OAuth scopes. Re-authorize from the connector's Scopes editor if more access is needed.
Open the dashboard Read connector docs
Use Sprites with Slack (User)
Let a Sprite read and post in Slack on your behalf.
- 1
Open your organization's Sprites Connectors
In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector.
- 2
Authorize your Slack user
Choose Slack (User), select the intended workspace, and approve the requested permissions. Availability varies by organization; Slack may not appear yet.
- 3
Grant your Sprite access
- 4
Test from your Sprite
Acts as the authorizing Slack user. Choose Slack (Bot) instead when messages should come from a bot.
Open the dashboard Read connector docs
Use Sprites with Slack (Bot)
Let a Sprite work in Slack as a bot rather than as your user.
- 1
Open your organization's Sprites Connectors
In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector.
- 2
Authorize the Slack bot
Choose Slack (Bot), select the intended workspace, and approve the bot permissions. Availability varies by organization; Slack may not appear yet.
- 3
Grant your Sprite access
- 4
Test from your Sprite
Access depends on the bot's granted permissions and channel membership. It does not have the user connector's search permission.
Open the dashboard Read connector docs
Use Sprites with Discourse
Read or post on a Discourse forum from a Sprite with your forum permissions.
- 1
Open your organization's Sprites Connectors
In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector.
- 2
Authorize your forum account
Choose Discourse, enter the forum URL, and select Read-only or Read & write. Approve access on the forum, then paste its authorization code back into the connector form.
- 3
Grant your Sprite access
- 4
Test from your Sprite
The forum issues a user API key. This is not an admin API key or a Slack-style OAuth connection.
Open the dashboard Read connector docs
Use Sprites with S3-compatible Object Store
Access an S3-compatible bucket without keeping its storage credentials in a Sprite.
- 1
Open your organization's Sprites Connectors
In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector.
- 2
Configure and test your bucket
Choose S3-compatible Object Store. Enter the bucket, endpoint URL, region, access key ID, and secret access key. Test the connection before saving.
- 3
Grant your Sprite access
- 4
Test from your Sprite
The gateway signs storage requests. Use credentials scoped to the bucket and operations you need.
Open the dashboard Read connector docs
Use Sprites with Fly.io Machines
Call the Fly Machines API from a Sprite using an organization-scoped token.
- 1
Open your organization's Sprites Connectors
In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector.
- 2
Generate a scoped Fly.io token
Choose Fly.io Machines, select read-only or read-write access, and generate a token. Test the connection and save it.
- 3
Grant your Sprite access
- 4
Test from your Sprite
A built-in Custom API preset for api.machines.dev. Choose the least access required for your task.
Open the dashboard Read connector docs
Use Sprites with Custom API
Connect a token-authenticated HTTP API through the Sprites gateway.
- 1
Open your organization's Sprites Connectors
In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector.
- 2
Configure and test your API
Choose Custom API. Enter the base URL and token, choose its authentication method, and provide a test URL. Test the connection before saving.
- 3
Grant your Sprite access
- 4
Test from your Sprite
Supports bearer or custom headers, query parameters, and token-bearing URL paths. The upstream must be publicly reachable; private and loopback addresses are blocked.
Open the dashboard Read connector docs
Use Sprites with Steel Browser Tools
Stateless scraping, screenshots, and PDFs without storing your key on a Sprite.
- 1
Open your organization's Sprites Connectors
In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector.
- 2
Enter your Steel API key
Choose Steel Browser Tools in Add connector and paste a key from app.steel.dev/settings/api-keys. Availability varies by organization during rollout. The gateway supplies the stored key; do not copy it into your Sprite.
- 3
Grant your Sprite access
- 4
Test from your Sprite
Only POST /v1/scrape, /v1/screenshot and /v1/pdf are supported. CDP, WebSocket, sessions, credentials and profiles are not supported. Screenshot/PDF URLs are hosted publicly by Steel. Saving or replacing a key and each connection test run a one-page scrape charged to your Steel account.
Open the dashboard Read connector docs
Use Sprites with Linkup
Search the web and fetch pages without putting your key on a Sprite.
- 1
Open your organization's Sprites Connectors
In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector.
- 2
Enter your Linkup API key
Choose Linkup in Add connector and paste a key from app.linkup.so. Availability varies by organization during rollout. The gateway supplies the stored key; do not copy it into your Sprite.
- 3
Grant your Sprite access
- 4
Test from your Sprite
Only POST /v1/search, POST /v1/fetch and GET /v1/credits/balance are supported. Product requests use your Linkup credits; validation only reads credit balance. Research and extraction jobs are not supported.
Open the dashboard Read connector docs
Use Sprites with Firecrawl
Scrape, search, and map websites without putting your key on a Sprite.
- 1
Open your organization's Sprites Connectors
In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector.
- 2
Enter your Firecrawl API key
Choose Firecrawl in Add connector and paste a key from firecrawl.dev/app/api-keys. Availability varies by organization during rollout. The gateway supplies the stored key; do not copy it into your Sprite.
- 3
Grant your Sprite access
- 4
Test from your Sprite
Only POST /v2/scrape, /v2/search, /v2/map and GET /v2/team/credit-usage are supported. Scrape, search, and map requests use your Firecrawl credits. Saving, replacing, and testing a key only read credit usage and do not start a scrape. Crawl, batch jobs, browser sessions and agents are not supported. Keep requests under the gateway's 120-second timeout.
Open the dashboard Read connector docs
Use Sprites with Deepgram
Prerecorded speech recognition and HTTP text-to-speech with your own Deepgram key.
- 1
Open your organization's Sprites Connectors
In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector.
- 2
Enter your Deepgram API key
Choose Deepgram in Add connector and paste a project key from console.deepgram.com. Availability varies by organization during rollout. The gateway supplies the stored key; do not copy it into your Sprite.
- 3
Grant your Sprite access
- 4
Test from your Sprite
Saving or replacing a key and each connection test run a roughly 18-second sample transcription charged to your Deepgram account. Supports POST /v1/listen and POST /v1/speak. Audio responses are buffered; WebSocket realtime speech and Voice Agent are not supported. Prefer public audio URLs for inputs over 8 MB.
Open the dashboard Read connector docs
Use Sprites with Fireworks
OpenAI-compatible inference without storing your Fireworks key on a Sprite.
- 1
Open your organization's Sprites Connectors
In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector.
- 2
Enter your Fireworks API key
Choose Fireworks in Add connector and paste an inference key from app.fireworks.ai/settings/users/api-keys. Availability varies by organization during rollout. The gateway supplies the stored key; do not copy it into your Sprite.
- 3
Grant your Sprite access
- 4
Test from your Sprite
Inference is charged to your Fireworks account. Saving, replacing and testing read one account name and require account-list permission; they do not verify inference permission or balance. Supports POST chat/completions, completions and embeddings under /inference/v1, plus GET /v1/accounts, which lets authorized Sprites list account metadata visible to the key, not only the name read during validation. No account writes, deployments, files or batches.
Open the dashboard Read connector docs
Use Sprites with Parasail
OpenAI-compatible inference without storing your Parasail key on a Sprite.
- 1
Open your organization's Sprites Connectors
In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector.
- 2
Enter your Parasail API key
Choose Parasail in Add connector and paste a standard inference key from www.saas.parasail.io/keys. Availability varies by organization during rollout. The gateway supplies the stored key; do not copy it into your Sprite.
- 3
Grant your Sprite access
- 4
Test from your Sprite
Inference is charged to your Parasail account. Saving and testing only list models. Supports POST chat/completions, completions, embeddings and GET models under /v1; no deployment management, files or batches.
Open the dashboard Read connector docs
Use Sprites with Depot build insights
Read container-build status and project metadata without storing a Depot token on a Sprite.
- 1
Open your organization's Sprites Connectors
In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector.
- 2
Enter your Depot organization or user token
Create a token in the Depot dashboard under Organization Settings → API Tokens, or Account settings → API Tokens for a user token. It must be able to list your organizations; project-only tokens are not supported. Availability varies by organization during rollout. The gateway supplies the stored token; do not copy it into your Sprite.
- 3
Grant your Sprite access
- 4
Test from your Sprite
Read-only organizations, projects and build metadata. This does not run builds or proxy Depot CLI/BuildKit; no build logs, registry access or token management. Saving, replacing and testing list organizations without starting compute. Supports ListOrganizations, ListProjects, GetProject, ListBuilds and GetBuild.
Open the dashboard Read connector docs
Use Sprites with Upstash Redis
Read and write Redis data over HTTP without placing your database token on a Sprite.
- 1
Open your organization's Sprites Connectors
In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector.
- 2
Enter your database REST URL and token
Copy the REST URL and REST token from the Upstash database console. Availability varies by organization during rollout. The URL is immutable; create a new connector for a different database. The gateway supplies the stored token; do not copy it into your Sprite.
- 3
Grant your Sprite access
- 4
Test from your Sprite
Supports individual key/value, hash, list, set and sorted-set commands. No TCP Redis, SDK auto-pipelines, scripts, transactions, pub/sub or administrative commands. Saving, replacement and tests run PING, which may count toward Upstash usage.
Open the dashboard Read connector docs
Use Sprites with Tigris
Create private Tigris buckets without placing an admin key on your Sprite.
- 1
Open your organization's Sprites Connectors
In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector.
- 2
Configure Tigris
Supply an existing Tigris access-key ID and secret with permission to list and create buckets. The gateway keeps the credential off your Sprite.
- 3
Grant your Sprite access
- 4
Test from your Sprite
Authorized Sprites can list buckets and create private buckets with globally unique names. An admin key has broad upstream access, but this connector only forwards listing and creation; no deletion, IAM, bucket settings or object operations. Use an S3 connector for access to an individual bucket. Saving, replacing and testing list buckets without creating one; this does not verify create permission. Requests may incur Tigris charges. Keep both credentials off your Sprite.
Open the dashboard Read connector docs
Use Sprites with AgentMail
Send and receive email from a Sprite without exposing your AgentMail key.
- 1
Open your organization's Sprites Connectors
In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector.
- 2
Configure AgentMail
Use an API key from your existing AgentMail account. The gateway keeps the credential off your Sprite.
- 3
Grant your Sprite access
- 4
Test from your Sprite
Email resources only, with polling for incoming mail. Sending messages has real external effects and may consume AgentMail usage. Domain, API-key and AgentID administration are not supported. The gateway stores the key; do not copy it into your Sprite.
Open the dashboard Read connector docs
Use Sprites with Resend
Send email from a Sprite through Resend without putting your API key on it.
- 1
Open your organization's Sprites Connectors
In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector.
- 2
Configure Resend
Create a Resend API key with Sending access limited to your sending domain. Use a Full access key only if agents must read delivery status. The gateway keeps the credential off your Sprite.
- 3
Grant your Sprite access
- 4
Test from your Sprite
Sends real email from your domain and uses your Resend quota (every recipient counts). Only sending (single and batch, up to 100) and reading one email's status are forwarded; domains, API keys, contacts, broadcasts and the sent-mail list are refused even with a full-access key. Sending-access keys cannot read delivery status. Saving and testing do not send email.
Open the dashboard Read connector docs
Use Sprites with Neon
Create and branch Neon Postgres databases from a Sprite without putting your API key on it.
- 1
Open your organization's Sprites Connectors
In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector.
- 2
Configure Neon
Create a Neon API key. Use a project-scoped key if Sprites should only reach one project, or an organization key if agents create their own projects. The gateway keeps the credential off your Sprite.
- 3
Grant your Sprite access
- 4
Test from your Sprite
Authorized Sprites can create projects, branches, databases, roles and compute, and fetch connection strings, which are database credentials for every project the key can see. Deleting projects, organization and API-key administration, transfers, sharing and Neon Auth are refused. Saving and testing only list projects.
Open the dashboard Read connector docs
Use Sprites with ElevenLabs
Build and run ElevenLabs voice agents from a Sprite without putting your API key on it.
- 1
Open your organization's Sprites Connectors
In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector.
- 2
Configure ElevenLabs
Create an ElevenLabs API key limited to ElevenAgents (and Voices and Models read if Sprites configure agents), with a credit limit. The gateway keeps the credential off your Sprite.
- 3
Grant your Sprite access
- 4
Test from your Sprite
Authorized Sprites can create and change agents, knowledge base and tools, read conversations, and place outbound calls, all billed to your ElevenLabs credits. Live conversations connect to ElevenLabs directly with a short-lived signed URL, so the key stays in the gateway. Workspace secrets, settings and members, voice cloning, and text to speech and speech to text are refused. Saving and testing only list agents.
Open the dashboard Read connector docs
Use Sprites with SenseLab
Share agent memory, briefings and outcomes across disposable Sprites.
- 1
Open your organization's Sprites Connectors
In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector.
- 2
Configure SenseLab
Create a non-admin API key in SenseLab Settings → API Keys. Replace the default * scope with the memory paths and read/write permissions your Sprites need. The gateway keeps the credential off your Sprite.
- 3
Grant your Sprite access
- 4
Test from your Sprite
Admin keys are rejected. A non-admin key is not necessarily narrowly scoped: the default * scope can grant read/write access to every memory path. Authorized Sprites share the stored key's permissions; use separate scoped keys and connections for isolation. Agent and session IDs are provenance, not access controls. Saving, replacing and testing check key identity and admin status, not write permission. Requests use your SenseLab plan. Only supported memory operations are forwarded; no account administration, branch management, training or subscriptions. Your agent must explicitly read context and record findings and outcomes; the connector does not do this automatically.
Open the dashboard Read connector docs
Use Sprites with Blotato
Publish to existing social accounts through Blotato without exposing its API key.
- 1
Open your organization's Sprites Connectors
In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector.
- 2
Configure Blotato
Connect social accounts in Blotato first, then provide your Blotato API key. The gateway keeps the credential off your Sprite.
- 3
Grant your Sprite access
- 4
Test from your Sprite
Creating a Blotato API key ends the free trial and starts a paid subscription. Use existing social accounts connected in Blotato; account authorization is not performed here. Publishing has real external effects and consumes your Blotato plan. Keep the API key off your Sprite.
Open the dashboard Read connector docs
Use Sprites with Keenable
Search with Keenable without placing its key on a Sprite.
- 1
Open your organization's Sprites Connectors
In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector.
- 2
Configure Keenable
Use an API key from your existing Keenable account. The gateway keeps the credential off your Sprite.
- 3
Grant your Sprite access
- 4
Test from your Sprite
Saving or replacing a key and each connection test fetch one small public page using your key, which consumes Keenable credits. Search and fetch requests also consume your plan. Only POST /v1/search and GET /v1/fetch are supported. The gateway supplies the stored credential; do not copy it into your Sprite.
Open the dashboard Read connector docs
Use Sprites with LemonSlice
Read the history and status of existing LemonSlice sessions.
- 1
Open your organization's Sprites Connectors
In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector.
- 2
Configure LemonSlice
Create sessions outside the gateway first, then supply a LemonSlice API key from the developers dashboard. The gateway keeps the credential off your Sprite.
- 3
Grant your Sprite access
- 4
Test from your Sprite
Read-only session history and status for existing LemonSlice sessions. This connector does not create or control sessions, generate video, or support WebRTC or WebSockets. Saving, replacing and testing a key only read session history; they do not start a paid session. Sessions must already be created outside the gateway.
Open the dashboard Read connector docs
Use Sprites with Mnemom
Read Mnemom trust and agent information without storing the API key on a Sprite.
- 1
Open your organization's Sprites Connectors
In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector.
- 2
Configure Mnemom
Use an API key from your existing Mnemom account. The gateway keeps the credential off your Sprite.
- 3
Grant your Sprite access
- 4
Test from your Sprite
Read-only Mnemom agent, state, alignment/protection card, checkpoint, trust-edge, proof/certificate and trust advisory/IOC APIs. Enforcement setup and governance mutations are not supported. Saving and testing verify the key identity without changing agent data. The gateway supplies X-Mnemom-Api-Key; authorize only trusted Sprites.
Open the dashboard Read connector docs
Use Sprites with Era
Read linked banking data through Era without exposing a banking API key.
- 1
Open your organization's Sprites Connectors
In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector.
- 2
Configure Era
Link your accounts in Era first and create an fmk key scoped to banking:read. The gateway keeps the credential off your Sprite.
- 3
Grant your Sprite access
- 4
Test from your Sprite
Read-only banking REST access to accounts already linked in Era: accounts, summaries, balances, transactions, categories and tags. Use an fmk key with banking:read permission, monitor its expiry and rotate it before it expires. Money movement, transfers, payments and account linking are not supported. Authorized Sprites can read the financial data visible to this key.
Open the dashboard Read connector docs
Use Sprites with Composio Tools
Discover and execute tools against existing Composio connected accounts.
- 1
Open your organization's Sprites Connectors
In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector.
- 2
Configure Composio Tools
Connect accounts in Composio first. Supply a project API key scoped to tool discovery and execution. The gateway keeps the credential off your Sprite.
- 3
Grant your Sprite access
- 4
Test from your Sprite
Existing preconnected accounts are required. Use a scoped Composio project API key and the connected_account_id for the account you intend to use. Only tool discovery and named-tool execution are supported; no account setup, OAuth, API-key administration, raw credentials, proxy execution, MCP or sessions. Project access is not isolated to a downstream account or user per Sprite: authorized Sprites can act on the connected accounts permitted by the project key. Tool execution can change external data and incur charges. A successful key check does not verify a particular account or tool-execution permission.
Open the dashboard Read connector docs
Use Sprites with Supabase Database
Access a hosted Supabase project's REST database API without exposing its secret key.
- 1
Open your organization's Sprites Connectors
In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector.
- 2
Configure Supabase Database
Copy the hosted project URL from Connect and a modern sb_secret_ key from Settings → API Keys. The gateway keeps the credential off your Sprite.
- 3
Grant your Sprite access
- 4
Test from your Sprite
Only hosted https://
Open the dashboard Read connector docs
Use Sprites with Usable
Use your Usable workspace knowledge through its authenticated MCP service.
- 1
Open your organization's Sprites Connectors
In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector.
- 2
Configure Usable
Use an existing workspace and the official @usabledev/mcp-server@0.21.0 client. Set --usable-url to this connector's gateway URL and --api-token to the dummy value sprites-gateway, never your real key. The gateway keeps the credential off your Sprite.
- 3
Grant your Sprite access
- 4
Test from your Sprite
The gateway supplies Bearer authentication to Usable's remote MCP service. Install the official @usabledev/mcp-server@0.21.0 client with this connector's gateway root as --usable-url and the dummy --api-token sprites-gateway; never put your real Usable key on the Sprite. MCP tools can read and write every workspace permitted by the stored key. Only MCP and client compatibility routes are forwarded, not account or API-key administration. Idle streams must reconnect.
Open the dashboard Read connector docs
Use Sprites with Exa
Search the web and retrieve page contents without storing your Exa key on a Sprite.
- 1
Open your organization's Sprites Connectors
In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector.
- 2
Enter your Exa API key
Choose Exa in Add connector and paste a key from dashboard.exa.ai/api-keys. Availability varies by organization during rollout; Exa may not appear yet. The gateway supplies the stored key; do not copy it into your Sprite.
- 3
Grant your Sprite access
- 4
Test from your Sprite
Only POST /search and POST /contents are forwarded. Saving or replacing a key and each connection test run a one-result search charged to your Exa account.
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.
TanStack AI TanStack
Sprites as a sandbox provider for TanStack AI agents.
Claude Managed Agents Anthropic
Anthropic runs the agent loop; each session's tool calls execute inside a Sprite you control.
Anthropic Connectors Directory Anthropic
Let Claude manage your Sprites.
QM QM Y Combinator
QM includes a built-in Sprites sandbox backend. Select Sprites and provide your Sprites API token.
Cursor Cloud Agents Cursor
Run Cursor Cloud Agent tools on a Sprite while Cursor hosts the agent and model.
Use Sprites with TanStack AI
Sprites as a sandbox provider for TanStack AI agents.
Use Sprites with Claude Managed Agents
Anthropic runs the agent loop; each session's tool calls execute inside a Sprite you control.
Use Sprites with Anthropic Connectors Directory
Let Claude manage your Sprites.
Connects Claude to Sprites through the hosted MCP server. For calling Claude models from inside a Sprite, use the Anthropic API connector in the Connectors tab.
QM Use Sprites with QM
QM includes a built-in Sprites sandbox backend. Select Sprites and provide your Sprites API token.
Use Sprites with Cursor Cloud Agents
Run Cursor Cloud Agent tools on a Sprite while Cursor hosts the agent and model.
- 1
Prepare your Cursor account
Create a Cursor user API key and enable Self-hosted Machines in Cursor's Cloud Agents settings. Use the current privacy setting, not legacy privacy mode. You also need a Sprites organization and a Cursor plan with Cloud Agents.
- 2
Create the integration in the Fly.io dashboard
Select your organization, then open Sprites → Integrations → Cursor Cloud Agents. Enter a name and your Cursor API key to create the Sprite and install the worker.
- 3
Choose the machine in Cursor
Wait for the Sprite to appear under My Machines in Cursor, then select it for a Cloud Agent session.
This is separate from the Cursor plugin and API gateway connectors. The worker runs on the Sprite and stores the Cursor API key in its service environment.
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.
StripeM-Inner