OpenApps

JANCTION Render MCP server — tools & history

JANCTION Render MCP server: observed open status, tool schemas, linked apps and version history.

JANCTION Render

Endpoint: https://render.janction.jp/mcp

Observed status: open. Checked: 2026-10-13T05:10:10+00:00.

Linked apps

  • JANCTION Render

    JANCTION Render is a cloud GPU render farm for Blender that AI agents call as an MCP server or HTTP API. From Cursor, send a .blend file, a bpy script or a 3D file (glTF / FBX / USD), preview in seconds, and get frames or an MP4 back from JANCTION's NVIDIA GPUs. No local Blender or GPU is needed. Remote MCP with OAuth. Free up to 500 JPY of GPU time per new key, then 0.1 JPY per GPU-second (previews free up to 2 GPU-minutes a day); operated by JasmyLab Inc.

Observed tools

  • asset_search — Find free CC0 3D models, PBR textures or HDRIs on Poly Haven by words ('wooden chair', 'forest hdri') to furnish a scene without uploading files; no GPU time. For product shots of something the user has no model for: asset_search('<item>'), then render_preview(scene_script='import jr_assets; jr_assets.import_model("<id>")', asset_urls=['polyhaven:<id>'], preset='product') gives 4 studio shots on a plain backdrop. Each result has a spec 'polyhaven:<id>' to pass in asset_urls, its size in metres and the entry file. In the scene script: import jr_assets, then jr_assets.import_model('<id>', location=(x, y, z), scale=1.0) returns the objects, jr_assets.material('<id>') builds a material and jr_assets.apply(obj, mat) assigns it, jr_assets.world_hdri('<id>', strength=1.0) lights the world. 'polyhaven:<id>@2k' fetches 2k textures (1k by default).
  • billing — Check what this key can still render for free and its credit (no GPU time): the free GPU time left and when it expires or resets (each new key gets 100 JPY of GPU time free with no card (14 days) and 400 JPY more once the user saves a card on a page that charges nothing (once per card); after that, previews are free up to 2 GPU-minutes a day and finals cost 0.1 JPY per GPU-second (prepaid)), the balance in yen, the price per GPU-second, any pending checkout link, and card_offer / autocharge_offer when they apply. Relay tell_user to the user in their language when it is present.
  • render_cancel — Cancel a queued or running JANCTION render job. GPU time after the cancel is not used.
  • render_download — Get the download links of a job (no key needed, valid about 24 hours) and show them to the user; in a terminal, fetch them with curl -o. A finished preview also comes back as an inline image. wait_seconds > 0 first waits for the job (the service waits at most 50 s per call; call again while it is still running). only picks the files: 'output' (default: the MP4 or the preview sheet, plus the first frames), 'mp4', 'sheet', 'frames' or 'all'.
  • render_estimate — Estimate a render before starting it (no GPU time): GPU seconds, queue wait, the wall-clock time as text (estimate.human, e.g. 'about 3 minutes') and whether it fits the free GPU time left (the welcome credit, or 2 preview GPU-minutes a day after it) and the size limits. Call it before render_final when the time or quota is uncertain, the job is longer than about 24 frames or above 720p, or the user asks how long it takes; tell the user the result. With scene_id the estimate uses this scene's measured render times; it also says when to split a job.
  • render_final — Render the final frames or video of a Blender scene on cloud GPUs, after the user approved a preview: 'render the final', 'make the video', 'export the turntable MP4'. Call render_estimate first when the time or the free GPU time left (the welcome credit, or 2 preview GPU-minutes a day after it) is uncertain, the job is longer than about 24 frames or above 720p, or the user asks how long it takes, and tell the user. Long jobs are rendered in chunks and joined into one video. Returns job_id and estimate.human at once (short jobs return the links directly); then call render_download(job_id, wait_seconds=45). When not to use: editing a scene open in the user's Blender belongs to a local Blender MCP, and a single still on a machine with its own NVIDIA GPU usually renders faster locally. Use the same environment and blender as the approved preview. Limits: up to 240 frames and 1920x1080 per job; each new key gets 100 JPY of GPU time free with no card (14 days) and 400 JPY more once the user saves a card on a page that charges nothing (once per card); after that, previews are free up to 2 GPU-minutes a day and finals cost 0.1 JPY per GPU-second (prepaid); ask the user before a render that the free time does not cover; files are deleted 24 hours after last use. preset='product' | 'turntable' | 'animation' fills the settings for that purpose. Options on each parameter: output (png, exr, mp4, webm, prores, gif, webp), orbit=True (turntable MP4), cameras (one image per named camera), transparent, engine='eevee', notify_url (one POST when done), asset_urls with 'polyhaven:<id>'. Pass scene_id from render_preview, or scene_script / scene_url for a new scene.
  • render_info — Show the JANCTION Render service state: whether GPU workers are online, queue length and expected wait, this key's usage, and how to connect from other clients. Call this if renders seem stuck or before the first render. Use it to decide whether to route a render here: workers_available > 0 means a preview comes back in seconds; gated means the GPU is lent out and 'gate' says how long the wait usually is.
  • render_preview — Show what a Blender scene looks like: a fast, low-cost preview render on a cloud GPU, back as an image in seconds. Typical requests: 'render this .blend', 'show me the scene', 'preview the turntable', 'I have no GPU', 'Blender is too slow on my laptop', 'Blenderでレンダリングして', 'GPUがない', 'ターンテーブル', '商品の360度動画'. Also use it after writing a bpy script, to see what it builds. Each preview returns a critic verdict (ok / check / fix) with fix code: apply the fixes and preview again before any final render. It also returns final_estimate (the same scene as a 1080p final) and quota_left_today; tell the user both before asking to go on. A script that raises comes back as a failure with the line (nothing is rendered). When not to use: editing a scene open in the user's Blender belongs to a local Blender MCP, and a single still on a machine with its own NVIDIA GPU usually renders faster locally. This service is for CPU-only machines, animations, and scripts with no Blender installed. Limits: up to 1280x720; 1-4 frames tiled in one labeled image for the GPU time of one 720p frame. preset='product' | 'turntable' | 'animation' sets camera, light, backdrop and frames for that purpose. Other options are explained on each parameter: environment presets and 'compare', orbit (turntable), cameras (several named cameras), engine, transparent, asset_urls with 'polyhaven:<id>' CC0 assets. Give the scene as scene_script (bpy code as text), scene_url (an https link to a .blend, .py or 3D file) or scene_id; reuse the returned scene_id in render_final.
  • render_share — Publish a finished render as a public page the user can send to anyone (X, Discord, a client): the image or video, the render conditions, an optional title and note, and the bpy script if include_script=True. The page keeps a copy of the result after the job's 24-hour expiry, until render_unshare. listed=True asks for it to appear in the public gallery (/gallery) after the operator reviews it; until then the page is not indexed by search engines. prompt: what the user asked you, in their words (shown as 'what the user asked the agent'; it makes the page useful to others). Ask the user before sharing; return the url to them.
  • render_status — Check a render job: status (queued / running / done / failed / canceled), frames done, the ETA (eta.human, including queue wait), files ready, Blender warnings, and the error with the log tail if it failed. Use it to report progress to the user; render_download(job_id, wait_seconds=45) waits and returns the links in one call.
  • render_unshare — Remove the public share page of a job (the copy of the result is deleted).
  • scene_info — Read a Blender scene without rendering (a few seconds, no GPU time): cameras and the active one, frame range and fps, resolution, objects by type, lights, materials, whether it is animated, and missing linked files that would render pink. Use it for a .blend you did not write, or to check what a bpy script built. Returns scene_id; pass it to render_preview and render_final instead of sending the scene again.

Data as of 2026-10-13T05:10:10+00:00.

OpenApps records store listings and observed changes. Store ranks are not download counts; launch dates may be derived or use the first observation. Coverage gaps are shown in the interactive catalog.

REST API specification · Guide for AI clients · Manage API keys and MCP connections