Name: SpriteCook
Author: SpriteCook

LABSCO SUMMARY

Art generated in the loop, with the style pinned to one asset.

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.

What it is

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.

What you get

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.

Requirements

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.

Setup effort

One command plus a key — npx spritecook-mcp setup, then supply credentials

See installation options

USE CASES

01

Getting placeholder art that does not look like placeholder art

Describe the sprite and it lands in the project while you carry on writing code.

02

Keeping a set of assets consistent

Generate the first one, then reference its id for the rest so they share a palette and proportions.

03

Animating something you already have

Import the local image first, then ask for the walk cycle on the asset id that comes back.

04

Adjusting an asset instead of regenerating it

Pass its id with the change you want, rather than starting again from the prompt.

05

Getting an asset ready to drop into the engine

Strip the background to a transparent PNG, rename it to something you will recognise, and export it in the shape Unity or Godot expects.

06

Coming back to an asset weeks later

Keep the ids in a manifest file next to the project so a future session can edit or animate without opening the dashboard.

BEFORE YOU INSTALL

What to know first

Requires

A client that can reach a remote MCP server over HTTP

INSTALLATION

Connect your client

Server setup

npx

Detected clients — setup command

TERMINAL

npx spritecook-mcp setup

Hosted endpoint

ENDPOINT URL

https://api.spritecook.ai/mcp/

Add this hosted endpoint to your MCP client using the credentials listed under Requirements.

MCP Clients

Cursor

CURSOR · JSON

{
  "mcpServers": {
    "spritecook": {
      "url": "https://api.spritecook.ai/mcp/",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}

VS Code

VS CODE · JSON

{
  "servers": {
    "spritecook": {
      "type": "http",
      "url": "https://api.spritecook.ai/mcp/",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}

Grok Build

GROK BUILD · TOML

[mcp_servers.spritecook]
url = "https://api.spritecook.ai/mcp/oauth"
enabled = true
tool_timeout_sec = 6000

Claude Desktop — plugin

In the Claude desktop app, open the Code tab and click Customize in the sidebar

Click the +, then Create plugin, then Add marketplace, then Add from a repository

Paste the plugin repo URL https://github.com/SpriteCook/claude-plugin and click Sync

Install SpriteCook and connect your account

SpriteCook