Cinema4D MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| C4D_MCP_HTTP_HOST | No | Host/interface for the HTTP server when using streamable-http transport (e.g., '127.0.0.1'). | 127.0.0.1 |
| C4D_MCP_HTTP_PATH | No | URL path/endpoint for the HTTP MCP server (e.g., '/mcp'). | /mcp |
| C4D_MCP_HTTP_PORT | No | Port for the HTTP server when using streamable-http transport (e.g., '8790'). | 8790 |
| C4D_MCP_TRANSPORT | No | Transport mode for the MCP server. Common values are 'stdio' (default) or 'streamable-http'. | stdio |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_scene_infoA | Get information about the current Cinema 4D scene. |
| add_primitiveB | |
| modify_objectC | |
| list_objectsA | List all objects in the current Cinema 4D scene. |
| create_materialC | |
| apply_materialB | |
| inspect_redshift_materialsA | |
| render_frameB | |
| set_keyframeC | |
| save_sceneC | |
| load_sceneB | |
| create_mograph_clonerC | |
| add_effectorB | |
| apply_mograph_fieldsB | |
| create_soft_bodyC | |
| apply_dynamicsC | |
| create_abstract_shapeB | |
| create_cameraB | |
| create_lightB | |
| apply_shaderC | |
| animate_cameraB | |
| execute_python_scriptA | |
| group_objectsC | |
| render_previewA | |
| snapshot_sceneB | |
| inspect_scene_nodes_graphC | Inspect the document-level Cinema 4D Scene Nodes graph. |
| search_scene_node_assetsB | Search installed Scene Nodes NodeTemplate assets. |
| describe_scene_node_assetC | Describe a Scene Nodes asset in an isolated temporary document. |
| edit_scene_nodes_graphC | Apply ordered Scene Nodes graph operations with per-operation rollback. |
| layout_scene_nodes_graphD | Run Cinema 4D's native Scene Nodes layout command. |
| inspect_capsule_instancesC | Discover object, tag, and Capsule instance graphs in the active document. |
| inspect_capsule_graphC | Inspect the exact Capsule instance graph identified by graph_target. |
| focus_capsule_graphC | Select a Capsule owner and request that Cinema 4D show its exact graph. |
| search_capsule_assetsC | Search installed Capsule and NodeTemplate assets without modifying repositories. |
| describe_capsule_assetC | Describe a Capsule asset using an isolated temporary document. |
| edit_capsule_graphB | Edit one exact Capsule instance graph with ordered partial-success operations. |
| layout_capsule_graphC | Request native layout for one exact Capsule instance graph. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_primitives_info | Get information about available Cinema 4D primitives. |
| get_material_types | Get information about available Cinema 4D material types and their properties. |
| get_connection_status | Get the current connection status to Cinema 4D. |
TDQS
Scored across 37 tools
Several tools occupy fuzzy boundaries: create_soft_body and apply_dynamics can both create soft bodies, render_frame and render_preview are easy to confuse, and add_effector / apply_mograph_fields / apply_shader overlap in material/effector workflows. The scene-nodes and capsule tool groups are structured but numerous, and get_scene_info, list_objects, and inspect_scene_nodes_graph all invite mis-selection for scene inspection.
All names are snake_case and mostly verb_noun, but the verb set is inconsistent: add_primitive, create_material, create_camera, add_effector, apply_dynamics, and create_soft_body capture similar actions with different verbs. The scene-nodes and capsule families are highly parallel, but their dense prefix/style can blur into one another.
37 tools is beyond a reasonably scoped MCP surface, especially when many are variants of inspect/edit/layout for Scene Nodes and Capsules. The core manipulation utilities could be much smaller; the additional sub-families push the set into heavier-than-useful territory.
The toolset is broad and covers scene creation, rendering, objects, materials, lights, animation, and MoGraph, but it has obvious lifecycle gaps like no direct object/material deletion and no dedicated keyframe-timeline management beyond set_keyfree. The execute_python_script fallback mitigates missing operations, but the structured API still has notable dead ends.