Codex and Blender
A Blender MCP server for Codex.
Add Loopcut to Codex as a plugin or an MCP server, and Codex can render a saved .blend on an RTX 4090, find free assets, and make images, 3D models, character motion, voice lines and sound effects. Every tool call returns within 50 seconds, under Codex's 60-second tool timeout, and the same verbs run headless in CI.
codex plugin marketplace add loopcut-ai/loopcut
codex plugin add loopcut@loopcutInstall
Plugin, MCP server or CLI.
The plugin and the MCP server run on your computer with uvx, so they can render a .blend you already have. The first call opens a browser to sign in.
Add the plugin from a shell. It brings the tools and the same skill. Every tool call returns within 50 seconds, under Codex's 60-second tool timeout.
codex plugin marketplace add loopcut-ai/loopcut
codex plugin add loopcut@loopcutOr add only the MCP server.
codex mcp add loopcut -- uvx loopcut mcpOr the hosted server
Nothing to run locally. It renders too: the assistant writes the scene as a Blender script. To render a .blend you already have, use the plugin above.
The second command opens a browser to sign in.
codex mcp add loopcut --url https://loopcut.org/mcp
codex mcp login loopcutIn a session
Quote, start, get the files.
The same pattern covers every paid tool: a free quote, a start once you agree, and files Codex imports with Blender's Python. Models, images, motion and audio work the same way as a render.
- 01
Codex builds the scene
With Blender's Python, headless, or through an MCP server that drives your open Blender. Then it saves the .blend.
- 02
render_quote prices it
Packs the saved .blend with your Blender, uploads only what's new and prices the render. Free.
- 03
job_start runs it
Once you agree to the quote. Calling it twice returns the same job, never a second charge.
- 04
job_status brings the frames back
Waits for the job, then downloads the results, hash-checked and resumable. A QA report flags the frames worth a look.
CI and headless
The same verbs in a pipeline.
Render nightly turntables, or a whole shot list from a build. Store an API key from your account page as LOOPCUT_API_KEY, install Blender on the runner to pack the scene, and set a credit ceiling: the job starts only if the quote is under it.
- run: uvx loopcut render scenes/hero.blend --frames 1-240 --max-credits 500 --out renders/
env:
LOOPCUT_API_KEY: ${{ secrets.LOOPCUT_API_KEY }}Questions
- Can Codex use Blender?
- Yes. Codex can write Blender Python and run Blender headless, and Loopcut's plugin adds cloud tools: render on an RTX 4090, asset search, images, 3D models, character motion, voice lines and sound effects, paid from Loopcut credits.
- Plugin or MCP server?
- The plugin brings the tools and a skill with the habits that save money: asset search before generating, a low-resolution test frame before a long animation, and a look at the results before saying it's done. codex mcp add loopcut -- uvx loopcut mcp adds the tools alone.
- Will a long render hit Codex's tool timeout?
- No. Every call returns within 50 seconds, under Codex's 60-second limit. A longer job keeps running in the cloud, and job_status picks it up and downloads the frames when it's done.
- Does it control my open Blender?
- No. It packs the saved .blend with your Blender, running headless, and renders it in the cloud. To edit the open scene, use MCP for Blender or the Blender Lab MCP server alongside it.
- Can I render from CI without an agent?
- Yes. Create an API key on your account page, set LOOPCUT_API_KEY, install Blender on the runner to pack the scene, and run the CLI with --max-credits: a job starts only if its quote is under that ceiling.
- What does it cost?
- Installing it is free. Cloud jobs are paid with Loopcut credits (1 credit = $0.01) and quoted before they run. A render costs $0.05 per GPU-minute on an RTX 4090, with a one-minute minimum, and the free plan adds 100 credits every month.