Maxon has built MCP support into Cinema 4D 2026.4, letting Claude and ChatGPT carry out tasks in the artist's own scene. It is off by default.
Maxon has added built-in Model Context Protocol (MCP) support to Cinema 4D, opening the door for using natural language instructions to direct Claude and ChatGPT assistants within Cinema 4D workflows as users work. Maxon officially supports Claude Desktop and ChatGPT Desktop. Other MCP-compatible apps may work but are unsupported.
The implementation supports all aspects of the Cinema 4D workflow, including procedural, iterative, and repetitive work, but nothing generative. Tasks that artists can hand off to an AI include organizing hundreds of imported objects into a consistent hierarchy, creating object and material variations, preparing multipass renders, organizing scenes, and even handling basic 3D camera tracking, UV mapping, rigging, and animating.
Every action happens through Cinema 4D's own tools and API, in the artist's own scene, on their own machine. The results remain native Cinema 4D scene data that artists can inspect, refine, or undo.
For studios and enterprise teams, access tokens, configurable permissions, and audit logging are available. The connection runs locally, with a separate opt-in required to work with other machines on the network. The MCP server is protected by an MCP adapter access token. Artists can choose which groups of Cinema 4D tools their assistant is permitted to use, and have control over Python execution. Each batch of MCP-driven changes is broken down in the undo history, and commands are written to a local audit log.
Implementation seems fairly straightforward judging by the docs on the Maxon website. MCP is switched off by default and must be enabled by the user.
MCP support is available now in Cinema 4D 2026.4 or later on Windows and macOS. The connection can be activated without additional installs.