GPT Spine MCP
Related Servers
Alternatives to GPT Spine MCP
No user-submitted related servers found.
Related Servers
- FlicenseBqualityBmaintenanceEnables 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-
- AlicenseAqualityDmaintenanceAn 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.45MIT
- 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
- AlicenseNot gradedqualityDmaintenanceEnables 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.8MIT
- 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
TDQS
Scored across 14 tools
Most tools have clearly distinct purposes (inspect_source vs rig_and_animate vs apply_motion_spec vs pack_atlas). The main overlap is build_workflow, which subsumes rig_and_animate plus mesh/clip/export steps, so an agent may be unsure whether to use the atomic tool or the all-in-one pipeline. The validation trio (audit_preview, validate_motion, validate_output) is distinguishable by target but close enough to require care.
The set mostly follows a verb_noun snake_case pattern (inspect_source, rig_and_animate, apply_motion_spec, validate_motion, pack_atlas, make_project, export_project). A few deviations exist — spine_doctor and project_info are noun-first, while preview and batch are bare. Still readable and largely predictable.
14 tools for a full rig/animate/validate/export pipeline is reasonable and most earn their place as distinct pipeline stages. It sits at the higher end but does not feel redundant given the breadth of the workflow.
The surface covers the full lifecycle: environment check (spine_doctor), inspect, rig/animate, motion-spec authoring, mesh/IK/clip validation, atlas packing, editable project round-tripping (make_project/export_project/project_info), preview rendering, batch roster processing, and quality gating. No obvious dead ends.