Skip to main content
Glama
YihonW

mcp-c4d-2025

by YihonW

Related Servers

Alternatives to mcp-c4d-2025

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables 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.
      -
    • 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
      207 npm
      28
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables 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.
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables 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.
      -

    TDQS

    A3.5/5.0

    Scored across 82 tools

    Disambiguation3/5

    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.

    Naming Consistency4/5

    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.

    Tool Count2/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues