Skip to main content
Glama
yafeiaa

Piskel MCP Server

by yafeiaa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Piskel MCP Server

No user-submitted related servers found.

    Related Servers

    • pixel-mcp

      ehm-93
      A
      license
      B
      quality
      C
      maintenance
      Enables LLMs to create and edit pixel art reliably with support for layers, frames, symmetry, and various drawing tools.
      70
      MIT No Attribution

    • 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

    • 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

    • 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

    • 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
    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.2/5.0

    Scored across 22 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no significant overlap. Drawing tools (draw_circle, draw_line, draw_pixel, draw_pixels, draw_rectangle, fill_area) target specific shapes, while project management (create_project, delete_project, list_projects), layer/frame operations (add_layer, remove_layer, add_frame, duplicate_frame, remove_frame, clear_frame), and export functions (export_gif, export_png, export_sprite_sheet) are well-separated. The data retrieval tools (get_frame_data, get_pixel, get_project_info) also serve unique roles.

    Naming Consistency5/5

    Tool names follow a consistent verb_noun pattern throughout, using snake_case exclusively. All names clearly indicate the action (add, create, delete, draw, duplicate, erase, export, get, list, remove) followed by the target object, making them predictable and readable. There are no deviations in naming conventions.

    Tool Count4/5

    With 22 tools, the count is slightly high but reasonable for a pixel art editor covering project management, drawing, layer/frame manipulation, export, and data retrieval. It feels comprehensive rather than bloated, though it borders on the upper limit of typical scoping (3-15 tools). Each tool appears to earn its place without obvious redundancy.

    Completeness5/5

    The tool set provides complete coverage for a pixel art editor domain. It includes project CRUD (create, delete, list, get info), drawing operations (various shapes and tools), layer and frame management (add, remove, duplicate, clear), export formats (GIF, PNG, sprite sheet), and data access (pixel and frame data). There are no apparent gaps that would hinder agent workflows for core pixel art creation and editing tasks.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources