Skip to main content
Glama
yb901104-wq

spine-mcp

by yb901104-wq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to 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
      6 npm
      13
      Apache 2.0

    • 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
      1
      MIT

    • 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.
      43 npm
      5
      MIT

    • effekseer-ai

      laodeng000
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for creating and editing Effekseer effects with AI agents. It provides tools to manage effect documents, nodes, properties, resources, and curves via stdio.
      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.
      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

    B3.3/5.0

    Scored across 36 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose, covering different aspects of Spine animation editing (getting info, modifying keyframes, managing animations, preview, validation). Even similar-sounding tools like get_animations, get_animation_sheet, and get_animation_timelines serve different granularities of data.

    Naming Consistency5/5

    All tools follow a consistent 'spine_verb_noun' pattern (e.g., spine_get_animations, spine_set_bone_keyframe, spine_delete_animation). No mixing of camelCase or inconsistent verb forms.

    Tool Count2/5

    With 36 tools, the count exceeds the 25+ threshold defined as 'too many.' While the tools are detailed and cover a complex domain, the number is high for typical MCP server usage and may overwhelm agents.

    Completeness5/5

    The tool set covers the full lifecycle of Spine animation work: creation, cloning, deletion, keyframe manipulation, pose application, preview, validation, backup, and runtime checking. No obvious gaps in core functionality.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources