Works with your agent. Yes, that one too.

1. 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. 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. 3

   Authenticate when Codex prompts you

   The plugin talks to the hosted MCP server at https://sprites.dev/mcp.

4. ✓

   Ask Codex to prove it's connected

   › List my sprites.

   An empty list is a successful, authenticated response.

1. 1

   Install the Sprites plugin from the Cursor Marketplace

   Cursor prompts you to authorize with Sprites over OAuth on first use.

2. 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.

3. ✓

   Ask the agent to prove it's connected

   › List my sprites.

1. 1

   Install straight from the repository

   $ agy plugin install https://github.com/superfly/sprites-antigravity-plugin
2. 2

   Authenticate the sprites server

   › /mcp

   Use restricted access unless your workflow genuinely needs broader organization control.

3. ✓

   List what you've got

   › /sprites:list

   The plugin also ships /sprites:new, /sprites:run, /sprites:checkpoint, /sprites:service, and /sprites:cleanup.

1. 1

   Install the plugin

   $ grok plugin install superfly/sprites-grok-plugin --trust
2. 2

   Enable it

   $ grok plugin enable sprites
3. 3

   Reload plugins, or restart Grok

   › /plugins

   Then press r to reload.

4. 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.

5. ✓

   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.

1. 1

   Install from GitHub

   $ cortex plugin install superfly/sprites-cortex-plugin
2. 2

   Enable the plugin

   $ cortex plugin enable sprites
3. 3

   Reload inside your session, or restart Cortex Code

   › /plugin reload
4. ✓

   Ask Cortex to list your environments

   › List my sprites.

1. 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. 2

   Start that profile

   $ npx @deepseek-ai/dsh --profile web
3. 3

   Complete browser OAuth and pick your Fly.io organization

   Restart Harness once if the first tool sync timed out while you were authorizing.

4. ✓

   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.

1. 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. 2

   Export a Sprites token into Pi's environment

   $ export SPRITES_TOKEN='...'

   This integration authenticates with a token, not browser OAuth.

3. ✓

   Ask Pi to list your environments

   › List my sprites.

1. 1

   Install the Sprites extension

2. 2

   Set your API token

   › Sprites: Set API Token

   Run it from the Command Palette and paste your Sprites.dev API token.

3. 3

   Open a Sprite

   › Sprites: Open Sprite

   Its filesystem appears in your workspace, editable in place.

4. ✓

   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.

1. 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. 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. 3

   Authorize in the browser on first use

4. ✓

   Ask your agent to prove it's connected

   › List my sprites.

1. 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. 2

   Complete browser OAuth on first MCP use

   Restricted connector tokens may enforce a sprite-name prefix, creation cap, label, or expiry.

3. ✓

   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.