Skip to main content
Glama

Related Servers

Alternatives to sky-spine-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables an AI assistant to create, edit, validate and animate Esoteric Software Spine 2D skeletons without the editor running, covering bones, slots, attachments, skins, events, constraints, keyframes and reference-safe renames or deletions. When the Spine editor is installed, it also drives the official CLI to import skeleton JSON into a project and export runtime JSON/binary with atlases.
      26
      1
      MIT
    • F
      license
      A
      quality
      A
      maintenance
      Enables converting layered PSD or PhotoshopToSpine exports into validated Spine 2D rigs, animations, atlases, previews, runtime JSON, and optionally editable .spine projects. It provides MCP tools and an OpenAI/Codex workflow for rigging, animation generation, validation, preview auditing, and batch processing.
      14
      -
    • A
      license
      A
      quality
      D
      maintenance
      Local MCP server for automating Spine projects via the official CLI, enabling AI tools to inspect, export, import, and add animations to .spine files.
      16
      5 npm
      23
      Apache 2.0
    • F
      license
      B
      quality
      B
      maintenance
      Enables any MCP client to turn layered PSD artwork into game-ready Spine packages by inspecting and classifying layers, rigging with meshes, bones, weights, IK, physics and animation, applying procedural or After Effects-driven FX, and running runtime and mobile-budget validation with preview output. It finishes by exporting the final .spine, JSON and atlas assets so a model can drive a full art pipeline without hand-authoring rig data.
      49
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients to directly control Spine 3.8.75 animation workflows through 55 MCP tools, including reading projects, editing keyframes, manipulating skeletons, constraints, meshes, atlases, and rendering previews.
      42 npm
      19
      MIT

    TDQS

    A3.6/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct Spine operation: CLI info, export, packing, atlas summary, JSON summary, and asset validation. No two tools have overlapping purposes.

    Naming Consistency5/5

    All tools follow a consistent 'spine_verb_noun' pattern using snake_case, making it predictable and easy to understand the action and target.

    Tool Count5/5

    With 6 tools, the server is well-scoped for Spine-related tasks. Each tool serves a clear purpose without redundancy, and the count is appropriate for the domain.

    Completeness4/5

    The tool set covers core Spine workflows: info, export, packing, summarizing, and validation. Minor gaps like importing or running specific Spine commands are absent but not critical for typical use.