spine-anim-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_animation_typesA | List the procedural animation types this server can generate. |
| describe_animation_typeA | Return the tunable parameters and defaults for one animation type. |
| import_psd_to_spineA | Convert a layered PSD into a Spine 4.2 project and generate animations. psd_path: path to a .psd whose layers are named after body roles (head, torso, arm_left, leg_right, ...). animations: list of {type, name?, params?}. If omitted, generates a default set: idle + walk. Returns JSON with project_path, atlas_path, png_path, animations. |
| animate_existingA | Add procedural animations to an EXISTING Spine 4.2 skeleton JSON. The skeleton's bones are auto-mapped to canonical roles by name. Bones whose names already follow the role convention (head, leg_upper_left, ...) map directly; others are ignored by the generators. Returns JSON with the updated project path and the animations added. |
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 4 tools
Each tool has a clearly distinct purpose: importing PSDs, listing animation types, describing parameters, and adding animations to existing skeletons. No overlap in functionality.
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.
With 4 tools, the server is well-scoped for its domain (Spine procedural animations). Each tool earns its place, covering essential operations without excess.
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.