Spritecook MCP Server

SpriteCook MCP Server - Connect your AI agent to SpriteCook for game asset generation, saved presets, import, background cleanup, asset organization

Local serverstdio

What is the Spritecook MCP server?

Spritecook MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. SpriteCook MCP Server - Connect your AI agent to SpriteCook for game asset generation, saved presets, import, background cleanup, asset organization, inspection, and animation.

What you get

Connect your AI agent (Cursor, VS Code, Claude Desktop, Claude Code) to SpriteCook for AI-powered pixel art and game asset generation.

What the assistant can call

Once Spritecook is connected, these are the calls the assistant has available:

  • SPRITECOOK_API_URL — Override the API base URL (for local development)

Configuration and credentials

You will need 2 environment variables: YOUR_API_KEY, SPRITECOOK_API_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

Installation goes through your MCP client rather than a global install: point it at spritecook-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Spritecook's toolset — SPRITECOOK_API_URL — is a fair guide to whether it matches your workflow. It is maintained by spritecook; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Spritecook's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the spritecook mcp server does with a few real requests.

Available tools

ToolWhat it does
SPRITECOOK_API_URLOverride the API base URL (for local development)

How to install the Spritecook MCP server

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

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
YOUR_API_KEYCredential the server authenticates with.Yes
SPRITECOOK_API_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use Spritecook to SPRITECOOK API URL.

Frequently asked questions

It connects Spritecook to MCP-compatible AI assistants such as Claude and Cursor, exposing 1 tool (SPRITECOOK_API_URL) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Spritecook directly.