Skip to main content
Glama
Aitidi

Cinema4D MCP

by Aitidi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Cinema4D MCP

No user-submitted related servers found.

    Related Servers

    • blender-mcp

      sandraschi
      A
      license
      C
      quality
      A
      maintenance
      Enables AI-powered control of Blender through natural language, allowing users to create, manipulate, and automate 3D scenes, objects, materials, animations, and more via Claude or other MCP clients.
      71
      41
      MIT

    • BlenderMCP

      diegofornalha
      A
      license
      B
      quality
      D
      maintenance
      BlenderMCP enables Claude AI to directly interact with and control Blender for prompt-assisted 3D modeling, scene creation, and manipulation. It supports object and material control, scene inspection, and execution of Python code through natural language commands.
      17
      MIT

    • mcp-cinema4d

      kumoproductions
      A
      license
      A
      quality
      A
      maintenance
      Bridges 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.
      67
      119 npm
      22
      MIT

    • BlenderMCP

      nludd25
      A
      license
      A
      quality
      C
      maintenance
      Enables connecting Blender 3D to AI assistants via MCP, allowing prompt-driven 3D modeling, scene editing, and real-time manipulation. Supports object/material control, scene inspection, viewport screenshots, and integrations with Poly Haven, Sketchfab, and AI model generators.
      22
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.4/5.0

    Scored across 37 tools

    Disambiguation2/5

    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.

    Naming Consistency3/5

    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.

    Tool Count2/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources