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 (14 hours ago)

Scores higher than 76% 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
set_cel_opacity ~43

Set the cel's opacity (0-255).

NameTypeReqDescription
file–––
frame–––
layer–––
opacityintegeryes–

No output schema declared.

No examples provided.

set_cel_position ~52

Move the cel's top-left origin to (x, y).

NameTypeReqDescription
file–––
frame–––
layer–––
xintegeryes–
yintegeryes–

No output schema declared.

No examples provided.

set_color_mode ~83

Convert the sprite between rgb | gray | indexed color modes. ``dithering`` applies only when converting to indexed: ordered | old | error-diffusion (default none). Returns the old and new mode. One undo step. Headless: pass ``file``.

NameTypeReqDescription
dithering–––
file–––
modestringyes–

No output schema declared.

No examples provided.

set_editor_view ~63

Live editor only: set the viewport zoom (1.0 = 100%) and/or scroll — e.g. zoom to the region you're about to edit so the artist can watch.

NameTypeReqDescription
scroll_x–––
scroll_y–––
zoom–––

No output schema declared.

No examples provided.

set_frame_duration ~39

Set frame ``number``'s duration in milliseconds.

NameTypeReqDescription
file–––
msintegeryes–
numberintegeryes–

No output schema declared.

No examples provided.

set_frame_durations ~55

Set every frame in [from_frame..to_frame] to ``ms`` milliseconds.

NameTypeReqDescription
file–––
from_frameintegeryes–
msintegeryes–
to_frameintegeryes–

No output schema declared.

No examples provided.

set_layer_blend_mode ~88

Set a layer's blend mode. One of: normal, multiply, screen, overlay, darken, lighten, color_dodge, color_burn, hard_light, soft_light, difference, exclusion, hue, saturation, color, luminosity, addition, subtract, divide.

NameTypeReqDescription
file–––
modestringyes–
namestringyes–

No output schema declared.

No examples provided.

set_layer_opacity ~39

Set a layer's opacity (0-255).

NameTypeReqDescription
file–––
namestringyes–
opacityintegeryes–

No output schema declared.

No examples provided.

set_layer_visibility ~34

Show or hide a layer.

NameTypeReqDescription
file–––
namestringyes–
visiblebooleanyes–

No output schema declared.

No examples provided.

set_onion_skin ~109

Configure the editor's onion-skin view: on/off, ghost counts each direction, and whether ghosting stays inside the current tag. A view preference — visually meaningful in the live editor. (For a rendered onion-skin image any backend can produce, use ``render_onion_composite``.)

NameTypeReqDescription
activebooleanyes–
file–––
loop_tag–––
next_framesinteger––
prev_framesinteger––

No output schema declared.

No examples provided.

set_palette ~41

