Prompt-driven 3D scene builder connecting Blender to Codex via MCP

What they did

They wanted to stop hand-modeling repetitive props and instead describe scenes in natural language. Using the mcp-for-blender project (formerly blender-mcp), they ran the one-command installer, which installed uv, detected their MCP clients, and offered to configure Codex alongside other apps. They selected Codex, let the script install and enable the Blender addon, then fully quit and reopened the AI app so the new `blender` server entry was picked up. With Blender open (the addon starts its own local server on launch), they began prompting: creating a base scene, adding primitives, positioning and scaling objects, applying materials, and adjusting lighting and camera framing. They iterated conversationally — asking for a tabletop arrangement, then nudging object transforms and colors — and used the agent to inspect the current scene state before each change so edits landed on the right objects. Finally they asked for a render to check the result, then refined proportions and lighting based on what came back.

How it went

The setup was quick and mostly hands-off: one installer command handled uv, client config, and the Blender addon, with backups written for any config file it touched. Prompting produced usable blockout scenes and material/lighting tweaks without manual modeling, which is a solid speedup for prototyping layouts and iterating on composition. Results are best treated as drafts — geometry is simple and needs human cleanup for production-quality assets.

Worth knowing

This is a third-party integration, not an official Blender product. The PyPI package was renamed from blender-mcp to mcp-for-blender; existing configs keep working but new installs should use the new name. You must fully quit and reopen the AI app after setup (on Windows, quit from the system tray), and Blender must be running with the addon enabled for the server to respond. Windows Defender may block the install script, in which case use the manual uv path. Complex or highly precise modeling still needs manual work.

Wiring

Install uv (brew, curl installer, or winget), then run `uvx mcp-for-blender setup`, which detects MCP clients including Codex and adds a `blender` server entry while saving a `.bak` of each modified config. Alternatively configure manually: point the MCP client at the `mcp-for-blender` server launched via uvx. Install and enable the Blender addon (the setup command does this), then restart the AI app completely. Open Blender — the addon starts a local socket server that the MCP server connects to, so the agent can query scene state and issue modeling, material, lighting, and render commands. Order matters: uv first, client config second, addon third, restart app, then launch Blender before prompting.

Try it yourself

Set up mcp-for-blender for my Codex client, then in Blender build a small studio scene: a rounded tabletop, three ceramic mugs of slightly different sizes, a soft key light, and a neutral backdrop. Show me the object list before and after each change, keep everything on a named collection called 'Studio', and finish with a 1080p render so I can review framing and lighting.