Aseprite Live logo

Aseprite Live

Drives live or headless Aseprite for sprite editing, layer management, metadata, and Unity-oriented asset workflows.

Install Aseprite Live

Pick your client, then add it in one click or paste the config.

STDIOPython
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "aseprite-live": {
      "command": "uvx",
      "args": [
        "aseprite-live-mcp"
      ],
      "env": {
        "ASEPRITE_MCP_BACKEND": "YOUR_VALUE_HERE",
        "ASEPRITE_PATH": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

The install command didn't complete successfully in our automated test.

uvx aseprite-live-mcp

Downloading pydantic-core (2.0MiB) Downloading cryptography (4.5MiB) Downloaded pydantic-core Downloaded cryptography Installed 29 packages in 16ms Traceback (most recent call last): File "/home/user/.cache/uv/archive-v0/8uUqke1-Ipa2NbaN/bin/aseprite-live-mcp", line 6, in <module> from aseprite_live_mcp.__main__ import main File "/home/user/.cache/uv/archive-v0/8uUqke1-Ipa2NbaN/lib/python3.11/site-packages/aseprite_live_mcp/__main__.py", line 1, in <module> from .server import main

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 15d ago.

Overview

Aseprite Live MCP server connects an MCP client to Aseprite in either a running-editor or headless file-based workflow. It exposes tools for sprites, pixels, metadata, documents, layers, canvas changes, image imports, and animation frames. The live backend sends edits to open documents through an Aseprite bridge, while headless mode operates on `.aseprite` files with Aseprite batch processing. Use it when an agent needs to inspect or modify pixel art, manage sprite structure, or automate asset preparation for a Unity project.

Use cases

  • Create and modify Aseprite sprites through an MCP client
  • Inspect pixels, metadata, documents, and layer structure
  • Organize layers and groups in a pixel-art document
  • Import images or spritesheets into Aseprite
  • Prepare sprite assets for Unity workflows

Key features

  • Live editing of open Aseprite documents
  • Headless operation on `.aseprite` files
  • Pixel and sprite metadata inspection
  • Layer and group management
  • Canvas, image import, and frame operations
  • Unity-oriented sprite-sheet workflows

Tools80

What Aseprite Live lets your agent do. Expand a tool for its parameters.

Self-reported~250 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

5/5 checks healthy over the last 46d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 13d ago via OSV.dev · aseprite-live-mcp (PyPI)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars8Stargazers on the source repository.
Last commit2mo agoMost recent push to the default branch.
Install checkInconclusiveInstall command did not finish in our automated test.
Tools exposed80Callable tools this server registers over MCP.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How Aseprite Live works

What Aseprite Live MCP server does

Aseprite Live MCP server lets an MCP-compatible agent work with Aseprite documents instead of only manipulating files through a separate image library. It can inspect open or saved sprites, create and edit documents, change layer structure, import image content, and add animation frames.

The server supports two operating modes. A headless mode uses Aseprite's batch operation path against files on disk. A live mode connects to a running editor, including open documents and unsaved tabs, through a bridge script and relay. In live mode, edits are described as individual undoable actions in Aseprite.

How it works

For headless use, configure the MCP server with the headless backend and provide a file argument to tools that act on a document. The README's example workflow creates a sprite, draws on it, and exports an image without requiring the editor to be open.

The live workflow requires more than the Python package. A Lua bridge script must be placed in Aseprite's scripts folder, and a Python relay must be started with the websockets package installed. After launching the bridge from Aseprite's Scripts menu, set the MCP backend to live. The bridge panel reports connection and activity status and includes a pause control.

Setup and configuration

The package requires Python 3.10 or newer and Aseprite 1.3 or newer. It can be launched with uvx aseprite-live-mcp or pipx run aseprite-live-mcp; installation from a cloned source checkout is also documented.

Set ASEPRITE_MCP_BACKEND to headless or live. ASEPRITE_PATH can point to the Aseprite executable. Common Steam and standalone installations may be detected automatically when this variable is omitted. A JSON-configured client can start the server with the uvx command and aseprite-live-mcp argument.

Tools and capabilities

The listed MCP tools cover:

  • Connection and document access through status, path, open_sprite, save_sprite, close_sprite, set_active_sprite, and list_sprites.
  • Sprite inspection and metadata through get_sprite_info, get_pixel, get_pixels, set_sprite_metadata, and get_sprite_metadata.
  • Creation and canvas changes through create_sprite, expand_canvas, and import_spritesheet.
  • Layer organization through add_layer, add_group, move_layer_to_group, list_layers, delete_layer, rename_layer, set_layer_visibility, set_layer_opacity, flatten_sprite, set_layer_blend_mode, duplicate_layer, merge_layer_down, and move_layer.
  • Asset and animation input through import_image_as_layer and add_frame.

The broader README describes Unity sprite-sheet and .meta export, per-slice pivots, art-QA checks, isometric primitives, tilemaps, and in-editor approval or point-selection interactions.

Limitations and notes

Live editing depends on a running Aseprite instance, the bridge script, the relay process, and user trust approval when the script requests it. The bridge and relay are in the repository rather than the pip package, so they must be obtained separately for live mode. Headless mode avoids the open editor but works against files on disk.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Aseprite Live

Aseprite Live is an MCP server that connects AI clients to Aseprite through either a live editor bridge or headless batch mode. Its main tools inspect and modify sprites, pixels, metadata, documents, layers, canvases, imported images, and animation frames. It also supports Unity-oriented asset workflows described in the project documentation.

Install it with `uvx aseprite-live-mcp` or `pipx run aseprite-live-mcp`, using Python 3.10 or newer and Aseprite 1.3 or newer. Source installation with `pip install -e .` is also documented. Live mode additionally requires the repository's bridge script and relay.

Set `ASEPRITE_MCP_BACKEND` to `headless` in the MCP client configuration. Headless tools operate on `.aseprite` files on disk and do not require the editor to be open. The `ASEPRITE_PATH` variable can specify the Aseprite executable when automatic detection does not find it.

Set the backend to `live`, install `claude-bridge.lua` in Aseprite's scripts folder, start `python bridge/relay_server.py`, and run the bridge from Aseprite's Scripts menu. The relay requires the `websockets` package, and the script may request trust approval.

Yes, the README provides a Cursor installation link for this server. Cursor can configure it as a stdio MCP server using `uvx aseprite-live-mcp`; choose the `headless` or `live` backend in the server environment configuration.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewAseprite Live AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/aseprite-live?style=directory)](https://allmcps.com/mcp/aseprite-live)
HTML Embed
<a href="https://allmcps.com/mcp/aseprite-live"><img src="https://allmcps.com/api/badge/aseprite-live?style=directory" alt="Aseprite Live on AllMCPs" /></a>