mcp-cinema4d
Related Servers
Alternatives to mcp-cinema4d
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables an LLM to drive Cinema 4D through typed tools for scene inspection and editing, guarded Redshift rendering, animation controls, and bounded PNG sequence rendering.822MIT
- FlicenseNot gradedqualityAmaintenanceEnables Claude to drive Cinema 4D through natural-language prompts, creating and modifying 3D scenes via tools for primitives, objects, cameras, animation, lights, materials, Redshift inspection, MoGraph cloners and fields, dynamics, and rendering previews or frames. It bridges a Python MCP protocol server to a Cinema 4D socket plugin so users can build, inspect, save, and load scenes conversationally.-
- AlicenseCqualityCmaintenanceEnables prompt-assisted 3D manipulation in Cinema 4D, including scene editing, object creation, animation, lighting, and material management, through MCP clients like ChatGPT, Claude, and Codex.37MIT
- FlicenseNot gradedqualityAmaintenanceEnables prompt-driven creation, inspection, and manipulation of 3D scenes via Claude, including objects, cameras, materials, MoGraph, dynamics, Redshift inspection, and rendering. It bridges MCP tools to a 3D application plugin for natural-language modeling workflows.-
- FlicenseNot gradedqualityAmaintenanceConnects Cinema 4D to Claude, enabling prompt-assisted modeling, scene creation, object manipulation, materials, lighting, cameras, animation, MoGraph, dynamics, rendering, and Redshift inspection through MCP tools.-
- FlicenseNot gradedqualityAmaintenanceEnables users to create and manipulate Cinema 4D scenes through natural-language prompts by exposing tools for primitives, cameras, lights, materials, Redshift, MoGraph, dynamics, rendering, and custom Python execution.-
TDQS
Scored across 67 tools
Tools are grouped into distinct Cinema 4D subdomains (document, entity, render, take, marker, layer, graph, Xpresso, mesh, MoGraph, plugins), and descriptions actively cross-reference alternatives, which keeps most boundaries clear. Some overlap remains—for example set_params vs set_transform/take_override, list_entities vs list_graph_nodes, and unified create_entity vs specialized creators—but the distinctions are documented.
The set overwhelmingly follows a predictable snake_case verb_resource pattern (list_*, get_*, set_*, create_*, remove_*, apply_*), making tool intent easy to infer. A few bare command-like names such as render, undo, batch, ping, and describe slightly break the strict verb_noun convention, but overall naming remains highly consistent.
With 67 tools, the server is far above the typical agent-friendly range and creates substantial selection load, even though Cinema 4D is a broad domain. Many specialized operations (preview_render, reset_scene, batch, ping, plugin enumeration, multiple low-level graph/Xpresso primitives) could be consolidated or tiered to reduce surface area.
The surface covers core lifecycle operations across the major Cinema 4D domains: scene and document management, entity CRUD, parameter access, rendering, render data, takes, markers, layers, keyframes, meshes, node graphs, Xpresso, MoGraph, plugins, import/export, undo, and batch execution. No obvious core capability is missing for the stated purpose, and remaining gaps are minor or specialized.