Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Aseprite Claude Connector

PYPI · ASEPRITE-CLAUDE-CONNECTOR

Let Claude draw in a running Aseprite, and export straight to Godot or Unity

0 this week 79 Trust /100

Last scanned (13 hours ago)

Scores higher than 75% of PyPI servers

Category Design and Media

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 0 of 29 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to UmarMuhammad18/aseprite-claude-connector). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 1 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability77
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 19541 tokens (~101/item across 193 items; 187 tools + 6 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (11% of tools); any adoption earns full credit.Pass
Tool Safety96
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 6 of 7 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "cancel_ask_point" implies "withdraw" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Partial
  • An AI judge read all 189 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 20 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 19 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 17 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 13 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 12 Nov 26 64

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed pypi/aseprite-claude-connector@0.4.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo UmarMuhammad18/aseprite-claude-connector
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/UmarMuhammad18/aseprite-claude-connector/.github/workflows/publish.yml@refs/tags/v0.4.0
Rekor log index 3815509317
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:7a41c49640632cabb03de5769d75b305b5d88394ad2765070cd745e4e636b370

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 29 packages
Packages resolved 29
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 187 exposed · ~18,843 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
draw_iso_cylinder ~137

Draw a vertical isometric cylinder (tank/silo/chimney): top ellipse + shaded body + front rim, auto-shaded from ``color``. ``top_y`` is the top of the body. One undo step. Headless: pass ``file``. ``preview`` true also returns a before/after picture of the canvas with the changed-pixel count and bbox.

NameTypeReqDescription
center_xintegeryes–
colorstringyes–
file–––
heightintegeryes–
previewboolean––
radiusintegeryes–
top_yintegeryes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

draw_line ~113

Draw a 1px line from (x1,y1) to (x2,y2). One undo step. Headless: pass ``file``. ``preview`` true also returns a before/after picture of the canvas with the changed-pixel count and bbox.

NameTypeReqDescription
colorstringyes–
file–––
previewboolean––
x1integeryes–
x2integeryes–
y1integeryes–
y2integeryes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

draw_on_tile ~120

Set pixels on one tile of a tilemap layer's tileset. ``pixels`` is a list of {x, y, color} objects (color #rrggbb or #rrggbbaa; x/y relative to the tile's top-left). Pixels outside the tile are skipped and counted. Every placed instance of the tile updates. One undo step. Headless: pass ``file``.

NameTypeReqDescription
file–––
layerstringyes–
pixelsarrayyes–
tile_indexintegeryes–

No output schema declared.

No examples provided.

draw_pixels ~119

Set individual pixels: ``pixels`` is a list of ``{"x": int, "y": int, "color": "#rrggbb[aa]"}``. The precision tool for detail work — one undo step for the whole batch. Capped at 4096 pixels per call. Headless: pass ``file``. ``preview`` true also returns a before/after picture of the canvas with the changed-pixel count and bbox.

NameTypeReqDescription
file–––
pixelsarrayyes–
previewboolean––
NameTypeReqDescription
resultobjectyes–

No examples provided.

draw_polyline ~107

Stroke connected line segments through ``points`` (ordered [x, y] pairs); ``close=True`` joins the last point back to the first. One undo step. Headless: pass ``file``. ``preview`` true also returns a before/after picture of the canvas with the changed-pixel count and bbox.

NameTypeReqDescription
closeboolean––
colorstringyes–
file–––
pointsarrayyes–
previewboolean––
NameTypeReqDescription
resultobjectyes–

No examples provided.

draw_rectangle ~133

Draw a rectangle on the active layer + frame. ``color`` is #rrggbb or #rrggbbaa. ``fill`` false draws only the outline. One undo step (live). Headless: pass ``file``. ``preview`` true also returns a before/after picture of the canvas with the changed-pixel count and bbox.

NameTypeReqDescription
colorstringyes–
file–––
fillboolean––
heightintegeryes–
previewboolean––
widthintegeryes–
xintegeryes–
yintegeryes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

duplicate_frame ~29

Duplicate frame ``number`` (1-based).

NameTypeReqDescription
file–––
numberintegeryes–

No output schema declared.

No examples provided.

duplicate_layer ~33

Duplicate a layer (with its cels) above the original.

NameTypeReqDescription
file–––
namestringyes–

No output schema declared.

No examples provided.

edit_batch ~118

