Spline V2's Real News Is the MCP Door, Not the WebGPU Rewrite

Spline's V2 is a full rewrite of its browser based 3D editor on WebGPU, and that renderer swap is the least interesting part of the release. The part worth paying attention to is the new MCP server, which lets an external coding agent, Claude Code, Cursor, whatever you are running, create and edit objects, materials, lights and interactivity directly inside a Spline scene.

That is a door into the file itself, not a plugin or an export step. An agent can add a light, adjust a material, wire up an interaction, and see it land in the same scene you have open, because it is talking to the project the same way a person clicking around the canvas would. A new code tab adds runtime HTML and JS access to scene data on top of that, so the scene is readable and drivable from outside the editor too.

Design tools have started adding this kind of hook one by one. Figma has moved in this direction, and now a web native 3D tool has followed with MCP specifically, rather than a bespoke integration only one assistant can use.

We think that is the real headline. A rewritten renderer makes Spline faster and nicer to use today. An open door for agents changes what a 3D scene file even is, a thing a person edits, or a thing a person and an agent both edit at once, and V2 is a clear step toward the second version of that answer.