A community MCP bridge connects an agent to Blender through an installed add-on. For Codex, 4 routes are explicitly documented by the integration maintainer.
A community server and Blender add-on exposing scene and object operations.
Platforms: macOS, Windows, Linux
The integration documentation explicitly names this client.
Blender, uv, MCP server and enabled Blender add-on.
Arbitrary Python execution is available. Review safe-mode documentation. External generation services are optional and may require accounts.
Blender’s command line supports background rendering and Python automation.
Platforms: Windows, macOS, Linux
The native interface is documented, but no setup for this coding agent is established by this source.
An installed Blender executable, project files and any script or render dependencies.
Background operations run in a separate Blender process rather than controlling the open editor session.
A Blender add-on and local server for scene editing, modeling and rendering.
Platforms: Windows, macOS, Linux
The integration documentation explicitly names this client.
Blender 4.2 LTS or Blender 5.0; the Blender add-on and MCP server.
The add-on must be enabled in a running Blender session; optional generation backends have additional dependencies.
A Blender add-on and MCP server for scene creation and interactive modeling.
Platforms: Not documented
The integration documentation explicitly names this client.
Blender 4.5 or newer with the BlendRelay add-on and a compatible MCP client.
Blender and the add-on must remain open and connected; some generation workflows use external models.
A Blender add-on and server for scene work in the editor or headless renders.
Platforms: macOS, Linux
The integration documentation explicitly names this client.
Blender 3.6 or newer, Python 3.10 or newer, and the companion add-on.
The quick-start scripts target macOS and Linux; headless operations run separately from the live editor.
An MCP server and Blender addon support scene and object operations.
Platforms: macOS, Windows, Linux
MCP support suggests compatibility; this client is not documented by the maintainer.
Blender 5.1 or newer, Python 3.13 or newer, pipx and the Blender addon.
The Blender addon and server must both be running for a live connection.
A Blender Lab add-on and MCP server connect an AI client to the Blender Python API.
Platforms: Not specified
The documentation describes general MCP client support but does not name this agent.
Blender 5.1 or newer, the Blender Lab add-on, an MCP server and an AI client.
The server can execute generated Python code in Blender; the Blender Lab documentation warns that it has no safeguards for sensitive data.
| Integration | Codex compatibility | Requirements |
|---|---|---|
| MCP for Blender | Documented setup Setup guide | Blender, uv, MCP server and enabled Blender add-on. |
| Blender command line | Not documented | An installed Blender executable, project files and any script or render dependencies. |
| Blender MCP · RFingAdam | Documented setup Setup guide | Blender 4.2 LTS or Blender 5.0; the Blender add-on and MCP server. |
| BlendRelay MCP | Documented setup Setup guide | Blender 4.5 or newer with the BlendRelay add-on and a compatible MCP client. |
| Blender MCP · djeada | Documented setup Setup guide | Blender 3.6 or newer, Python 3.10 or newer, and the companion add-on. |
| Blender MCP · josuemontano | MCP compatibility (inferred) | Blender 5.1 or newer, Python 3.13 or newer, pipx and the Blender addon. |
| Blender Lab MCP Server | MCP compatibility (inferred) | Blender 5.1 or newer, the Blender Lab add-on, an MCP server and an AI client. |
The sources establish the capabilities listed above, not complete application coverage. Check each bridge’s limitations and your application version before starting.
Choose a route that explicitly documents Codex and matches your environment. Start with the maintainer’s setup guide and a disposable project copy. Shared MCP support alone is listed as an inference.
All Blender integrations