Blender farm with MCP support
FXRender is a Blender farm with MCP support. The website is one way in. The fxr command-line tool is the other: upload a .blend, render a frame range, stream the log, and download the stills. It runs on macOS, Windows, and Linux.
fxr mcp starts a local MCP server on your machine. Claude, Cursor, and any other client that speaks MCP can call the farm: check who you are, submit a render, poll the job, and save the frames. A chat website that cannot run a local server cannot. The client has to read the .blend on disk.
Download a build:
On your own computer, fxr login stores the API token in the system keyring. On a server, set FXRENDER_TOKEN for that process instead. Create the token at fxrender.com, under API Tokens.
Getting started
Four steps, start to finish:
- Verify your email. You get 15 minutes of GPU time free, no card needed.
- Upload a
.blend, or a.zipwith the blend plus any packed textures it links to. - Pick a camera, output format, resolution, samples, and frame range, then send it to the farm.
- Watch frames land in your library, then download stills or generate a movie.
Uploading a scene
Uploads go straight from your browser to private, per-account storage. Nobody else can see your files. Once a file lands, it is inspected: frame range, engine, resolution, samples, and every camera are read out of it. Missing linked files, no camera, and unusual settings show up as warnings before you spend any GPU time.
A file with linked textures or other blends needs to go up as a .zip that contains everything it references. A bare .blend with broken links renders with missing textures.
Camera selection
If your scene has more than one camera, you pick which one renders. The scene's active camera is pre-selected. A scene with no camera cannot be sent to the farm. There is nothing to render from.
Render settings
Blender 4.2 LTS, 4.5 LTS, 5.0, and 5.3 Alpha are supported. Cycles runs on GPU. Eevee is also available. Output is written in the format you pick: PNG, JPEG, TIFF, WebP, or EXR. There is no hidden intermediate format.
Multiple GPUs
Every shot starts on exactly one GPU. Extra GPUs start only after that first slice renders successfully, so a broken scene is caught on one box before more spin up. You can then request more GPUs on a running job to split the remaining frames. Each extra box bills a short prep minimum for the download, on top of its render time.
Movies and formats
Once every still in a job has landed, you can cut an MP4 from the sequence at no extra cost. Encoding does not bill GPU time. Only the render is billed.
Cancelling a render
Cancelling a live render stops it after the current frame finishes and reports in. It does not kill Blender mid-frame. Frames already rendered stay in your library and stay billed. Frames that never started are not charged.
Billing and storage
You are billed per GPU-second a render actually uses, drawn from a balance you top up with a one-time pack. There is no subscription. That balance does not expire.
Each pack also sets your storage size for one year from the purchase date. If you do not buy again within that year, the storage cap reverts to the free tier. Existing files are not deleted. New uploads are blocked until you are back under the lower cap, or you buy another pack.
FAQ
Does a render ever fail partway through?
Yes. The usual cause is running out of GPU memory on a very heavy frame. The job stops, and you are billed only for frames that finished.
Can I use a file I do not have the rights to?
No. See the terms of service.
Where do my files go?
See the data policy for storage, processing, and deletion.
Something not covered here?
Email [email protected].