Mcp Cinema4d

Please install the `mcp-cinema4d` MCP server into my current AI client (that's you).

Required prerequisites (do these first if not already done):
- **Install Node.js 24+** — Node.js version 24 or newer is required to run the MCP server via npx.
- **Install Cinema 4D 2026+** — A running Cinema 4D 2026.0.0 or newer session is required for the bridge plugin to respond. (https://www.maxon.net/en/cinema-4d)
- **Install the Cinema 4D bridge plugin** — Download the latest cinema4d_mcp_bridge-<version>.zip from the GitHub Releases page and extract the inner cinema4d_mcp_bridge/ folder into your Cinema 4D plugins directory, then restart Cinema 4D. Keep the plugin version matched to the npm package version. (https://github.com/kumoproductions/mcp-cinema4d/releases/latest)
- **Set matching bridge environment variables in Cinema 4D launch environment** — The same C4D_MCP_* variables used by the MCP server must also be set in the Cinema 4D process environment before launch or restart, because the bridge plugin reads them at Cinema 4D startup.

Optional prerequisites:
- Generate and set a shared token — Generate a random token and set C4D_MCP_TOKEN in both the MCP server environment and the Cinema 4D launch environment. Strongly recommended for secure operation; the bridge rejects mismatched requests when configured. Run: `openssl rand -hex 16`

Canonical MCP server config (stdio transport):
- command: `npx`
- args: ["-y","@kumoproductions/mcp-cinema4d"]
- optional environment variables:
  - `C4D_MCP_TOKEN`: Shared secret token for authenticating requests between the MCP server and the Cinema 4D bridge. If set, it must match the value in the Cinema 4D launch environment. (example: `<your-random-hex-token>`)
  - `C4D_MCP_HOST`: Host for the TCP bridge connection to the Cinema 4D plugin. Defaults to loopback. Must match the Cinema 4D bridge environment if changed. (example: `<your-bridge-host>`)
  - `C4D_MCP_PORT`: Port for the TCP bridge connection to the Cinema 4D plugin. Must match the Cinema 4D bridge environment if changed. (example: `<your-bridge-port>`)
  - `C4D_MCP_ENABLE_EXEC_PYTHON`: Optional opt-in to expose the exec_python tool. Must be set to 1 on both the MCP server and Cinema 4D sides to enable arbitrary Python execution. (example: `<1-or-true>`)
  - `C4D_MCP_ENABLE_PYTHON_OPS`: Not used by the Node MCP server itself, but the README states the same C4D_MCP_* variables may be set alongside server env values. On the Cinema 4D side, this enables creating or editing Python-bearing plugin types. (example: `<1-or-true>`)
  - `C4D_MCP_ALLOW_REMOTE`: Not required for local use. Relevant when binding the Cinema 4D bridge to a non-loopback host; the Cinema 4D plugin requires this to allow remote binding. (example: `<1-or-true>`)

Note: Transport is stdio for the MCP client connection. The MCP server then connects over TCP JSON Lines to the Cinema 4D bridge plugin, which by default listens on 127.0.0.1:18710. Cinema 4D must be running with the bridge plugin loaded before the server can function.

Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.