Spine Pipeline MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SPINE_MCP_CLI | No | Optional absolute path to a licensed Spine CLI executable, used to enable spine_export. | |
| SPINE_MCP_CLI_VERSION | No | Optional Spine CLI version, for example 4.3.26. The skeleton's version must exactly match this configured CLI version. | |
| SPINE_MCP_SOURCE_ROOT | Yes | Absolute path to the source root containing Spine JSON assets. Required; source must already exist and must be separate from the staging root. | |
| SPINE_MCP_STAGING_ROOT | Yes | Absolute path to the staging root for generated jobs. Required; must be separate from the source root, and neither root may contain the other. | |
| SPINE_MCP_GODOT_EXECUTABLE | No | Optional absolute path to a Spine-enabled Godot executable, used to enable godot_validate. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| skeleton_inspectA | Inspect a Spine JSON in the configured read-only root; basic checks, not full validation. |
| stage_json_copyA | Copy one Spine JSON into a new isolated staging job. Never changes the source. |
| skeleton_validateB | Statically check bone references, mesh topology/weights and timeline times. Not a visual guarantee. |
| stage_asset_bundleB | Create an isolated JSON + referenced image bundle. No source writes. No audio/sequences. |
| job_validateB | Run static structural checks against a staged job, without changing it. |
| mesh_inspectA | Inventory skins/meshes, topology, continuity and weights. Supply exactly one source path or job ID. Static only. |
| mesh_weights_getB | Read up to 256 vertices with named bones, bone-local bind coordinates and weights from a staged mesh. |
| mesh_weights_setC | NEW job: updates=[{vertex:0,weights:{bone:1}}]. Replace existing bindings' weights, normalize/sort; retain bind x/y. Spine 4.3 only; no deform/linked meshes. Does not preserve pose. |
| mesh_replaceB | NEW job: replace uvs/triangles/vertices/hull (optional edges), preserving texture. Continuous geometry only; Spine 4.3; no deform/linked meshes. Weighted vertices need explicit bind coordinates. |
| mesh_policy_validateC | Check {rules:[{skin,slot,attachment,continuous?,max_vertices?,max_influences?,regions?}]}. Regions use vertices plus allowed_bones/rigid_bone/forbidden_ancestors. Static only. |
| animation_copyA | Copy an existing animation to a new name in a NEW staging job; refuses name collisions. |
| animation_retimeA | Return a new job with animation times divided by positive speed. Only linear/stepped; rejects Bezier. |
| bone_keys_setC | Replace one rotate/translate/scale timeline in a NEW job. Spine 4.3 rotate uses value. Linear/stepped only. |
| spine_exportC | Run explicitly configured licensed Spine CLI on another copy; produce project/JSON/atlas/PNG. Staging only. |
| godot_validateC | Use configured native Spine-enabled Godot in an isolated project. Runtime load/sample, not visual approval. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.