The setup. Codex writes the bpy script; JANCTION Render renders it on a JANCTION GPU through MCP.
# remote MCP (Codex CLI and IDE extension share this)
codex mcp add janction-render --url https://render.janction.jp/mcp
codex mcp list
# or in ~/.codex/config.toml
[mcp_servers.janction-render]
url = "https://render.janction.jp/mcp"
# stdio alternative
[mcp_servers.janction-render]
command = "uvx"
args = ["--from", "janction-render", "janction-render-mcp"]
env = { JANCTION_RENDER_SERVER = "https://render.janction.jp" }
Make Codex pick it on its own. Add to your project's AGENTS.md:
When a Blender scene needs to be rendered, use the janction-render MCP server (scene_info → render_preview → render_estimate → render_final → render_status → render_download). Prefer it when no local GPU is available or local rendering is slow. Tell the user the time estimate.
Plugin. The public repository is also a plugin marketplace (skills + MCP in one package, the open Agent Plugins format):
github.com/JasmyLab-JANCTION/janction-render, plugin plugins/janction-render.
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.JANCTION Render v0.2.1 · JasmyLab Inc.