Ugur T.
Feature Request:
I'd like to request an official scripting API or Model Context Protocol (MCP) server integration for Plasticity.
What this would enable:
Right now, tools like Autodesk Fusion 360 can be controlled directly by AI assistants like Claude Code via an MCP server. This means you can describe a part in plain English — "create a 40mm bracket with two 5mm holes spaced 20mm apart" — and the AI executes every modeling step inside the CAD tool, just like a human would. The result is precise, editable geometry, not a mesh approximation.
Plasticity is already the best-in-class tool for artist-friendly NURBS and hard-surface modeling, built on the same Parasolid kernel as SolidWorks and Siemens NX. Adding an MCP interface would make it the most powerful AI-native CAD tool for creatives — a category no one else owns yet.
What I'm asking for, concretely:
A local MCP server (or equivalent scripting/automation API) that exposes Plasticity's core modeling operations — sketch creation, extrude, boolean, fillet, loft, sweep, export — so that AI coding assistants can drive Plasticity through natural language, the same way FusionMCP works for Fusion 360.
Since Plasticity's application layer is already open-source (LGPL), the community could likely build and maintain this — but an official hook or documented internal API would make it far more reliable and sustainable.
Why this matters:
The Claude Code + Fusion 360 MCP workflow is gaining serious traction (tens of thousands of views on YouTube tutorials in May 2026 alone). Plasticity users — especially indie designers, game artists, and product prototypers — are exactly the audience who would benefit most from this kind of AI acceleration. Without an API, they're forced to switch to Fusion 360 just to access this workflow, despite already owning Plasticity licenses.
This would be a major differentiator and a strong signal that Plasticity is ready to be part of the modern AI-assisted design stack.