Cinema 4D
Cinema4D MCP Server enables Claude to interact with Cinema 4D through a socket-based communication system, allowing for scene manipulation, rendering, and animation directly from conversations. The implementation includes both a Python MCP server component and a Cinema 4D plugin that establishes a socket connection, supporting operations like creating primitives, applying materials, setting keyframes, and working with MoGraph objects. It features thread-safe execution of commands in Cinema 4D's main thread, comprehensive object detection including MoGraph elements, and robust error handling - making it particularly valuable for 3D artists and motion designers who want to prototype ideas or automate workflows without leaving their AI assistant interface.
Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-19.
Scan details: Circle-IR · 2026-09-19 · Appeal
View full trust & usage report →Metadata
- Version
- 1.0.0
- Skill type
- atomic
- Execution layer
- mcp-remote
- Category
- other
- Source
- PulseMCP
- Repository
- github.com/ttiimmaacc/cinema4d-mcp
- Author type
- human
- Last scanned
- 2026-09-19
- Updated
- 2026-09-19
Use via MCP
Resolve Cinema 4D from your agent
Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.
One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.
claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp--scope user for --scope project to commit it to .mcp.json.