Cinema 4D MCP plus Sume MCP in one Claude Desktop chat

Yes, you can run both in one Claude Desktop chat. Cinema 4D's new MCP server drives the scene on your machine, and Sume's hosted MCP server handles the generative steps afterwards: animating a render, adding voice, or cutting variants. The two servers do not talk to each other, so Claude is the glue, and the hand-off between them is a file at a public HTTPS URL.

What does the Cinema 4D MCP server do?

According to CG Channel's report on Cinema 4D 2026.4, released September 30, 2026, the server lets AI tools control Cinema 4D through natural-language prompts. The tasks listed include scene hierarchy and naming, multi-pass renders, camera tracking, basic modeling, UV editing, rigging and animation, and particle and liquid simulations. Maxon stresses that it is not a generative system: it executes instructions rather than inventing designs.

Claude Desktop and ChatGPT Desktop are the officially supported clients. The server runs locally, is off by default, and needs a separate opt-in before it uses the network.

Where does Sume fit?

Cinema 4D produces exact, controllable geometry. Sume is the generative side: it can turn a still or a prompt into motion with generate_video, make stills with generate_image, and so on. Sume's MCP server is hosted, so you add it as a remote connector rather than a local process.

A sensible split is to let Cinema 4D own anything that must be exact (product shape, logo placement, camera path) and let Sume own anything that benefits from generation (background life, secondary motion, variants for different platforms).

How do I hand a render from one to the other?

Sume's media inputs are URL-first, and a hosted server cannot read your disk. For a local render you have two options. Host the file at a public HTTPS URL and pass that URL to the generator, or use the upload flow: the assets_upload_url tool returns a target, your client does the PUT, and assets_complete finishes it.

Note that assets_create only registers metadata for a URL you already host and does not verify it, so it is not an upload.

• Ask Claude to render a single hero frame in Cinema 4D first, not the whole sequence.
• Upload it with the assets flow or host it, then call generate_video with that URL as the starting image.
• Wait with jobs_wait in slices of up to 55 seconds, then fetch results with jobs_result on the same job IDs.
• If a wait times out, wait again on the same IDs. Do not resubmit a paid create.

What should I watch for on the Sume side?

OAuth sign-in with the mcp:read scope is read-only. Creating media needs mcp:write (or an API key), and every paid or writing call needs an idempotency_key so a retry never pays twice. For three or more independent calls of the same shape, such as one video per aspect ratio, Sume's script_run runs the loop on Sume's side with the same gates, and each paid create inside it still needs its own idempotency_key.

Before a big batch, estimate with generation_admission_preview and check balance_get. Ask Claude to confirm with you before any expensive step.