
Janction Render
io.github.JasmyLab-JANCTIONv0.2.1Updated Oct 1, 2026
Render Blender scenes (.blend or bpy script) on JANCTION GPUs from AI agents: previews, frames, MP4.
Overview
Renders Blender scenes on JANCTION cloud GPUs, returning preview frames, estimates, and final PNG or MP4 output.
- What it does
- Lets an assistant submit a .blend file, a bpy scene script, or a scene URL and render it on remote GPUs. Tools include scene_info for inspecting cameras, frame range and missing files without rendering; render_preview for up to four low-cost tiled frames; render_estimate for GPU seconds, queue wait and quota fit; render_final for PNG or MP4 output; render_status, render_download and render_cancel for job control; plus billing and render_info for quota and worker availability. A CLI exposes the same operations.
- When to use it
- Useful when you want Blender renders without a local GPU, when local rendering is slow, or when an agent should iterate on a scene by previewing, adjusting, and re-rendering. It fits agent workflows that build scenes from bpy scripts and need quick visual feedback before a final render.
- Requirements
- Remote option: connect to the Streamable HTTP endpoint with OAuth 2.1 or a Bearer API key, nothing to install. Local stdio option: Python with uvx or pip, and the JANCTION_RENDER_SERVER URL (default A temporary API key is issued automatically on first use and cached locally; JANCTION_RENDER_API_KEY can pin one. Network access is required.
Installation
In SourceWeft
- Open Janction Render in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"janction-render": {
"type": "http",
"url": "https://render.janction.jp/mcp"
}
}
}README
JANCTION Render
[JasmyLab-JANCTION/janction-render MCP server]
A cloud GPU render farm for Blender, built for AI agents. Render Blender scenes on JANCTION GPUs from Claude, ChatGPT, Claude Code, Codex, Cursor or any MCP client: an MCP server (remote and stdio) plus a CLI. Use it to render Blender without a GPU, or when rendering locally is slow.
- Input: a
.blendfile, or a bpy Python script that builds the scene (no local Blender needed). scene_inforeads the scene without rendering (cameras, frame range, missing files).render_previewreturns 1-4 low-cost frames tiled in one image within seconds, so the agent can look, fix, and repeat.render_estimatesays how long a render will take ("about 3 minutes") and whether it fits today's free quota.render_finalrenders the frames on GPUs and joins them into an MP4;render_statusreports the remaining time.- Free beta: no charges. Each key gets 10 GPU-minutes per day; a final render is up to 240 frames at 1080p. Paid plans (per GPU second, prepaid credit) will be announced on the service page before they start.
- Inputs and results are deleted 24 hours after last use and are never used for training.
Status
Free beta. Service page: https://render.janction.jp (/v1/health, /llms.txt). Blender 5.0, Cycles on GPU.
Connect (remote MCP, nothing to install)
MCP server URL: https://render.janction.jp/mcp (Streamable HTTP). Auth is OAuth 2.1 with dynamic client
registration: pressing "Connect" opens a page that creates a free API key (or takes one you already have). A raw API key
also works as Authorization: Bearer jr_....
Remote tools take scene_script (bpy code as text), scene_url (an https link to a .blend or .py) or scene_id;
results come back as an inline image plus download links that need no key and work for about 24 hours.
Claude Code plugin (the remote connector plus a skill with the workflow):
Install (stdio MCP, sends local files)
The package is on PyPI as janction-render.
Codex: add to ~/.codex/config.toml
A temporary API key is issued automatically on first use and cached in ~/.janction-render.json; set
JANCTION_RENDER_API_KEY to pin one (quota and, later, credit belong to the key). The same key can be used from the
remote connector: paste it on the connect page.
Then, in Claude Code:
Build a small street scene in Blender with a camera fly-through and render a preview with janction-render.
Tools
CLI: janction-render inspect|preview|render|status|download|cancel|jobs|balance|topup|info.
Writing a scene script
The service sets engine (Cycles), resolution, samples and denoising; your script sets the scene, camera and frame range.
Scripts run in an isolated container with no network. See samples/cube_scene.py.
HTTP API
During the free beta a 429 quota_exceeded response carries resets_at; a 400 beta_limit means the job is too big
(split it). Once paid plans start, a 402 payment_required response carries checkout_url.
Self-hosting
The server (FastAPI + SQLite, with the remote MCP endpoint) and the worker (Blender in disposable Docker containers,
--network none --cap-drop ALL) live in the internal repository and are not part of this package yet. This repository
holds the client side: stdio MCP server, CLI, HTTP client, samples and the Claude Code plugin.
MCP registry
This server is listed in the official MCP registry as io.github.JasmyLab-JANCTION/janction-render (remote: https://render.janction.jp/mcp).
mcp-name: io.github.JasmyLab-JANCTION/janction-render
License
MIT (see LICENSE). Operated by JasmyLab Inc.
Source: README.md at commit 5b9c716
Tools
0Version history
1- v0.2.1LatestOct 1, 2026


