How to Connect Claude to Cinema 4D: The Built-In Cinema 4D MCP Server

To connect Claude to Cinema 4D, update to Cinema 4D 2026.4 or later and use its built-in MCP server: tick Allow MCP Server in Edit, Preferences, MCP, choose Claude Desktop under Clients, click Update Selected Client, then quit Claude completely and reopen it while Cinema 4D is running. Maxon officially supports Claude Desktop on Windows and macOS, and the server is free. Claude Code is not in Cinema 4D’s list, but it connects to the same local address, http://127.0.0.1:5556/mcp, with one command and a token. claude.ai in a browser cannot reach it.

I run MeltFlex, an AI rendering tool for architects and interior designers, and this is the third of our Claude guides for 3D software. It is different from the Claude and 3ds Max guide in one big way: Maxon built the server into Cinema 4D on September 30, so there is no plugin to choose. What its documentation leaves out is Claude Code, so I tested that part myself against a stand-in server that copies Maxon’s address and token check, and I list below the exact messages you will see when something is wrong.

The two halves, from their own pages: Maxon’s MCP server page and Anthropic’s desktop app download. Both must be on the same computer.

FreeUpload photo · freeRedesign my room for freeUpload a photo and let MeltFlex design your space. Your first AI design is free, no card needed.

Which Claude works with Cinema 4D: Claude Desktop, Claude Code or claude.ai?

Claude Desktop is the supported route, and Claude Code works too. Maxon’s MCP server page says: “At this time, Maxon officially supports Claude Desktop and ChatGPT Desktop.” The client list in Cinema 4D 2026.4 has three entries: Claude Desktop, OpenAI Codex and Other. The server listens only on your own computer by default, so anything that runs in Anthropic’s cloud cannot see it.

The Code tab row comes from Anthropic’s desktop docs: a server defined in claude_desktop_config.json “is available in both the Desktop chat surface and local Code tab sessions.” The plan rows come from Anthropic’s setup page: “The free claude.ai plan does not include Claude Code access.” Pro costs $20 a month, or $17 billed yearly, on the pricing page. Cinema 4D itself is rental only, at $109 a month or $839 a year in the US, according to CG Channel, and it needs Windows 10 or later or macOS 14 or later.

How do you connect Claude Desktop to Cinema 4D?

Five minutes, if you follow the order. This is Maxon’s procedure from its help pages, with the details I read off Maxon’s own setup videos.

1. Install and open Claude Desktop once on the computer that runs Cinema 4D. If Claude is missing, Cinema 4D lists it as “(not installed)”.
2. Turn on the server. Edit, Preferences (Cinema 4D, Preferences on a Mac), then MCP, the last item in the list. Tick Allow MCP Server and confirm the warning. It starts at once; the default port is 5556.
3. Write Claude’s entry. Under Clients, pick Claude Desktop and click Update Selected Client. The dialog shows the endpoint, http://127.0.0.1:5556/mcp, and the file it edits, claude_desktop_config.json. It saves a dated .bak copy first and leaves your other servers alone.
4. Quit Claude completely and start it again, with Cinema 4D still open. Closing the window is not enough: quit from the menu bar or the system tray, and end any leftover Claude process in Activity Monitor or Task Manager.
5. Test it. In Claude, Settings, Connectors should list cinema4d. Ask “Create a cube in Cinema 4D.” Claude asks permission for each tool the first time; if a cube appears, you are done.

