Skip to main content
Glama
bauneAustin

aseprite_mcp

by bauneAustin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to aseprite_mcp

No user-submitted related servers found.

    Related Servers

    • 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

    • Aseprite-MCP

      iborymagic
      A
      license
      C
      quality
      D
      maintenance
      Enables AI assistants to automate Aseprite tasks such as sprite sheet export, frame extraction, and Lua scripting for sprite manipulation.
      21
      42 npm
      1
      MIT

    • aseprite-ai-artist

      with-pebbly
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to create and edit pixel art in a live Aseprite window, with tools for drawing, selection, transformation, and animation.
      18
      1
      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

    A3.5/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a distinct purpose: app control (launch_aseprite), project creation (create_project), animation (add_animation), drawing (draw_asset), preview (get_preview), and low-level scripting (run_script). No two tools overlap in their primary function, and run_script is clearly positioned as a general escape hatch.

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun pattern (run_script, launch_aseprite, create_project, add_animation, draw_asset, get_preview). This makes the API highly predictable and easy to navigate.

    Tool Count5/5

    Six tools is well-scoped for an Aseprite MCP server. Each tool covers a core operation without redundancy, staying within the ideal 3-15 range for a focused integration.

    Completeness2/5

    The tool surface lacks standard lifecycle operations such as opening an existing project, saving/exporting, and managing layers or palettes. While run_script can perhaps fill these gaps via custom Lua code, the explicit toolset is incomplete for typical Aseprite workflows.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources