Blender plugin
Install the public KinoCloud Blender integration and understand its current qualification status.
Type: How-to · Applies to: Blender
Blender is the only publicly listed and downloadable KinoCloud DCC plugin. It is the only provisioned candidate, but full production qualification is still pending. Do not treat the plugin or its cloud render lane as fully live.
The Blender plugin includes a default-off embedded MCP server that controls the running host through a typed command allowlist, plus the in-host Director Chat UI.
Embedded DCC MCP is not the hosted cloud MCP at https://kinocloud.io/mcp: it listens only on a generated 127.0.0.1 port, uses a per-session token, and exposes Blender scene commands rather than the cloud job catalogue. Start it explicitly from the KinoCloud panel and stop it when no longer needed.
Download Blender from Settings → DCC Plugins.
Current capability
| Host | Public status | In-host agent surface |
|---|---|---|
| Blender | Only provisioned candidate; full production qualification pending | Director Chat + embedded MCP |
Installing the plugin does not make its cloud render lane live. Runtime eligibility remains fail-closed on fleet binaries, node probes, qualification, and deployment configuration. A gated lane fails before upload or billing with an explicit availability error.
Install and authenticate
- Download the Blender zip from Settings → DCC Plugins.
- In Blender, open Preferences → Add-ons → Install, select the zip, and enable KinoCloud.
- Open the KinoCloud panel and sign in. The standard plugin flow opens
https://kinocloud.iofor OAuth and stores the resulting session in the OS keyring, with a restricted file fallback where keyring support is unavailable. API keys are for headless or self-hosted API clients, not the normal Blender login flow.
Start embedded MCP
Use Blender’s Start MCP action. The plugin displays a URL such as http://127.0.0.1:<port>/mcp and creates a bearer token for that run. Connect an MCP client directly or through packages/plugins/tools/mcp_stdio_proxy.py.
Nothing listens before the artist starts the server. The token is regenerated after restart, the listener never binds a non-loopback interface, host calls are marshalled to Blender’s main thread, and tools cannot execute arbitrary code.
Staying current
The plugin reports its build version and checks the public build manifest. Re-download and reinstall when the panel reports an update. Capability badges describe conservative product status; the API and node probes remain authoritative.