Step 4 is where most setups fail. Maxon’s support article explains why: “When your AI app starts, it waits about 20 seconds for Cinema 4D. If Cinema 4D is not running by then, the app gives up and does not try again on its own.” Once connected, Claude does reconnect if you restart Cinema 4D. If it still sees nothing, the same article names two other causes: antivirus “Web Protection” scanning local traffic (add http://127.0.0.1:5556 as an exception, never a wildcard), and a third-party plugin breaking the server’s Python at startup, which shows in Extensions, Console, Python.

The best walkthrough is Maxon’s own. I went through it frame by frame: Jonas Pilz does the setup above on a Mac, then asks Claude Desktop, running Opus 5.5, to organize a messy scene. Claude groups the objects into named nulls and creates and assigns layers, in under three minutes of video.

Maxon Training Team, “#C4DQuickTip 251: How to activate and use Cinema 4D’s MCP”, October 1, 2026, 2 min 45 s. It is the vendor showing its own feature, so expect the happy path.

How do you connect Claude Code to Cinema 4D?

If you use the Code tab of the Claude desktop app, do the Claude Desktop setup above and you are finished. For Claude Code in a terminal, on Windows or a Mac, click Copy Token in the Server section of the MCP preferences and run:

claude mcp add --transport http --scope user cinema4d http://127.0.0.1:5556/mcp --header "Authorization: Bearer PASTE_TOKEN_HERE"

Then run claude mcp get cinema4d with Cinema 4D open and the server on. Maxon does not list Claude Code, so I could not take this from its docs. I worked it out from two sources: the endpoint in Maxon’s setup dialog, and the open source C4D_MMD_Tool, whose adapter talks to Maxon’s server with a Bearer token read from the mcp folder of the Cinema 4D preferences. I do not own a Cinema 4D license, so I wrote a small server that copies exactly that behavior and pointed Claude Code 2.1.309 at it:

One thing surprised me. claude mcp add hides the token in its output, but claude mcp get prints it in full. Maxon warns that anyone with the token and network access to your machine can drive Cinema 4D, and with Python allowed, your files too. So never paste mcp get output into a forum post or a support ticket.

On a Mac there is a cleaner option that also survives Regenerate Token: let Claude Code read the token from Cinema 4D’s token file each time it connects, with a headersHelper. Maxon says the entry from Other, Copy Config includes the token file’s location. Save this as ~/c4d-token.sh, with that path in place of TOKEN_FILE (keep the quotes, the folder name has spaces), and run chmod +x ~/c4d-token.sh:

#!/bin/sh
printf '{"Authorization":"Bearer %s"}' "$(cat "TOKEN_FILE")"

Then add the server with it:

claude mcp add-json --scope user cinema4d '{"type":"http","url":"http://127.0.0.1:5556/mcp","headersHelper":"$HOME/c4d-token.sh"}'

In my test, with a token file in a folder whose name has spaces, this connected, kept working after I changed the token, and mcp get no longer showed the secret. The test has limits: my server answered only two dummy tools, so it proves the connection and the error messages, not how well Claude works in a real scene.

The headersHelper option in Anthropic’s Claude Code docs, captured October 23, 2026.

Which Cinema 4D MCP settings matter?

• Python is on by default. Allow exec_python Command lets Claude run any Python “essentially the Script Manager, but remotely controlled”. Allow Python-Bearing Operations lets it put Python tags and generators into the scene, which, Maxon warns, “are saved with the .c4d file, and run whenever anyone opens the file.” Turn the second one off when you exchange scenes with clients or freelancers.
• Fewer tool groups, better choices. The Toolset section has 15 groups, from Rendering to Assets. In Maxon’s example, Claude reported 68 tools. Maxon’s FAQ says switching off groups you do not need “shortens the list and improves its choices”, and that a model which cannot see a tool will say the feature does not exist.
• Long commands. Cinema 4D’s Request Timeout (30 seconds in the video) limits how long one command may run. In Claude Code, an HTTP server also has a per-request timer of at least 60 seconds; if you raise Cinema 4D’s limit for heavy commands, raise the server’s timeout in Claude Code to match.
• Approvals belong to Claude. The permission prompts come from Claude, not Cinema 4D. Keep them for Python and file operations, and run one Cinema 4D server per client: Maxon asks you to switch off any third-party Cinema 4D server while you use the built-in one.
• Check the log. Every call is written to an audit log in the mcp folder that Open Preferences Folder opens, and each batch of changes is one undo step.

Maxon’s MCP documentation. The FAQ page is the most useful one: it is unusually candid about what the assistant gets wrong.

What can Claude actually do in Cinema 4D?

Chores, reliably; creative work, not yet. Maxon is blunt about it: the connection “is not a generative system. It does not invent designs, it does not produce imagery, and it holds no opinion about whether a shot works.” Its list of what works is renaming and reorganizing a hierarchy, translating object names, building takes from a spreadsheet, setting up object IDs and matte AOVs, tracking down why a rig fails, and writing small scripts. Its rule of thumb: routine maintenance “should come back in a minute or two, and if it does not, you are probably faster yourself.”

Two more warnings from the same FAQ are worth knowing before you trust a result. Claude does not see the scene, only tool answers, so “it can describe the result with more confidence than the result deserves”; check the Object Manager. And jobs that create hundreds of separate objects can stall, so ask for one merged mesh or work in batches.

The most honest outside report I found is by Azusa Kuno, a medical animator in Berlin, on note.com on October 9. Setup with Claude was “almost instantaneous”, and renaming imported objects and sorting them into layers was a job she “would never want to do by hand”. But modeling tools from photo references was “unusable even after several attempts”, and her overall view was that “for many tasks, it is faster to do it yourself in the end.” She also uses it only on projects without NDAs, because the scene data Claude reads goes to Anthropic.

Finished renders from the MeltFlex gallery, not made with Claude or Cinema 4D. Curved shelving and a planter bench are the kind of geometry Claude can block out; the light and materials still take a person.

What if you are on Cinema 4D 2026.3 or older?

Then you need a third-party server, and the best one says so itself. kumoproductions/mcp-cinema4d opens its README by sending 2026.4 users to Maxon and keeps itself for Cinema 4D 2026.0 to 2026.3, “which have no built-in server”, for running several Cinema 4D processes at once, and for people who want open source code.

kumoproductions/mcp-cinema4d on GitHub, October 23. Its exec_python is off unless you opt in on both sides, which is stricter than Maxon’s default.

The rental model makes this table short for most people: an active Cinema 4D subscription can update to 2026.4. If you cannot update, kumoproductions is the careful choice; the older ttiimmaacc server has no token, and Maxon’s own comparison says such add-ons usually open “an open port, commonly without authentication”.

Should architects, designers and motion artists connect Claude to Cinema 4D?

Yes, if you are on 2026.4 and pay for Claude. It is the easiest Claude setup of the 3D tools we have covered: no plugin, no hand-edited config, a vendor that supports it, and it works on a Mac as well as Windows. Start with a copy of a real scene and a dull job, such as naming and layering an imported model, and see whether the result holds up in the Object Manager. Turn off Python-Bearing Operations before you share scenes. Do not expect it to model or light for you.

For the image after the scene, our comparison of AI architectural rendering tools covers what works from a viewport capture, and our architectural rendering prompts cover what to write. This is where MeltFlex fits, so here is the disclosure: upload a Cinema 4D viewport capture to photo to render and it returns a finished image with the camera and geometry where they are, and floor plan to 3D does the same from a drawing. The same Claude approach works in Blender, Rhino, SketchUp and 3ds Max, and our list of MCP servers for architects covers the rest of the toolkit.

Two more from the MeltFlex gallery: moody light on plinths and a curved banquette, the kind of scene Cinema 4D artists are hired to light.

Sources and what we could not verify

Read on October 23, 2026: Maxon’s MCP server page, its help pages What is MCP? and MCP Server FAQ with the Server, Clients, Security, Toolset and Remote Access pages, and its connection troubleshooting article (updated October 19); CG Channel on the release; Maxon’s videos “How to set up the Cinema 4D MCP Server in 3 Steps” and QuickTip 251, checked frame by frame at 1080p; the READMEs of the four GitHub projects above and the C4D_MMD_Tool adapter; Azusa Kuno’s post; and Anthropic’s Claude Code MCP, desktop and setup pages. Quotes are word for word.

What we did not do: we did not run Cinema 4D, so the Claude Desktop steps come from Maxon’s documentation and videos, not our own clicks. Our Claude Code test used a stand-in server built from Maxon’s published endpoint and a third-party adapter’s code, not Maxon’s server; the command is right if Maxon’s server takes the token as that adapter sends it. We did not test the Claude free plan, Windows, or remote access, and we could not read the exact text of a Copy Config entry.

Claude and Cinema 4D: FAQ

Keep reading

• How to connect Claude to 3ds Max, the Windows route and our 179-tool token test.
• How to connect Claude to Blender, the free route on a Mac.
• How to connect Claude to Rhino, McNeel’s official server and our Opus 5.5 living room test.
• The best MCP servers for architects, the wider Claude Code toolkit.
• Photo to render, turn a Cinema 4D viewport capture into a finished image.