The problem. A classic render farm is built for humans: you upload a .blend through a web form, wait, and download. An AI agent that just wrote a Blender scene cannot click through that. It needs a tool it can call, an image it can look at, and a time estimate it can tell the user.
How JANCTION Render works. It is a render farm exposed as an MCP server. The agent sends a .blend or a bpy script, gets a preview back inline, fixes the scene, asks the user, then renders the final frames on JANCTION GPUs (NVIDIA, Cycles). Frames are split across GPUs and joined into an MP4. Results come back as files (stdio) or as links valid for 24 hours (remote).
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.Connect.
| from | how |
|---|---|
| Claude.ai | Settings → Connectors → Add custom connector → https://render.janction.jp/mcp |
| ChatGPT | Settings → Connectors → Advanced → Developer mode → Create → https://render.janction.jp/mcp (OAuth) |
| Claude Code | claude mcp add --transport http janction-render https://render.janction.jp/mcp |
| Codex | codex mcp add janction-render --url https://render.janction.jp/mcp |
| Cursor and other MCP clients | Streamable HTTP at https://render.janction.jp/mcp; OAuth or Authorization: Bearer <api key> |
Limits and price. Free beta: 10 GPU-minutes per key per day, final renders up to 240 frames at 1080p. Nothing is charged. Inputs and results are deleted 24 hours after last use and never used for training. Paid plans (per GPU second, prepaid credit) will be announced on this site before they start.
JANCTION Render v0.2.1 · JasmyLab Inc.