Skip to main content
Glama

sky-spine-mcp

中文 | English

sky-spine-mcp 是一个面向 Spine 资源流水线的 MCP Server,用来通过 Spine 官方命令行工具自动执行导出、纹理打包、资源检查和文件摘要等任务。

它适合接入 Codex、Claude Desktop 或其他支持 MCP 的客户端,让 AI 可以在本地项目中调用 Spine CLI,完成常见的批处理工作。

本项目目前专注于文件级自动化:

  • 导出 .spine 项目或 Spine 数据文件

  • 打包纹理图集

  • 查看 Spine CLI 信息输出

  • 汇总导出的 JSON 与 atlas 文件

  • 检查运行时资源目录是否完整

它不是 Spine 编辑器脚本 API,不能直接在 Spine UI 内创建骨骼、权重或关键帧。当前更可靠的自动化边界是通过 Spine CLI 处理项目文件、导出文件和图集资源。

环境要求

  • Node.js 20 或更高版本

  • 已授权的 Spine 安装

  • 可执行的 Spine CLI,例如 Spine、Spine.com、Spine.exe、Spine.sh,或通过 SPINE_CLI_PATH 指定路径

在 Windows 上,Spine 官方推荐使用 Spine.com,因为它会等待 Spine 退出,并把输出写到控制台。

Related MCP server: GPT Spine MCP

安装

npm install
npm run build

运行

$env:SPINE_CLI_PATH="C:\Program Files\Spine\Spine.com"
npm start

MCP 客户端配置

本地 MCP 配置示例:

{
  "mcpServers": {
    "sky-spine-mcp": {
      "command": "node",
      "args": ["D:/AIWorkSpace/GithubTool/sky-spine-mcp/dist/index.js"],
      "env": {
        "SPINE_CLI_PATH": "C:/Program Files/Spine/Spine.com"
      }
    }
  }
}

工具

spine_cli_info

运行 Spine CLI 信息命令:

Spine -i <path>

spine_export

导出 Spine 项目或数据文件:

Spine -i <project.spine> -o <output> -e <export.json>

exportSettings 也可以使用 json、binary、json+pack 或 binary+pack。

spine_pack

打包图片目录为 Spine 纹理图集:

Spine -i <images> -o <output> -p <pack.json-or-atlas-name>

spine_summarize_json

读取导出的 Spine JSON,返回 skeleton 元数据、数量统计、skins 和 animations。

spine_summarize_atlas

读取 .atlas 文件,返回图集页和 region 数量。

spine_validate_assets

扫描目录中的 .json/.skel、.atlas 和图片资源,检查运行时资源是否齐全。

开发

npm run dev
npm run build

说明

Spine CLI 参数行为可能随编辑器版本变化。如果命令因为启动器不识别新参数而失败,请更新 Spine launcher,或使用 Spine 官方文档中对应版本支持的 CLI 参数。

许可证

MIT

English

MCP server for automating common Spine asset pipeline tasks through the official Spine command line interface.

This project focuses on practical file-level automation:

  • export Spine projects or data files

  • pack texture atlases

  • inspect Spine CLI info output

  • summarize exported JSON and atlas files

  • validate runtime asset folders

It does not provide an editor scripting API for creating bones, weights, or keyframes inside the Spine UI. Spine currently exposes the reliable automation surface for these workflows through its CLI.

Requirements

  • Node.js 20 or newer

  • A licensed Spine installation

  • Spine CLI available as Spine, Spine.com, Spine.exe, Spine.sh, or configured with SPINE_CLI_PATH

On Windows, Spine's documentation recommends the command line executable Spine.com because it waits for Spine to exit and writes output to the console.

Install

npm install
npm run build

Run

$env:SPINE_CLI_PATH="C:\Program Files\Spine\Spine.com"
npm start

MCP Client Configuration

Example local MCP config:

{
  "mcpServers": {
    "sky-spine-mcp": {
      "command": "node",
      "args": ["D:/AIWorkSpace/GithubTool/sky-spine-mcp/dist/index.js"],
      "env": {
        "SPINE_CLI_PATH": "C:/Program Files/Spine/Spine.com"
      }
    }
  }
}

Tools

spine_cli_info

Runs Spine CLI info:

Spine -i <path>

spine_export

Exports a Spine project or data file:

Spine -i <project.spine> -o <output> -e <export.json>

exportSettings can also be json, binary, json+pack, or binary+pack.

spine_pack

Packs a folder of images:

Spine -i <images> -o <output> -p <pack.json-or-atlas-name>

spine_summarize_json

Reads exported Spine JSON and returns skeleton metadata, counts, skins, and animations.

spine_summarize_atlas

Reads a .atlas file and returns atlas page and region counts.

spine_validate_assets

Scans a folder for .json/.skel, .atlas, and page image files.

Development

npm run dev
npm run build

Notes

Spine CLI parameter behavior can vary by editor version. If a command fails because the launcher rejects a newer parameter, update the Spine launcher or use the CLI option documented by Spine for unknown parameters.

License

MIT

Available Tools

6 tools
spine_cli_infoSpine CLI infoC

Run Spine CLI info for a project, folder, JSON, or binary skeleton file.

Inputs: inputPath (required), spinePath, timeoutMs.

spine_exportSpine exportB

Export a Spine project or data file with an export settings JSON file or default json/binary mode.

Inputs: exportSettings (required), clean, inputPath, spinePath, +3 more.

spine_packSpine texture packB

Pack image folders into a Spine texture atlas using default settings or a pack settings JSON file.

Inputs: pack (required), inputPath (required), outputPath (required), name, +4 more.

spine_summarize_atlasSummarize Spine atlasA

Read a Spine .atlas file and return page and region counts.

Inputs: atlasPath (required).

spine_summarize_jsonSummarize Spine JSONA

Read exported Spine JSON and return skeleton metadata, counts, skins, and animations.

Inputs: jsonPath (required).

spine_validate_assetsValidate Spine assetsC

Check whether a folder contains expected Spine runtime assets.

Inputs: folderPath (required), requireAtlas, requireImages.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.6/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct Spine operation: CLI info, export, packing, atlas summary, JSON summary, and asset validation. No two tools have overlapping purposes.

    Naming Consistency5/5

    All tools follow a consistent 'spine_verb_noun' pattern using snake_case, making it predictable and easy to understand the action and target.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Local MCP server for automating Spine projects via the official CLI, enabling AI tools to inspect, export, import, and add animations to .spine files.
      16
      16 npm
      25
      Apache 2.0
    • F
      license
      A
      quality
      B
      maintenance
      Enables 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
      -
    • F
      license
      B
      quality
      B
      maintenance
      Enables 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
      -
    • A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      26
      1
      MIT