mcp-c4d-2025
Related Servers
Alternatives to mcp-c4d-2025
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceBridges MCP-compatible clients to Cinema 4D, enabling LLMs to inspect scene hierarchy, author shots, build node materials, and rig animation through a typed, undo-safe tool layer.67559 npm25MIT
- 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
- AlicenseBqualityBmaintenanceEnables AI agents to drive Autodesk Maya through semantic tools covering scene, object, material, animation, and rendering operations, paired with execute_python/execute_mel escape hatches and read-only resources. Also supports multi-instance routing, viewport capture for visual iteration, and asynchronous render job polling.221MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to programmatically control Autodesk Maya via natural language using over 30 tools for 3D modeling, lighting, and animation. It connects through Maya's command port to facilitate procedural scene generation and complex production-ready workflows.1-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to directly control SideFX Houdini, including creating nodes, setting parameters, executing Python, capturing viewports, and rendering frames, via 57 MCP tools.2MIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude and other MCP clients to control Autodesk Maya 2024 through 244 typed tools, including modeling, rigging, previs, FX, Arnold rendering, asset libraries, AI 3D generation, and a real-time change stream for Unreal.MIT
TDQS
Scored across 82 tools
Most tools are individually well-described, but several groups overlap: render/preview_render/rs_render, create_entity vs rs_create_material, describe vs get_container, and create_render_data vs rs_configure_render can all be reasonable choices for the same task. The descriptions usually resolve the ambiguity, but the boundaries are not always crisp.
The dominant verb_noun snake_case pattern is consistent, and subsystem prefixes like rs_, list_, get_, and set_ are used predictably. Minor deviations exist: remove_ vs delete_, bare verbs like render/undo/batch, and outliers such as new_document, describe, dump_shader, and take_override.
82 tools is well beyond the 25+ threshold and creates a heavy selection surface for agents, even for a broad Cinema 4D automation domain. Several specialized groups, especially the 13 Redshift tools and multiple node-graph/Xpresso variants, could likely be consolidated.
The surface is unusually broad: document lifecycle, scene entity CRUD, params, animation, meshes, layers, selection, rendering, Redshift, node graphs, and Xpresso are all covered, with few dead ends. Minor gaps exist, such as no explicit active-RenderData switcher and no generic Python escape hatch, but most workflows can be assembled from existing tools.