DevOps / SRE / Platform · 21.08.2026, 20:31 UTC
Spline rebuilt its entire 3D editor. Then it handed the keys to Claude Code.
| Schweregrad | info |
|---|---|
| Kategorie | DevOps / SRE / Platform |
| Quelle | The New Stack ↗ |
| Veröffentlicht | 21.08.2026 UTC |
Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.
Spline released V2 on Thursday, a complete rebuild of its 3D editor that enables external coding agents to work directly on live, editable scenes.
The key new addition, Spline MCP Server, opens the editor to Claude Code, Cursor, Codex, Google Antigravity and VS Code. Through a local server bundled with the desktop app, those tools can work directly within a live Spline project, changing the scene and its behavior while keeping the result fully editable.
Spline V2 also includes its own AI agent, which can build and edit a scene from a prompt. MCP lets developers access the same design environment from a coding agent that already understands the codebase and the work in progress, without having to rebuild that context in a separate Spline conversation.
Through a local server bundled with the desktop app, those tools can work directly within a live Spline project, changing the scene and its behavior while keeping the result fully editable.
MCP calls hit live scenes
The MCP server is bundled directly into Spline’s rebuilt desktop application for macOS and Windows; it does not work in the browser, and there is no standalone server package to install.
When the desktop app opens, it looks for supported clients and registers the server in their configuration files. The developer then restarts the AI client and prompts it normally. If someone asks Claude Code to create a floating island, for example, Claude turns that request into structured MCP tool calls. Spline then routes those calls to an open 3D editor tab, where they run against the live document. If no suitable file …