Blender Socket Control

The problem

Controlling 3D software via natural language or scripts is difficult because Blender lacks a native, easy-to-access remote interface for external agents. Developers often have to write custom Python scripts and execute them manually within Blender's internal environment.

What it does

• Establishes a WebSocket connection between an external agent and a running Blender instance.
• Creates 3D primitives like cubes, spheres, and cylinders with precise coordinates.
• Applies materials, textures, and modifiers programmatically to scene objects.
• Configures render engines, resolutions, and samples for automated image generation.
• Saves local .blend files to persist the session and retrieve rendered assets.

Frameworks & tools

Blender (3.6+), blender-mcp addon, Python, WebSocket, JSON.

Why this beats prompting it yourself

General-purpose agents often hallucinate Blender's internal API methods or fail to manage the lifecycle of a headless session. This skill provides a structured command protocol that ensures the agent follows a valid execution flow, from socket handshake to file export.

Use cases

• Automating the generation of 3D assets for datasets or e-commerce mockups.
• Creating a voice-controlled or chat-driven 3D modeling interface.
• Programmatic rendering of scene variations for testing lighting and materials.

Known limitations

Requires the blender-mcp addon to be installed and active in the Blender instance. Not suitable for real-time animation playback or high-frequency interactive sculpting.