sky-spine-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SPINE_CLI_PATH | No | Path to the Spine CLI executable. If not set, the server will look for Spine, Spine.com, Spine.exe, or Spine.sh in the system PATH. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| spine_cli_infoC | Run Spine CLI info for a project, folder, JSON, or binary skeleton file. |
| spine_exportB | Export a Spine project or data file with an export settings JSON file or default json/binary mode. |
| spine_packB | Pack image folders into a Spine texture atlas using default settings or a pack settings JSON file. |
| spine_summarize_jsonA | Read exported Spine JSON and return skeleton metadata, counts, skins, and animations. |
| spine_summarize_atlasA | Read a Spine .atlas file and return page and region counts. |
| spine_validate_assetsC | Check whether a folder contains expected Spine runtime assets. |
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 6 tools
Each tool targets a distinct Spine operation: CLI info, export, packing, atlas summary, JSON summary, and asset validation. No two tools have overlapping purposes.
All tools follow a consistent 'spine_verb_noun' pattern using snake_case, making it predictable and easy to understand the action and target.
With 6 tools, the server is well-scoped for Spine-related tasks. Each tool serves a clear purpose without redundancy, and the count is appropriate for the domain.
The tool set covers core Spine workflows: info, export, packing, summarizing, and validation. Minor gaps like importing or running specific Spine commands are absent but not critical for typical use.