Spine Pipeline MCP
Related Servers
Alternatives to Spine Pipeline MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables AI-assisted inspection and editing of Spine 4.3 animation projects, including generating simple motion drafts, adjusting keyframes per track, previewing results, and importing and validating changes through the official CLI. It also supports low-context tool sets for animation workflows.15MIT
- AlicenseAqualityCmaintenanceEnables 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.261MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to drive the Spine 2D animation editor: export, import, texture pack and unpack, repair generated skeleton JSON, and merge rigged characters into a single scene with a layout preview. Every tool returns a structured result with an ok flag so agents can branch on outcomes instead of parsing console output.MIT
- FlicenseAqualityBmaintenanceEnables 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-
- AlicenseBqualityBmaintenanceThis server enables AI agents to read, measure, view, and safely edit Spine 4.3 animations by bridging the gap between creative artistic decisions and technical requirements. It facilitates a comprehensive animation pipeline, ensuring all changes are verified, backed up, and ready for deployment across various rendering environments.3816 npmMIT
- AlicenseBqualityBmaintenanceEnables AI clients to control background Blender jobs over stdio so they can inspect a 3D character or companion model, calibrate its anatomy and named bones, bake and export animation, and numerically verify the persisted GLB for playback review. Includes a CLI, models and workspaces that stay local unless explicitly shared.9MIT
TDQS
Scored across 15 tools
The set contains four validation-flavored tools (job_validate, skeleton_validate, mesh_policy_validate, godot_validate) and two inspection tools (mesh_inspect, skeleton_inspect) whose boundaries are only partially clarified by the descriptions. mesh_inspect vs skeleton_inspect vs skeleton_validate overlap substantially (both inventory meshes/weights and topology), and an agent may pick the wrong one. The descriptions do differentiate them somewhat (static vs runtime, policy vs structural), keeping it above the low band.
Most tools follow a clear resource_action pattern (job_validate, mesh_inspect, skeleton_validate, animation_copy, bone_keys_set, spine_export, godot_validate). The two stage_* tools (stage_json_copy, stage_asset_bundle) invert to verb_noun, a minor deviation. Overall predictable and readable.
15 tools sits at the top of the well-scoped band and covers a genuinely multi-stage pipeline (stage, inspect, validate, edit, export, runtime-check). A couple of the validation/ inspection tools could plausibly be merged, but none feel like pure filler. The count is defensible for the domain's breadth.
The core lifecycle is covered: stage source, inspect, validate, mutate weights/mesh/animations/bone keys, export, and runtime-verify in Godot. Gaps are moderate rather than fatal: there is no job listing/status or staging-job delete/cleanup, and no tool to create slots/attachments or inspect atlases/textures. Agents can work around these but lifecycle cleanup is a dead end.