Skip to main content
Glama
kumoproductions

mcp-cinema4d

by kumoproductions
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mcp-cinema4d

No user-submitted related servers found.

    Related Servers

    • mcp-c4d-2025

      YihonW
      A
      license
      A
      quality
      B
      maintenance
      Enables an LLM to drive Cinema 4D through typed tools for scene inspection and editing, guarded Redshift rendering, animation controls, and bounded PNG sequence rendering.
      82
      2
      MIT

    • Cinema4D MCP

      Aitidi
      A
      license
      C
      quality
      C
      maintenance
      Enables 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.
      37
      MIT

    • Cinema4D MCP Server

      georgesoto830
      F
      license
      Not graded
      quality
      A
      maintenance
      Connects Claude to Cinema 4D so you can create and manipulate scenes through natural-language prompts. It exposes tools for building primitives and abstract shapes, grouping objects, adding cameras, lights, materials and shaders, applying MoGraph cloners, effectors and fields, setting keyframes, driving physics, running Python inside C4D, and rendering previews or frames.
      -
    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

    A3.7/5.0

    Scored across 67 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count2/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources