Skip to main content
Glama
rafidaaziz23

Aseprite MCP Server

by rafidaaziz23
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Aseprite MCP Server

No user-submitted related servers found.

    Related Servers

    • Pixel Art AI

      stereomp3
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to create, draw, and refine Aseprite documents through deterministic canvas, layer, frame, tag, and palette tools, with pixel analyzers, style validation, and preview/diff visual feedback. It also supports spritesheet and animated GIF export, producing multi-layer game-ready assets.
      1
      MIT

    • Aseprite MCP Tools

      midarikawa
      A
      license
      B
      quality
      C
      maintenance
      Enables AI assistants to create and edit pixel art and animated sprites in Aseprite through 104 tools covering drawing, layers, animation, palettes, tilemaps, exports, visual analysis, and raw Lua scripting.
      116
      MIT

    • aseprite-mcp

      VukasinTheProgrammer
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to drive Aseprite for pixel-art creation, including sprite setup, grid-based drawing, layer/frame/tag management, reference image import, and export, with rendered previews after every mutation.
      MIT

    • mnehmos.aseprite.mcp

      Mnehmos
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to create, inspect, edit, and export pixel art, sprites, animations, and spritesheets using headless Aseprite, and to convert arbitrary images into indexed pixel art.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools have clearly distinct resource+action targets, but aseprite_run_lua and aseprite_run_pipeline both execute workflows and could be confused, and aseprite_analyze_style partially overlaps palette/inspection concerns of aseprite_apply_palette and aseprite_inspect_sprite.

    Naming Consistency5/5

    Every tool uses the aseprite_ prefix with a consistent verb_noun pattern (create_sprite, draw_pixels, apply_palette, export_spritesheet, inspect_sprite, run_lua), making the set highly predictable.

    Tool Count5/5

    12 tools is a well-scoped size for a sprite-editing server, covering distinct phases (info, create, draw, animate, palette, export, inspect) without obvious redundancy.

    Completeness4/5

    Core pixel-art lifecycle is covered from creation through drawing, animation, palette, export, and inspection, but there are gaps in editing existing sprites (e.g. add/remove layers or frames, delete/resize operations) that could create dead ends for iterative workflows.

    Resources