The reference id is what makes this more than a generator behind a chat window: make one hero asset, pass its id to everything after, and the whole set looks like one artist made it. The habit worth adopting is keeping those ids in a manifest file beside the project — a later session can then animate or edit an asset without going back to the dashboard to find it.
SpriteCook's connector between its pixel-art generator and a coding agent, so characters, tilesets, props, textures and animations are produced in the same session as the code that uses them. The server is hosted; a setup command detects your editors and wires them up.
- Sprites, tilesets, props, UI kits and seamless textures generated from a plain description, at the resolution and palette you ask for.
- An existing sprite animated into whatever motion you describe, and frame-level editing when the generated motion needs correcting.
- Style held constant across a set: generate one hero asset, then pass its id as reference_asset_id to everything after, and palette and proportions carry across.
- An existing asset revised rather than regenerated — pass its id as edit_asset_id with the change, a cape added or a sword made to glow.
- A local PNG imported first, then animated from the asset id that comes back.
- Background removal to a transparent PNG, renaming, and exports shaped for Unity and Godot.
- Workflow skills installed alongside the connection, covering asynchronous job polling, model discovery, saved presets, multi-image style references and asset recovery, so the agent calls things in a workable order.
A SpriteCook account and an API key from the SpriteCook app, sent as a bearer token to the hosted endpoint. Running the setup command detects your installed editors, authenticates, writes the config and installs the workflow skills; you can also paste the URL and header into your editor's MCP config yourself. Grok Build is the exception — it uses host-managed OAuth and never exposes the credential to the model.
One command plus a key — npx spritecook-mcp setup, then supply credentials