页:1

GitHub 默认显示此英文 [[T0]. 中文版以README.zh-CN.md保持.

Windows上的斯宾通自动化本地MCP服务器. 它只呼叫官方斯宾克CLI,并在stdio上进行交流,因此克洛德代码, Codex, Cursor等AI工具可以在当地启动.

此服务器不进行UI自动化,AutoHotkey,鼠标或键盘模拟,时间表操作,网格绑定,骨重编辑,或直接[T2]内部修改. 它只通过官方斯宾克CLI修改了.spine文件.

□ 要求

• 视窗
• 20多号节点
• 当地安装了斯宾普 这种MCP不包括斯宾克,不能在没有本地斯宾克安装的情况下运行.
• 斯宾克CLI可执行文件:
• [[T4],最好指[T5]]
• 或在[[T7] 上可用的Spine命令;

□ Spine 版本兼容性

这个MCP包是版本0.1.0.

该项目中的斯宾克-CLI指令建设已经与本地斯宾克-Pro/斯宾克-发射装置3.8.75进行对比. 特别是斯宾克[T10]要求导出命令使用导出设置 JSON 文件:

spine-mcp

English | 简体中文

GitHub shows this English README.md by default. The Chinese version is maintained in README.zh-CN.md.

Local MCP server for Spine automation on Windows. It only calls the official Spine CLI and communicates over stdio, so AI tools like Claude Code, Codex, and Cursor can start it locally.

This server does not do UI automation, AutoHotkey, mouse or keyboard simulation, timeline operations, mesh binding, bone weight editing, or direct .spine internals modification. It only modifies .spine files through the official Spine CLI.

Requirements

• Windows
• Node.js 20+
• Spine installed locally. This MCP does not include Spine and cannot run without a local Spine installation.
• A Spine CLI executable available as either:
  • SPINE_EXE, preferably pointing to Spine.com
  • or a Spine command available on PATH

Spine Version Compatibility

This MCP package is version 0.1.0.

The Spine CLI command construction in this project has been checked against local Spine Pro / Spine Launcher 3.8.75. In particular, Spine 3.8.75 requires export commands to use an export settings JSON file:

Spine -i "" -o "" -e ""

If a command fails even though the input paths are correct, first check whether your local Spine version has different CLI flags or export behavior. Run:

& "$env:SPINE_EXE" --help

Then compare the output with the command shown by the MCP result. Different Spine versions may require different export settings JSON formats, support different flags, or reject commands that work in 3.8.75.

Install

cd G:\spine-mcp
npm.cmd install

Configure Spine

Recommended: point SPINE_EXE to your local Spine.com. The example below is the default install style, but use the actual path for your own Spine installation.

$env:SPINE_EXE = "C:\Program Files\Spine\Spine.com"

Example for a custom local install path:

$env:SPINE_EXE = "E:\BaiduNetdiskDownload\Spine pro 3.8.75+K'D\Spine.com"

Confirm the CLI is reachable and note the version:

& "$env:SPINE_EXE" --help

To persist it for future PowerShell sessions:

[Environment]::SetEnvironmentVariable("SPINE_EXE", "C:\Program Files\Spine\Spine.com", "User")

If SPINE_EXE is not set, the server runs Spine directly.

Build

npm.cmd run build
npm.cmd run typecheck

Start

node G:\spine-mcp\build\index.js

The server uses stdio. Do not expect normal terminal output on stdout because stdout is reserved for the MCP protocol. Diagnostic logs go to stderr.

Add To Claude Code

Basic setup:

claude mcp add --transport stdio spine-mcp -- node G:\spine-mcp\build\index.js

With an explicit Spine CLI path: