Skip to main content
Glama
AlexPascu007

spriteloom-mcp

by AlexPascu007
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to spriteloom-mcp

No user-submitted related servers found.

    Related Servers

    • pixel-sprite

      MCPBytes
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables generating animated 32x32 character sprite sheets — with walk cycles, frame PNGs, looping GIFs, QA metadata and Godot/Unity exports — from a text prompt or reference image, running locally on an NVIDIA GPU or through a hosted cloud backend. It exposes a single create_pixel_sprite tool that writes the files to disk and returns enlarged previews so an MCP client can inspect and iterate on the result.
      46 PyPI
      2
      AGPL 3.0

    • mcpixel-studio

      chibivaru1225
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to create and edit pixel art and animations through a local-first editor, sharing the same project, editing commands, and undo history with the GUI.
      -

    • pixelsmith

      liamlz11
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that lets AI agents create, edit, and animate pixel-art sprites, with PNG previews after every step and support for export to GIF/APNG/spritesheets.
      47,127 npm
      MIT

    • PixelHand

      SirLichDevCraft
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to create and edit pixel-art projects — sprites, props, palettes, eight-direction animation, and tile-based environments — through a stdio MCP server with discovery, help, and call tools. Agents can build from silhouette to detail, inspect native-scale renders, silhouettes, value maps, and GIF playback, then save every change as versionable source.
      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.6/5.0

    Scored across 7 tools

    Disambiguation4/5

    Six of seven tools are cleanly separated by action: generate, edit, inpaint, rotate, list, stop, status. The main risk is edit_sprite vs rotate_sprite, since both take an existing image plus an instruction; the rotate description explicitly says it re-views rather than rotates pixels, which mitigates but does not eliminate the overlap.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern (generate_sprite, edit_sprite, inpaint_sprite, rotate_sprite, list_generations, stop_service). spriteloom_status breaks the pattern by being noun-first with a vendor prefix, a minor deviation within an otherwise predictable set.

    Tool Count5/5

    Seven tools is well-scoped for a sprite generation service: four generation/editing operations plus lifecycle and listing helpers. No tool appears redundant or superfluous.

    Completeness4/5

    Core lifecycle is covered: generate, modify (edit/inpaint/rotate), list, status, stop. Minor gaps exist — no delete/cleanup of generated outputs, no get-by-id detail fetch for a single generation, and no explicit service start — but these are workable around the filesystem.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources