aseprite-mcp

aseprite_import_image

Import an external PNG, JPG, or GIF into Aseprite as a new sprite for tracing or onto a layer or frame of the active document at specified coordinates.

Instructions

Bring an external image into the pipeline. With asNewSprite it becomes a new document (useful for tracing over a reference, or for slicing an existing sprite sheet by hand). Otherwise it is drawn onto a layer of the active document at (x, y) - handy for stamping a palette reference, a logo, or a texture into a piece.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "source": "<source>"
    },
    "name": "aseprite_import_image"
  }
}

Input Schema

Name	Required	Description
`x`	No	Left edge to place the image at (default 0).
`y`	No	Top edge to place the image at (default 0).
`frame`	No	Target frame (default 0).
`layer`	No	Target layer (a new layer is created when omitted).
`source`	Yes	Absolute path to the image to import (PNG, JPG, GIF, ...).
`document`	No	Document to act on: a short name inside the art folder ("hero"), a relative path, or an absolute .aseprite path. Omit to use the active document.
`asNewSprite`	No	Import as a new document rather than into the active one.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 27, 2026

TDQS

A3.6/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full behavioral burden. It discloses the two modes and that non-new-sprite imports are drawn onto a layer of the active document at (x, y), but it omits mutation side effects such as layer creation behavior, frame targeting, reversibility, or what happens to the active document.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in the first sentence, and the following sentences efficiently explain the two operational modes with relevant examples. The parenthetical examples are useful, though slightly verbose, keeping it from a perfect score.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter mutation tool with no annotations and no output schema, the description covers the main branching behavior but leaves gaps around return values, error handling, and side effects like document/frame/layer interactions. The rich schema reduces the burden, but the description could do more to prepare an agent for safe invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so all parameters are already documented in the input schema. The description names `asNewSprite` and references (x, y), but it does not add syntax, formatting, or constraints beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: importing an external image into the pipeline, with a clear branch for `asNewSprite` versus drawing onto the active document. It does not name a sibling tool to contrast with, but the purpose is unambiguous and distinguishable from generic open/create operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides concrete use cases for both modes: tracing over a reference or manually slicing a sprite sheet with `asNewSprite`, and stamping a palette reference, logo, or texture otherwise. It does not state when not to use the tool or name alternatives, so it stops short of full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server