Skip to main content
Glama
Sign In
spine-anim-mcp

spine-anim-mcp

by K-ulucay
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to spine-anim-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
      23
      Apache 2.0

    • GPT Spine MCP

      kumikilongyeyo
      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
      -

    • ART-PIPELINE-MCP

      kumikilongyeyo
      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
      -
    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

    A4.1/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: importing PSDs, listing animation types, describing parameters, and adding animations to existing skeletons. No overlap in functionality.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with underscores (animate_existing, describe_animation_type, import_psd_to_spine, list_animation_types), making them predictable.

    Tool Count5/5

    With 4 tools, the server is well-scoped for its domain (Spine procedural animations). Each tool earns its place, covering essential operations without excess.

    Completeness4/5

    The tool set covers the core workflows: project creation, animation type discovery, parameter lookup, and application. A minor gap is the lack of an update/delete tool for animations, but the surface is sufficient for the stated purpose.

    Resources