The setup. Claude Code can write and edit a bpy script (or a .blend through a local Blender MCP), but rendering needs a GPU. JANCTION Render executes the render on a remote GPU through MCP and hands the result back to Claude Code.
# remote (nothing to install; OAuth creates a free key) claude mcp add --transport http janction-render https://render.janction.jp/mcp # or stdio (sends local files, saves results locally) claude mcp add janction-render -e JANCTION_RENDER_SERVER=https://render.janction.jp -- uvx --from janction-render janction-render-mcp # plugin with the workflow skill /plugin marketplace add JasmyLab-JANCTION/janction-render /plugin install janction-render@janction-render
Then ask. "Build a small street scene in Blender with a camera fly-through and render a 24-frame preview with janction-render."
What Claude Code does.
scene_info reads the scene without rendering: cameras, frame range, objects, missing files.render_preview renders 1-4 frames at 720p in a few GPU seconds and returns the image, so the agent can look, fix the scene and try again.render_estimate says how long the final render takes ("about 3 minutes") and whether it fits today's free quota.render_final renders the frames on GPUs and joins them into an MP4; render_status reports the remaining time; render_download returns the files or links.Tips for scripts. Always add a camera and a light and set the frame range; do not change render settings or call
bpy.ops.render.render; procedural materials work, external images must be packed into a .blend.
See the sample cube_scene.py.
JANCTION Render v0.2.1 · JasmyLab Inc.