Cinema4D MCP
Drives a running Cinema 4D session over a socket plugin, so scene changes appear in the viewport.
Add it to your client
Community- Transport
- stdio
- Runtime
- Python
- License
- MIT
- Stars
- 114
The setup is two pieces and both are required. A plugin file is copied into the Cinema 4D preferences folder and started from the Extensions menu, where it opens a socket server; the Python MCP server then connects to that socket and forwards commands. There is no headless path, and that is a design position rather than a gap: the scene stays live in a real session, so an artist watches each object, material and transform land instead of receiving a rendered file after the fact and guessing what changed. It targets Cinema 4D R2024 and later and needs Python 3.10 or newer for the server half. An agent skill is bundled alongside the tool commands.
Similar MCP servers
Blender MCP
MCP serverDrives Blender from a prompt — scene inspection, object edits and arbitrary Python execution.
Penpot MCP Server
MCP serverPenpot's official server drives an open design file through a plugin running inside the editor.
Unreal Engine MCP Server
MCP serverControls the Unreal Editor through a native C++ automation plugin: actors, levels, Blueprints, Niagara and Sequencer.
Comments(0)
Sign in to comment