Skip to main content
Glama
claudeskydream-hash

sky-spine-mcp

by claudeskydream-hash
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to sky-spine-mcp

No user-submitted related servers found.

    Related Servers

    • spine-mcp

      1425sd
      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
      13 npm
      12
      Apache 2.0

    • Spine MCP Server

      zhoushengmin
      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.
      33 npm
      4
      MIT

    • Spine Motion MCP

      nihatcagri44
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables authoring, preview, and export of Spine 2D skeletal animations via natural language from Claude Code or any MCP client, with a web dashboard and tools for keyframing, templates, and GIF preview.
      3
      MIT

    • spine-mcp

      yb901104-wq
      F
      license
      B
      quality
      D
      maintenance
      MCP server for reading, validating, and modifying Spine 4.1.24 JSON animation files, with tools for animation timeline editing, validation, preview, and agent integration.
      36
      -

    • spine-anim-mcp

      K-ulucay
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that converts layered PSD characters into Spine 4.2 rigs with deterministic, parametric 2D/2.5D animations (idle, walk, run, jump, attack, hit) ready for the Spine editor and Unity.
      4
      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 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.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources