MCP server for Cinema 4D — entity CRUD, parameter-level access, batched undo, security controls.
MCP server for Cinema 4D — entity CRUD, parameter-level access, batched undo, security controls. The mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 4 defined tools rather than through you.
Let an LLM drive Cinema 4D. mcp-cinema4d bridges MCP-compatible clients (Claude Desktop, Claude Code, or any other stdio-capable MCP client) to a running Cinema 4D 2026 session so the model can inspect scene hierarchy, author shots, build node materials, and rig animation through a typed, undo-safe tool layer — not arbitrary Python pasted into a Script Manager.
Everything the assistant can do here goes through one of these:
Group — CountBasics — 4Script-style — 5Layers — 5You will need 4 environment variables: C4D_MCP_TOKEN, C4D_MCP_HOST, C4D_BRIDGE_HOST, C4D_MCP_BRIDGE_HOST. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Installation goes through your MCP client rather than a global install: point it at @kumoproductions/mcp-cinema4d on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP's toolset — Group, Basics, Script-style and 1 more — is a fair guide to whether it matches your workflow. It is maintained by kumoproductions; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Group | Count |
| Basics | 4 |
| Script-style | 5 |
| Layers | 5 |
{
"mcpServers": {
"cinema4d": {
"command": "npx",
"args": ["-y", "@kumoproductions/mcp-cinema4d"],
"env": {
"C4D_MCP_TOKEN": "your-value",
"C4D_MCP_HOST": "your-value",
"C4D_BRIDGE_HOST": "your-value",
"C4D_MCP_BRIDGE_HOST": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| C4D_MCP_TOKEN | Credential the server authenticates with. | Yes |
| C4D_MCP_HOST | Endpoint or connection string the server talks to. | Optional |
| C4D_BRIDGE_HOST | Endpoint or connection string the server talks to. | Optional |
| C4D_MCP_BRIDGE_HOST | Endpoint or connection string the server talks to. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.