Replace the whole palette with ``colors`` (list of #rrggbb/#rrggbbaa).

NameTypeReqDescription
colorsarrayyes–
file–––

No output schema declared.

No examples provided.

set_palette_color ~49

Set palette entry ``index`` to ``color`` (#rrggbb or #rrggbbaa).

NameTypeReqDescription
colorstringyes–
file–––
indexintegeryes–

No output schema declared.

No examples provided.

set_safety_rails ~130

Set the safety rails for this session, or pass nothing to read them. ``dry_run`` true makes every edit report what it would change, as an error, then roll back; tools that save, export, or run raw Lua refuse instead. ``max_changed_pixels`` caps what one call can change, and an edit over it is rolled back; 0 removes the cap. It counts hidden layers. ``move_layer`` isn't capped, and ``run_lua`` is capped only with ``edit=true``.

NameTypeReqDescription
dry_run–––
max_changed_pixels–––

No output schema declared.

No examples provided.

set_slice_center ~79

Set a slice's 9-patch stretchable center rectangle (relative to the slice). One undo step. Headless: pass ``file``.

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

No output schema declared.

No examples provided.

set_slice_pivot ~87

Set a slice's pivot point, in pixels relative to the slice's top-left. This pivot is exported into the Unity ``.meta`` by export_unity_slices. One undo step. Headless: pass ``file``.

NameTypeReqDescription
file–––
namestringyes–
pivot_xintegeryes–
pivot_yintegeryes–

No output schema declared.

No examples provided.

set_sprite_metadata ~77

Attach typed key/value metadata to the sprite (Aseprite's Properties system — stored in the .aseprite file itself). Values may be strings, numbers, or booleans. Useful for provenance ("generated_by", spec IDs) and pipeline state. One undo step.

NameTypeReqDescription
entriesobjectyes–
file–––

No output schema declared.

No examples provided.

set_symmetry ~85

Live editor only: set mirror-painting symmetry — ``mode`` is ``none``, ``horizontal`` (mirror across a vertical axis), ``vertical``, or ``both``; optionally place the axis lines. Affects the artist's subsequent brush strokes.

NameTypeReqDescription
modestringyes–
x_axis–––
y_axis–––

No output schema declared.

No examples provided.

set_tag_color ~63

Set the timeline label color of the tag ``name`` (#rrggbb or #rrggbbaa). One undo step. Headless: pass ``file``.

NameTypeReqDescription
colorstringyes–
file–––
namestringyes–

No output schema declared.

No examples provided.

set_tag_direction ~62

Set the playback direction of the tag ``name``: forward | reverse | pingpong | pingpong_reverse. One undo step. Headless: pass ``file``.

NameTypeReqDescription
directionstringyes–
file–––
namestringyes–

No output schema declared.

No examples provided.

set_tag_range ~83

Move the tag ``name`` to span frames ``from_frame``..``to_frame`` (1-based, inclusive; validated against the sprite's frame count). One undo step. Headless: pass ``file``.

NameTypeReqDescription
file–––
from_frameintegeryes–
namestringyes–
to_frameintegeryes–

No output schema declared.

No examples provided.

set_tiles ~113

Place tile references on a tilemap layer's cel. ``tiles`` is a list of {column, row, index} objects (0-based grid cells; index 0 erases to the empty tile). The cel is created or grown as needed, anchored at the sprite origin. ``frame`` is 1-based. One undo step. Headless: pass ``file``.

NameTypeReqDescription
file–––
frameintegeryes–
layerstringyes–
tilesarrayyes–

No output schema declared.

No examples provided.

sharpen ~67

Sharpen the active cel (unsharp mask over a 3x3 neighborhood). ``strength`` 0.1-2.0. Only opaque pixels are considered, so sprite edges don't halo against transparency. One undo step.

NameTypeReqDescription
file–––
strengthnumber––

No output schema declared.

No examples provided.

show_choice_dialog ~79

Live editor only: pop a small dialog IN Aseprite with a message and up to 4 option buttons (e.g. approve/redo). Non-blocking — call ``get_dialog_choice`` to collect the artist's pick.

NameTypeReqDescription
messagestringyes–
optionsarrayyes–
titlestring––

No output schema declared.

No examples provided.

smear_frame ~83

Append a motion-smear frame blending ``from_frame`` and ``to_frame``: overlapping pixels averaged, single-frame areas ghosted at half alpha — a pixel-content smear. RGB sprite only. Headless: pass ``file``.

NameTypeReqDescription
file–––
from_frameintegeryes–
layer–––
to_frameintegeryes–

No output schema declared.

No examples provided.

sort_palette ~86

Reorder palette swatches by ``luminance`` (default), ``hue``, or ``saturation``. Intended for RGB sprites' swatch organization — on an INDEXED sprite this changes which color each pixel shows (indices aren't remapped). One undo step.

NameTypeReqDescription
ascendingboolean––
bystring––
file–––

No output schema declared.

No examples provided.

split_into_layers ~221

Separate a picture into parts on their own layers, like armour and meadow, so each can be edited or animated alone. ``seeds`` are points on each part: ``[{"name": "armour", "x": 90, "y": 40}, {"name": "meadow", "x": 5, "y": 5}]``. The first part named ends up on top. Each part grows from its seeds and stops where colours change sharply, so put a seed on every distinct area of a part (a part may have many seeds). If a part leaks into another, add seeds where it leaked and run it again. ``layer`` defaults to the active one, which is hidden afterwards unless ``hide_source`` is false. Check the result with ``look`` and ``layer=``. One undo step. Headless: pass ``file``.

NameTypeReqDescription
file–––
frame–––
hide_sourceboolean––
layer–––
seedsarrayyes–

No output schema declared.

No examples provided.

split_sheet ~249

Cut a character sheet (poses in a ``columns`` x ``rows`` grid) into one pixel-art sprite per pose, all at the same scale and on ONE shared palette of ``colors`` colours (or ``palette``), so the poses stay consistent with each other. Each cell is shrunk to ``width`` x ``height`` (the cell's aspect by default), its background cleared and the bits of neighbouring poses dropped. Each sprite gets a tag named from ``names`` (row by row; "pose_1"... by default), so ``pin_sprite(tag=...)`` can pick it. Live: opens the sprites in the editor. Headless: writes ``<out_dir>/<name>.aseprite``.

NameTypeReqDescription
clear_edgesboolean––
colorsinteger––
columnsintegeryes–
ditherstring––
height–––
image_pathstringyes–
layer_namestring––
names–––
out_dir–––
palette–––
remove_backgroundboolean––
rowsintegeryes–
widthintegeryes–

No output schema declared.

No examples provided.

start_recording ~92

Start recording this session: a picture of the active frame is kept after every edit, for ``stop_recording`` to turn into a GIF timelapse. Each picture is one more read of the sprite, so edits run a little slower while it's on. Starting again throws away what's recorded. Headless: pass ``file``.

NameTypeReqDescription
file–––
max_framesinteger––

No output schema declared.

No examples provided.

status ~50

Report backend health plus this server's version and whether a newer release exists. Live: whether Aseprite is connected + its version. Headless: the resolved Aseprite executable path and whether it exists.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

stop_recording ~92

Stop recording and write the timelapse GIF to ``out_path``. It's zoomed with sharp pixels to fit ``max_size``, and the final picture holds for a beat before it loops. Larger GIFs take longer to encode, so raise ``max_size`` with care.

NameTypeReqDescription
frame_msinteger––
max_sizeinteger––
out_pathstringyes–

No output schema declared.

No examples provided.

stop_watching_changes ~19

Detach the ``watch_changes`` listener.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

swing_part ~239

Swing a wing, arm, tail or ear about its joint across frames. ``outline`` is a polygon round the part, in canvas pixels ``[[x, y], ...]``; keep it to the part itself (not the face or chest beside it). ``pivot`` is the joint. ``keys``, one per frame (frames are made as needed): ``{"frame": 2, "angle": 10, "dx": 0, "dy": -1, "ms": 90}``, angle in degrees clockwise. Where the part met the body, a ``band`` of ``shadow`` (the part's darkest colour by default) stays underneath, so turning never opens a gap, and the part's light outer halo is dropped so it doesn't streak. Small angles (up to about 15) look best. One undo step. Headless: pass ``file``.

NameTypeReqDescription
bandinteger––
file–––
keysarrayyes–
layer–––
outlinearrayyes–
pivotarrayyes–
shadow–––

No output schema declared.

No examples provided.

tween_cel_opacity ~121

Fade a layer's cels across [from_frame..to_frame]: opacity interpolates from ``from_opacity`` to ``to_opacity`` (0-255) with the chosen easing. Every frame in the range needs a cel on the layer. One undo step.

NameTypeReqDescription
easingstring––
file–––
from_frameintegeryes–
from_opacityintegeryes–
layer–––
to_frameintegeryes–
to_opacityintegeryes–

No output schema declared.

No examples provided.

tween_frames ~152

Insert ``count`` in-between frames between ``from_frame`` and ``to_frame`` that slide the start frame's art toward where the end frame's art sits, so it works for moved cels and for art redrawn in a new place. It moves the art without reshaping it, and refuses if the art hasn't moved. ``easing``: linear, ease_in, ease_out, or smoothstep. Check the result with ``look_animation``. Headless: pass ``file``.

NameTypeReqDescription
countinteger––
easingstring––
file–––
from_frameintegeryes–
layer–––
to_frameintegeryes–

No output schema declared.

No examples provided.

undo ~24

Undo the last edit on the active sprite (live editor).

NameTypeReqDescription
file–––

No output schema declared.

No examples provided.

walk_cycle_template ~186

Lay down a timed, tagged walk or run skeleton to draw over. It adds ``frames`` frames (an even number, 4-16), or uses the sprite if it's a blank single frame, with a locked faded guide layer and an empty art layer above it, which it leaves active. The near limbs are light blue and the far limbs dark blue. Feet travel backward on the ground and swing forward through the air, so the cycle walks forward; the figure stays in place, ready for scrolling scenery or game movement. Check it with ``look_animation``, then hide or delete the guide. One undo step. Headless: pass ``file``.

NameTypeReqDescription
body_heightintegeryes–
facingstring––
file–––
framesinteger––
gaitstring––
tag–––

No output schema declared.

No examples provided.

watch_changes ~59

Live editor only: start counting edits the ARTIST makes to the active sprite (via ``Sprite.events``). Poll with ``get_watched_changes`` — e.g. wait for the artist to finish touching up, then re-run the QA sweep.

Input schema present but exposes no named parameters.

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.