About this integration
MCP server for Cinema 4D — entity CRUD, parameter-level access, batched undo, security controls.
- Transport
- stdio
- Authentication
- unknown
- Initial setup
- credentials
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.4.3
- Package
- @kumoproductions/mcp-cinema4d
- Last compatibility test
- Not independently tested
Connect your agent
@kumoproductions/mcp-cinema4dReviewed from frozen publisher README and manifest captures. Evidence is documentation-only; the package, service, and remote endpoint were not executed.
Capabilities: Inspect Cinema 4D scenes, Create or modify scene objects, Invoke plugin-backed rendering operations
Connected profiles
Additional details
io.github.kumoproductions/mcp-cinema4d
Source ↗ · Checked 2026-09-170.4.3
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17npm
Source ↗ · Checked 2026-09-17@kumoproductions/mcp-cinema4d
Source ↗ · Checked 2026-09-190.4.3
Source ↗ · Checked 2026-09-19Cinema 4D and its separately installed plugin must remain running for bridge requests.
Source ↗ · Checked 2026-09-19A random shared token is configured on both the MCP server and plugin.
Source ↗ · Checked 2026-09-19The npm stdio server connects to the loopback Cinema 4D plugin bridge.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19