mcp.film / 3D, Worlds & VFX / Cinema 4D MCP Server

Cinema 4D MCP Server

Officialby Maxonpaidverified Oct 1, 2026

Maxon's built-in MCP server: drive scenes, variations, multipass renders and sims in Cinema 4D.

What it does

Shipped inside Cinema 4D 2026.4 on 30 Sep 2026, this is Maxon's first-party bridge between a desktop assistant and a running C4D session. An agent can reorganise scene hierarchies and naming, spin out object and material variations, set up and composite multipass renders, prepare 3D camera tracks, do basic modelling and UVs, rig and animate, and build particle and liquid sims, with Python as the escape hatch for anything the toolset does not cover. Maxon is explicit that it is not generative — it makes no imagery and has no opinion on whether a shot works — so its value in a film pipeline is the tedious scene housekeeping that eats a motion-graphics or title-sequence artist's day.

Connect

Connection is set up through the vendor's flow — follow the official connect instructions.

Local install: No package to install: in Cinema 4D 2026.4+, open Preferences → MCP, enable the MCP server, then under Clients pick your assistant, click Update Selected Client, and restart the client. Cinema 4D writes the client entry itself.

Auth: local-app — Requires the full Cinema 4D 2026.4+ application running (Windows or macOS) with the MCP server enabled in Preferences; access is gated by an MCP adapter key that Cinema 4D manages

Field notes

One day old at listing: released with Cinema 4D 2026.4.0 on 30 Sep 2026, per Maxon's FAQ page and coverage in CG Channel and AEC Magazine. The server costs nothing extra, but Cinema 4D is subscription-only ($109/month or $839/year per CG Channel), so this is a paid entry in practice. Off by default; connections are local-only unless you tick Allow Remote Connections, and Maxon warns remote traffic is unencrypted, so whitelist IPs and keep it on a trusted network. Not available in Cinema 4D Lite, Commandline, Team Render, c4dpy or Cineware. Claude Desktop and ChatGPT Desktop are the officially supported clients; other MCP clients and local models via LM Studio may work but are unsupported, and a local model will fight C4D and your renderer for the same GPU. Maxon also notes it slows down on scenes with hundreds of separate objects. Two separate toggles — Allow exec_python Command and Allow Python-Bearing Operations — decide whether the agent can run arbitrary Python or author Python-containing objects; leave both off unless you need them. Fifteen tool groups can be switched individually, but Maxon has not published tool names in a form this directory could read (the help pages render client-side), and no Claude Code command is documented — Cinema 4D writes client configs itself, so Claude Code users should copy the generated entry. For C4D 2024–2026.3 the community ttiimmaacc/cinema4d-mcp remains the fallback.