Blender

Description

Blender is a free and open source 3D creation suite covering modelling, sculpting, animation, simulation, rendering and compositing.

Overview

This role installs Blender on a workstation and connects it to the coding agents the same host deploys, so a model can drive the scene instead of only describing it.

The bridge has two halves. Inside Blender an add-on opens a local socket; outside it the mcp-for-blender server speaks the Model Context Protocol over stdio and relays to that socket. Both halves come from the same pinned upstream distribution, which also carries the install-addon subcommand this role uses to place the Blender side.

Registration follows the host: the role declares claude and code as services gated on whether dsk-gnt-claude and dsk-code are deployed, and registers the server only with the clients that are present. A workstation without either installs Blender and the bridge, and nothing tries to configure an absent editor.

The agents keep their own model wiring. dsk-gnt-claude already points at the LiteLLM gateway, so a prompt reaches the local gateway and the resulting tool calls reach Blender.

Architecture

ARCHITECTURE.md draws Blender from its own metadata: the containers it runs under compose, what changes under swarm, how each volume is backed, and every role it depends on or is depended upon by.

Section	Drawn from
Compose	meta/services.yml
Swarm	meta/services.yml replicas and placement
Volumes	meta/volumes.yml against the NFS decision chain
Dependencies	meta/services.yml and meta/main.yml of every role

Features

• Agent-driven modelling: An MCP client creates, edits and renders scenes through Blender’s own Python API.

• Follows the host: The MCP server is registered with each agent the workstation actually deploys.

• Pinned bridge: Add-on and server ship from one version-pinned distribution, so the two halves cannot drift apart.

• No remote installer: The server arrives through pipx and the add-on through its own subcommand.

Quick Setup

Development

Clone, set up the workstation, and deploy Blender onto the local stack:

git clone https://github.com/infinito-nexus/core.git
cd core
make onboard
make compose-deploy mode=reinstall apps=dsk-blender full_cycle=false

Production

Install Blender directly onto the target machine: clone the repository, install the OS prerequisites and the repository toolchain, then deploy against localhost over a local connection (no SSH, no container):

git clone https://github.com/infinito-nexus/core.git
cd core
bash scripts/install/package.sh
make install
source scripts/meta/env/load.sh

APP=dsk-blender
DOMAIN="<your-domain>"
TLS_MODE=self_signed
SSH_PUBLIC_KEY="<your-ssh-public-key>"
INVENTORY=inventories/production
infinito administration inventory provision "$INVENTORY" \
  --inventory-file "$INVENTORY/devices.yml" \
  --host localhost \
  --include "$APP" \
  --vars "{\"TLS_MODE\": \"$TLS_MODE\", \"DOMAIN_PRIMARY\": \"$DOMAIN\", \"users\": {\"administrator\": {\"authorized_keys\": [\"$SSH_PUBLIC_KEY\"]}}}"
infinito administration deploy dedicated "$INVENTORY/devices.yml" \
  --password-file "$INVENTORY/.password" \
  --diff -vv

Further Resources

• MCP for Blender

• Model Context Protocol

• Blender Python API

Credits

Kevin Veen-Birkenbach

Part of the Infinito.Nexus Project and maintained by Kevin Veen-Birkenbach. Licensed under the Infinito.Nexus Community License (Non-Commercial).

That licence covers this role. The software it deploys is a separate grant: GPL-2.0-or-later, under which commercial use is allowed. You owe its authors this much: publish the source of changes you distribute. Permission for one of the two is not permission for the other.