Skip to main content
Glama
Sign In
sprite-agent-mcp

sprite-agent-mcp

by tiensdattnek-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to sprite-agent-mcp

No user-submitted related servers found.

    Related Servers

    • tenten

      debuffjp
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to create, edit, inspect, render, diff, preview, watch, and export indexed pixel-art sprites and animations as text grids through twelve MCP tools, including .tt and .aseprite import/export.
      55 npm
      1
      MIT

    • PixelHand

      SirLichDevCraft
      A
      license
      Not graded
      quality
      C
      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

    • 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.
      33 PyPI
      3
      AGPL 3.0

    • 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.
      48,326 npm
      MIT

    • libresprite-mcp

      vchopDev
      A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to generate and edit pixel art by driving LibreSprite headlessly through MCP tool calls, supporting operations like creating sprites, resizing canvases, and exporting PNGs.
      7
      BSD Zero Clause
    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 28 tools

    Disambiguation3/5

    Most tools have a clear resource+action target, but several clusters overlap: sprite_quickstart and sprite_policy both claim priority ('Call this FIRST' vs 'Read this before doing anything else'), sprite_preview / sprite_inspect / sprite_critique / sprite_gallery all cover 'look at the art', and sprite_loop / sprite_animate / sprite_tween / sprite_timing all manipulate the timeline. sprite_enhance also duplicates outline/shade operations that sprite_draw_ops exposes directly. Descriptions are detailed enough to resolve most cases, but the boundaries require reading rather than being self-evident from names.

    Naming Consistency4/5

    Nearly every tool follows the sprite_<verb>_<noun> or sprite_<verb> convention in consistent snake_case, e.g. sprite_new_project, sprite_load_project, sprite_list_projects, sprite_draw_grid. Minor deviations are noun-only multi-action tools (sprite_palette, sprite_layer, sprite_frame, sprite_timing) that bundle several verbs into one name, but the prefix scheme remains predictable throughout.

    Tool Count2/5

    At 28 tools the surface is heavy for essentially one asset domain, and several tools are near-duplicates that could be merged (sprite_list_palettes into sprite_palette, sprite_timing/sprite_loop into a frame-timing op, sprite_gallery into sprite_export). The discovery trio sprite_quickstart / sprite_policy / sprite_catalog plus sprite_verify_integrity further inflates the count beyond what the creative workflow needs.

    Completeness4/5

    Coverage is genuinely broad: project lifecycle (new/list/info/select/delete/save/load), drawing (grid and vector ops), frame and animation control, palettes, critique/inspect/preview, and many export formats. The main gaps are no undo/redo or history tool and no canvas resize/import operation, both of which an agent doing iterative pixel art would reasonably expect.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing

    Resources