Run several editing tools as one undo step, so one Ctrl-Z reverts them all. Each step is ``{"tool": "draw_line", "args": {...}}``, in order. If any step fails, none of them apply. The pixel cap covers the whole batch. Steps can't see each other's results, and tools that save or export can't be batched. Headless: pass ``file`` here, not in the steps.

NameTypeReqDescription
file–––
labelstring––
stepsarrayyes–

No output schema declared.

No examples provided.

edit_in_selection ~126

"Fix this bit": run editing tools so they change only what's inside the current selection, as one undo step. Anything they'd do outside it, on any layer or frame, is put back. Steps are written as in ``edit_batch``. Select the area in Aseprite first; ``look`` with ``selection`` shows what's selected. Steps can't change the frames, layers, or canvas size. Headless: pass ``file`` here, not in the steps.

NameTypeReqDescription
file–––
labelstring––
stepsarrayyes–

No output schema declared.

No examples provided.

erase_area ~74

Erase pixels to transparent. Pass an explicit rect (works everywhere, including headless), or pass nothing to erase the current selection — including non-rectangular ones (live editor). One undo step.

NameTypeReqDescription
file–––
height–––
width–––
x–––
y–––

No output schema declared.

No examples provided.

expand_canvas ~82

Grow (or shrink, with negatives) the canvas per side WITHOUT scaling content — existing pixels keep their positions relative to the old origin. One undo step. Headless: pass ``file``.

NameTypeReqDescription
bottominteger––
file–––
leftinteger––
rightinteger––
topinteger––

No output schema declared.

No examples provided.

explain_changes ~64

Say which Aseprite tool, menu, or shortcut would do what Claude just did, so you pick up the technique. Covers the ``last`` most recent edits, newest repeats merged. Shortcuts are Aseprite's defaults.

NameTypeReqDescription
lastinteger––

No output schema declared.

No examples provided.

export_animation ~152

Write the animation (or one ``tag``) as a looping ``.gif`` or animated ``.png`` at ``path``, scaled up ``scale`` times with sharp pixels (4 turns a 384x128 banner into 1536x512). Each frame keeps its own duration. An animated PNG keeps transparency; a GIF is laid on ``background`` (#rrggbb, black by default), as are both when it's given. Written from Python, so the live editor shows no security prompt. Headless: pass ``file``.

NameTypeReqDescription
background–––
file–––
pathstringyes–
scaleinteger––
tag–––

No output schema declared.

No examples provided.

export_gamemaker ~122

Write sprite strips GameMaker cuts up by itself: one ``<name>_<tag>_stripN.png`` per tag, or ``<name>_stripN.png`` with no tags. Drag them into GameMaker, or import them in its sprite editor. GameMaker gives a sprite one speed, so the result lists each strip's ``fps`` to enter there, and flags uneven timing. Headless: pass ``file``.

NameTypeReqDescription
file–––
name–––
output_dirstringyes–

No output schema declared.

No examples provided.

export_godot ~147

Export a horizontal sprite sheet AND a Godot 4 ``SpriteFrames`` ``.tres`` beside it, with one animation per tag, keeping each frame's timing, the tag's direction, and its repeat count. No tags gives one looping ``default`` animation. Export inside a Godot project and the ``res://`` path is worked out from ``project.godot``; otherwise ``project_found`` is false and the file must sit at the project root. For sharp pixels, set the node's Texture Filter to Nearest. Headless: pass ``file``.

NameTypeReqDescription
file–––
png_pathstringyes–

No output schema declared.

No examples provided.

export_layers ~126

Export every image layer (recursing into groups) as its own PNG in ``out_dir``, named ``<sanitized-layer-name>.png``. Hidden layers are exported too; every layer's original visibility is restored afterwards, so the document ends exactly as it started. A multi-frame sprite splits each layer into ``<name>1.png``, ``<name>2.png``, ...; the returned ``files`` lists what was actually written. Headless: pass ``file``.

NameTypeReqDescription
file–––
out_dirstringyes–

No output schema declared.

No examples provided.

export_sprite ~130

Export the active sprite to a file; format is chosen by ``out_path`` extension (.png, .gif, ...). A multi-frame sprite saved to a single-image format is split into ``<name>1.ext``, ``<name>2.ext``, ...; a multi-frame sprite saved to ``.gif`` becomes one animated GIF (all frames, honoring per-frame durations). The returned ``files`` lists what was actually written. Does not modify the sprite. Headless: pass ``file``.

NameTypeReqDescription
file–––
out_pathstringyes–

No output schema declared.

No examples provided.

export_spritesheet ~90

Pack all frames into a single sprite-sheet image (optionally writing a JSON atlas to ``data_path``). ``sheet_type`` is rows | columns | horizontal | vertical | packed. Does not modify the sprite. Headless: pass ``file``.

NameTypeReqDescription
data_path–––
file–––
out_pathstringyes–
sheet_typestring––

No output schema declared.

No examples provided.

export_tags ~115

Export each animation tag's frame range as its own file in ``out_dir``: an animated ``<tag-name>.gif`` (format="gif", default) or a horizontal ``<tag-name>.png`` strip (format="png"). Errors if the sprite has no tags. Returns each tag's file, frame range, and frame count. Does not modify the sprite. Headless: pass ``file``.

NameTypeReqDescription
file–––
formatstring––
out_dirstringyes–

No output schema declared.

No examples provided.

export_tileset ~116

Export a tilemap layer's tileset as a horizontal PNG strip (plus an Aseprite JSON atlas if ``data_path`` is given). The strip includes tile 0 (the empty tile) first, so tile index i sits at x = i * tile_width. Writes files but does not modify the sprite (it does make the layer active). Headless: pass ``file``.

NameTypeReqDescription
data_path–––
file–––
layerstringyes–
output_pathstringyes–

No output schema declared.

No examples provided.

export_to_game ~209

Export the sprite into a game project in one action, ready to select in the engine. ``game_dir`` is the project folder; it's remembered, so leave it out after the first time. Godot is detected from ``project.godot``, Unity from ``Assets`` plus ``ProjectSettings``, and any other folder gets a plain sheet. Art goes in the project's existing sprites or assets folder, or a new ``sprites`` (``Assets/Sprites`` in Unity). Godot gets a PNG, plus a ``SpriteFrames`` ``.tres`` if animated. Unity gets a PNG and a pre-sliced ``.meta``, using ``pixels_per_unit``, and exporting again keeps the references to it working. ``name`` defaults to the sprite's file name. Headless: pass ``file``.

NameTypeReqDescription
file–––
game_dir–––
name–––
pixels_per_unitinteger––

No output schema declared.

No examples provided.

export_unity_slices ~118

Export the sprite as a single PNG AND write a Unity ``.meta`` with one Multiple-mode sprite **per named slice**, each carrying that slice's pivot — so an atlas laid out with slices imports into Unity already sliced *and* pivoted. No competitor's Aseprite→Unity path exports pivots. Requires slices (see create_slice / set_slice_pivot). Headless: pass ``file``.

NameTypeReqDescription
file–––
pixels_per_unitinteger––
png_pathstringyes–
NameTypeReqDescription
alignment–––
frame_size–––
frames–––
guid–––
meta–––
mode–––
pixels_per_unit–––
png–––
png_exists–––
sheet_size–––
sprites–––
texture_size–––

No examples provided.

export_unity_sprite ~170

Export a horizontal sprite sheet AND write the Unity ``.meta`` beside it, pre-sliced into named Multiple-mode sprites (one per frame) — one action, no manual Sprite Editor pass. ``alignment`` is one of center, top_left, top, top_right, left, right, bottom_left, bottom, bottom_right, custom; ``custom`` uses ``pivot_x``/``pivot_y`` (0..1, 0,0 = bottom left). Targets Unity 2021.3+/6. Headless: pass ``file``.

NameTypeReqDescription
alignmentstring––
file–––
pivot_xnumber––
pivot_ynumber––
pixels_per_unitinteger––
png_pathstringyes–
NameTypeReqDescription
alignment–––
frame_size–––
frames–––
guid–––
meta–––
mode–––
pixels_per_unit–––
png–––
png_exists–––
sheet_size–––
sprites–––
texture_size–––

No examples provided.

extend_scene ~249

Grow the canvas by ``left``/``right``/``top``/``bottom`` pixels and fill the new space on ``layer`` (the active one) by continuing its own texture, like turning a portrait scene into a wide banner. Patches of ``patch`` pixels are copied from the ``sample_*`` area (all of the layer by default) and matched to what is already beside them, so no new colours appear. Pick a sample of pure background, like open meadow, so the subject isn't copied, and big enough not to repeat. The margins come from ``frame`` and are shared by the layer's other frames. Other layers just get a bigger canvas. One undo step. Headless: pass ``file``.

NameTypeReqDescription
bottominteger––
file–––
frame–––
layer–––
leftinteger––
patchinteger––
rightinteger––
sample_height–––
sample_width–––
sample_x–––
sample_y–––
seedinteger––
topinteger––

No output schema declared.

No examples provided.

extract_palette_from_image ~92

Extract a palette (median-cut) from an external image file and, by default, set it as the active sprite's palette — the concept-art → locked-palette step. Returns the colors as hex, sorted dark→light. Headless: pass ``file``.

NameTypeReqDescription
file–––
image_pathstringyes–
max_colorsinteger––
replaceboolean––

No output schema declared.

No examples provided.

fill_area ~95

Flood-fill the contiguous same-color region at (x, y). Most reliable on RGB sprites. One undo step. Headless: pass ``file``. ``preview`` true also returns a before/after picture of the canvas with the changed-pixel count and bbox.

NameTypeReqDescription
colorstringyes–
file–––
previewboolean––
xintegeryes–
yintegeryes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

fill_polygon ~107

Scanline-fill an arbitrary polygon given ``points`` (a list of [x, y] pairs, in order). ``color`` is #rrggbb or #rrggbbaa. One undo step. Headless: pass ``file``. ``preview`` true also returns a before/after picture of the canvas with the changed-pixel count and bbox.

NameTypeReqDescription
colorstringyes–
file–––
pointsarrayyes–
previewboolean––
NameTypeReqDescription
resultobjectyes–

No examples provided.

find_stray_pixels ~184

Find pixels and colors that look like accidents, and return a picture of them: the art in gray, with floating ``isolated`` pixels in red, ``orphan`` pixels (touching art but matching none of it) in yellow, and pixels of colors used ``rare`` times or fewer in magenta. Also lists ``near_duplicates``: colors within ``near`` of a much commoner one. Dithering and highlights can be deliberate orphans, so treat this as a list to look over, not to erase. Defaults to the active frame, all visible layers. Read-only. Headless: pass ``file``.

NameTypeReqDescription
file–––
frame–––
layer–––
max_sizeinteger––
nearinteger––
rareinteger––

No output schema declared.

No examples provided.

flatten_sprite ~21

Flatten all layers into a single layer.

NameTypeReqDescription
file–––

No output schema declared.

No examples provided.

flip_sprite ~28

Flip the whole sprite horizontally or vertically.

NameTypeReqDescription
directionstringyes–
file–––

No output schema declared.

No examples provided.

frame_diff ~89

Pixel-exact diff of two composited frames: changed-pixel count and ratio, the bounding box of the change, and whether they're identical. Use it to verify an animation actually moves — or that an edit didn't leak into frames it shouldn't touch. Headless: pass ``file``.

NameTypeReqDescription
file–––
frame_aintegeryes–
frame_bintegeryes–

No output schema declared.

No examples provided.

generate_color_ramp ~108

Generate a dark->light shading ramp from ``base_color`` and APPEND it to the palette in order — ready for ``palette_ramp_walk``. ``count`` colors; ``hue_shift`` pushes shadows toward blue and highlights toward yellow. Returns the ramp as hex. One undo step. Headless: pass ``file``.

NameTypeReqDescription
base_colorstringyes–
countinteger––
file–––
hue_shiftboolean––

No output schema declared.

No examples provided.

get_asked_point ~49

Poll the result of ``ask_point``: ``done`` false while waiting, then the clicked ``x``/``y`` (or ``cancelled`` if the artist pressed Esc).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_color_stats ~75

Return a color histogram of the composited sprite: distinct opaque color count, total opaque pixels, and the ``top`` most-used colors with counts — a palette-drift check for the art-QA loop. Read-only. Headless: pass ``file``.

NameTypeReqDescription
file–––
topinteger––

No output schema declared.

No examples provided.

get_dialog_choice ~36

Poll the result of ``show_choice_dialog``: ``done`` false while the dialog is open, then the chosen button text.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_editor_state ~39

Live editor only: current zoom, scroll, and which sprite pixel the mouse is over — lets an agent know what the artist is looking at.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_palette ~28

Return the active sprite's palette as #rrggbbaa hex strings.

NameTypeReqDescription
file–––

No output schema declared.

No examples provided.

get_pixel ~49

Read one composited pixel (all layers) at (x, y) as #rrggbbaa.

NameTypeReqDescription
file–––
xintegeryes–
yintegeryes–

No output schema declared.

No examples provided.

get_pixels ~91

Read a composited pixel region as a grid of #rrggbbaa strings — the AI feedback loop for 'what does the canvas look like now'. Capped at 4096 px; use a smaller region or export for larger areas.

NameTypeReqDescription
file–––
heightintegeryes–
widthintegeryes–
xintegeryes–
yintegeryes–

No output schema declared.

No examples provided.

get_selection ~50

Report whether a selection exists and its bounding rectangle. (Selection is editor-session state — in headless mode it doesn't persist between calls, so this is mainly a live-editor tool.)

NameTypeReqDescription
file–––

No output schema declared.

No examples provided.

get_sprite_info ~45

Get the active sprite's size, color mode, and layer/frame/tag lists. Headless: pass ``file`` (the .aseprite to inspect).

NameTypeReqDescription
file–––
NameTypeReqDescription
colorMode–––
filename–––
frames–––
height–––
layers–––
tags–––
width–––

No examples provided.

get_sprite_metadata ~25

Read the sprite's typed key/value metadata (Properties).

NameTypeReqDescription
file–––

No output schema declared.

No examples provided.

get_tilemap_info ~96

Read a tilemap layer: tile size, tileset length, and the cel's grid size, pixel position, and tile-index grid (``tiles`` as rows of columns, flip flags stripped; capped at 64x64 with ``truncated`` set). Read-only. Headless: pass ``file``.

NameTypeReqDescription
file–––
frameinteger––
layerstringyes–

No output schema declared.

No examples provided.

get_watched_changes ~39

Poll the change counter started by ``watch_changes`` (``reset=True`` zeroes it after reading).

NameTypeReqDescription
resetboolean––

No output schema declared.

No examples provided.

import_image_as_layer ~88

Import an external image file (PNG, etc.) into a new layer at (x, y) — a reference/trace layer for concept-art intake. One undo step. Headless: pass ``file``.

NameTypeReqDescription
file–––
image_pathstringyes–
layer_name–––
xinteger––
yinteger––

No output schema declared.

No examples provided.

import_spritesheet ~103

Slice a sheet PNG into animation frames: cells are read row-major at the given frame size onto a new "imported" layer, adding frames as needed. The sheet's dimensions must be exact multiples of the frame size. One undo step. Headless: pass ``file`` (the target sprite).

NameTypeReqDescription
file–––
frame_heightintegeryes–
frame_widthintegeryes–
sheet_pathstringyes–

No output schema declared.

No examples provided.

inbetween ~189

Fill in ``count`` frames between the key pose on ``from_frame`` and the one on the next frame, then return a picture of the result. Unlike ``tween_frames`` it handles a pose that changes shape: both poses slide toward each other and trade pixels through an ordered dither, so no new colors appear. ``smear`` makes the middle frame hold both poses at once, for fast moves. Other layers hold still. It's a first pass to draw over, not finished art. ``easing``: linear, ease_in, ease_out, or smoothstep. One undo step. Headless: pass ``file``.

NameTypeReqDescription
countinteger––
easingstring––
file–––
from_frameintegeryes–
layer–––
max_sizeinteger––
smearboolean––

No output schema declared.

No examples provided.

invert_colors ~28

Invert the active cel's RGB (alpha untouched). One undo step.

NameTypeReqDescription
file–––

No output schema declared.

No examples provided.

invert_selection ~23

Invert the current selection against the canvas bounds.

NameTypeReqDescription
file–––

No output schema declared.

No examples provided.

Install

How do I install the Aseprite Claude Connector MCP server?

Aseprite Claude Connector runs locally as a PyPI package, launched with uvx aseprite-claude-connector. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · aseprite-claude-connector

# add to Claude Code
claude mcp add umarmuhammad18-aseprite-claude-connector -- uvx aseprite-claude-connector
Common questions

What is the Aseprite Claude Connector MCP server?

Aseprite Claude Connector is an MCP server listed in the public MCP registry as io.github.UmarMuhammad18/aseprite-claude-connector. Let Claude draw in a running Aseprite, and export straight to Godot or Unity. This page covers its PyPI package (aseprite-claude-connector).

Is the Aseprite Claude Connector MCP server safe to use?

Aseprite Claude Connector scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Aseprite Claude Connector MCP server expose?

Aseprite Claude Connector exposes 187 tools: status, get_sprite_info, describe_sprite, get_pixel, set_sprite_metadata, and 182 more. Their descriptions and schemas cost roughly 18,843 tokens of context every time the server is loaded.

Is the Aseprite Claude Connector MCP server still maintained?

Aseprite Claude Connector is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Aseprite Claude Connector MCP server under?

Aseprite Claude Connector declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the Aseprite Claude Connector MCP server?

VerifyMCP ran 15 checks on Aseprite Claude Connector, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Aseprite Claude Connector: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.