Blender render farm · over MCP

Your agent writes the scene.
We render it.

makerhouse is a cloud Blender renderer behind one MCP server. Ask Claude Code, Codex or OpenCode for a shot, and it comes back as a finished MP4, rendered on cloud GPUs. No GPU on your desk, no render queue to babysit.

Free sandbox: 60 GPU-minutes every month. No card to join the list.

claude · ~/shorts/coffee-ad
› make a 6s 9:16 hero shot: coffee cup on oak table,
  slow push-in, morning light, render it

● Writing scene coffee_hero.py (camera dolly, area light, oak material)
⏺ makerhouse.render_animation
  file   coffee_hero.blend   engine cycles
  frames 1–144 @ 24fps   size   1080×1920
⏺ makerhouse.job_status  rendering 96/144 ▮▮▮▮▮▮▮▯▯▯
⏺ makerhouse.get_output
  ✓ coffee_hero.mp4 · 6.0s · 41 GPU-min · $0.00 (sandbox)
  https://out.makerhouse.id/j/7f3a…/coffee_hero.mp4

Works with any MCP client

Agents can already build a Blender scene.
Rendering it is where the session stalls.

Laptops choke.

A 30-second Cycles shot can hold a consumer GPU for hours. Your agent waits, and so do you.

Render farms are built for people.

Upload plugins, dashboards and per-GHz pricing. None of it is something an agent can call.

Local MCP stops at your machine.

Today's Blender MCP tools drive the Blender on your desk. The heavy part still runs there.

How it works

One tool call from prompt to MP4

  1. 01

    Connect once

    Add the makerhouse MCP server to your agent with one command. Your key stays in the agent's config.

  2. 02

    Agent builds the scene

    Your agent writes or edits the .blend with Python, or uploads one you made. Assets go up with it.

  3. 03

    We split and render

    The job is cut into frame ranges and rendered in parallel on cloud GPUs with headless Blender.

  4. 04

    MP4 comes back

    The agent gets a preview frame, the encoded MP4 and the cost, then can tweak and render again.

Setup preview

Paste one line into the agent you already use

makerhouse is a remote MCP server over HTTP. Early-access members get a key and the live endpoint; the commands below show what setup will look like.

  • render_animation render a frame range to MP4
  • render_still one frame, for quick look-dev
  • upload_assets .blend, textures, HDRIs, audio
  • estimate_cost GPU-minutes before you commit
  • job_status / get_output progress and files
# terminal
claude mcp add --transport http makerhouse \
  https://mcp.makerhouse.id/mcp \
  --header "Authorization: Bearer $MAKERHOUSE_KEY"

Made for creators

What people will render with it

Vertical 3D shorts

9:16 product hero shots and loops for Reels, TikTok and Shorts, rendered in batches.

Faceless explainers

Agent-written scenes for each beat of a script, rendered and cut together in one session.

Launch films

Camera moves around a 3D model of your product for a release post.

Music visualisers

Geometry nodes driven by audio, rendered at full length without tying up your machine.

Pricing

Pay for GPU-minutes, not for idle machines

One GPU-minute is one minute on an L40S-class GPU. Billed per second of actual render time. Prices are planned for launch and may change before general availability.

Sandbox

$0

60 GPU-minutes / month

  • Up to 1080p
  • Eevee and Cycles
  • 1 GPU at a time
  • Small watermark
Join the list

For most creators

Creator

$19/mo

500 GPU-minutes / month

  • Up to 4K, no watermark
  • 2 GPUs in parallel
  • Outputs kept 30 days
  • Extra: $0.045 / GPU-minute
Get early access

Studio

$79/mo

2,400 GPU-minutes / month

  • 8 GPUs in parallel
  • Priority queue
  • 3 agent keys
  • Extra: $0.038 / GPU-minute
Get early access

Scale

Custom

Reserved GPUs

  • Dedicated capacity
  • Private asset storage
  • SLA and invoicing
  • For studios and platforms
Talk to us

Estimate a shot

Frames720
GPU-minutes300
Wall-clock on 8 GPUs≈ 38 min
Cost as Creator overage$13.50

Fits inside the Creator plan's monthly minutes.

Seconds per frame are typical figures for 1080p on an L40S-class GPU. Your scene may be faster or slower; estimate_cost renders a sample frame to tell you before you commit.

Where makerhouse fits

Your own GPUClassic render farmmakerhouse
Your agent can start a renderYes, locallyNoYes, over MCP
Parallel GPUs1ManyUp to 8, more on Scale
How you payHardware + powerGHz-hours or machine-hoursGPU-minutes, per second
Machine busy while renderingYesNoNo
Returns an encoded MP4If you set it upUsually frames onlyYes, plus preview frame

Questions

Is this live today?

Not yet. We are opening the MCP server to an early-access group first. Join the list and we'll send your key when your slot opens.

Which Blender versions and engines?

We plan to start with the current Blender LTS and the latest release, with Cycles (GPU) and Eevee. Tell us on the form if you need an older version.

Do I need Blender installed?

No. Your agent can write the scene as a Python script that we run in headless Blender. If you have Blender, you can also upload your own .blend.

Can I use add-ons and custom assets?

Assets you upload (textures, HDRIs, models, audio) are packed with the job. Popular add-ons will be pre-installed; tell us which ones you rely on.

Who owns the renders?

You do. We store outputs only so you can download them, and delete them after the retention period of your plan.

What if a render fails?

Minutes spent on a job that fails on our side are refunded automatically. The agent gets the Blender log so it can fix scene errors itself.

Early access

Be one of the first 200 creators to render through your agent

Tell us which agent you use and what you want to render. We'll reply with a key and your free sandbox minutes when your slot opens.

Opens your email app with this filled in, addressed to hello@makerhouse.id.