What SpriteCook MCP server does
SpriteCook MCP server connects an AI agent to the SpriteCook service at spritecook.ai. It lets the agent request pixel-art and game-asset work using natural-language instructions, including new sprites, sprite sheets, tilesets, animations, icons, and transparent-background images.
The service also supports workflows around existing assets. An agent can import a local PNG, animate a supplied character, remove an image background, apply a saved character preset, rename an asset, or use a multi-image style guide reference. The README also describes guidance for Godot-ready character exports and asset recovery, but the exact tool names and schemas are not listed.
How it works
The SpriteCook MCP server uses a remote HTTP MCP endpoint. Manual configurations point to https://api.spritecook.ai/mcp/ and send an API key in an Authorization header. Grok Build uses a separate OAuth endpoint at https://api.spritecook.ai/mcp/oauth; its host manages credential storage and refresh.
For automatic setup, run npx spritecook-mcp setup. The command detects installed AI clients, configures their MCP connections, and can install an optional agent skill. That skill provides current workflow guidance for asynchronous job polling, model discovery, quality settings, presets, uploads, background removal, asset organization, and related operations. The README names Cursor, VS Code, Claude, Codex, and Grok Build as supported AI clients.
Setup and configuration
The simplest setup path is:
The setup process may request an API key. API keys can be obtained and managed through the SpriteCook application. For manual configuration, add the SpriteCook MCP endpoint and an Authorization bearer token to the relevant client configuration. Cursor uses .cursor/mcp.json, while VS Code uses .vscode/settings.json.
Grok Build requires a TOML entry using the OAuth URL and can be authenticated from /mcps. If the tools do not appear in Grok Build, the README recommends grok mcp doctor spritecook and grok inspect for diagnosis. The repository also contains a root .mcp.json intended for a Grok Build marketplace submission; marketplace publication is separate from setup.
SPRITECOOK_API_URL can override the API base URL for local development. No other environment variable is documented.
Tools and capabilities
With the connection configured, an agent can ask SpriteCook to:
- Generate pixel-art sprites at a requested size.
- Create character sprite sheets for a game.
- Produce icon sets with transparent backgrounds.
- Generate new assets from a saved character preset.
- Import a local image and animate it.
- Remove an asset background and return a transparent PNG.
- Rename generated assets.
- Work with model discovery, asynchronous job polling, style-guide references, and asset organization through the optional skill guidance.
The README does not provide a complete inventory of MCP tool names, input schemas, model limits, pricing, or output formats beyond references to canonical sprite_url output and transparent PNG results.
Limitations and notes
SpriteCook MCP server requires access to the SpriteCook service and authentication unless the client uses Grok Build's host-managed OAuth flow. The available documentation describes configuration and example workflows, but it does not state whether the service supports offline generation, local model execution, or a self-hosted deployment.
The optional skill is separate from the MCP connection and is described as additional guidance for agent behavior. API URL overrides are documented for local development only. Treat the remote endpoint, authentication method, and client configuration as distinct choices when deploying the integration.