Skip to main content
Glama
Sign In
aseprite-mcp

aseprite-mcp

by Ryan3719
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to aseprite-mcp

No user-submitted related servers found.

    Related Servers

    • aseprite-mcp

      MaxPanRa
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for safe local automation of Aseprite, providing tools to create, inspect, edit, save, and export pixel art documents through the official Aseprite CLI and controlled Lua scripts.
      109 npm
      MIT

    • aseprite-mcp

      letsagents
      A
      license
      Not graded
      quality
      C
      maintenance
      A TypeScript MCP server that exposes Aseprite to LLM clients as 76 tools for drawing, layers, frames, palettes, and more by generating Lua scripts and running Aseprite headlessly.
      44 npm
      MIT

    • Aseprite MCP Tools

      ext-sakamoro
      A
      license
      A
      quality
      D
      maintenance
      A Python MCP server enabling programmatic interaction with Aseprite for pixel art creation and manipulation with features like drawing operations, palette management, and batch processing.
      19
      27
      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 8 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: status, listing commands, command sequences, raw CLI, Lua, create, export, info. However, aseprite_cli overlaps with many others since it can perform any of those actions, and aseprite_command_sequence and aseprite_run_lua both execute Lua, creating some ambiguity.

    Naming Consistency3/5

    All tools share the aseprite_ prefix and use snake_case, but the pattern is mixed: some are verb_noun (list_commands, run_lua, create_sprite), some are noun-only (status, cli), and others are noun_noun (command_sequence, sprite_info). This inconsistency reduces predictability, though names remain readable.

    Tool Count5/5

    8 tools is well within the ideal 3-15 range and appropriate for covering Aseprite's main capabilities: status, command introspection, execution, scripting, creation, export, and metadata. Each tool earns its place without bloat.

    Completeness4/5

    Core workflows are well covered: create, export, inspect, run commands/scripts, and get config. Minor gaps exist, such as no high-level edit/modify tool, but aseprite_run_lua and aseprite_cli provide escape hatches for any missing operations, making the surface reasonably complete.

    Resources