Vol. 1 · No. 303Blender 3.6 / 4.2 / 4.5 / 5.0 / 5.2 / 5.3Cycles · EEVEE
JANCTION
Render · Blender on RTX PRO 6000 · Tokyo
0.1 JPYper GPU-secondFirst 100 JPYfree, no card
Front page / Render Blender scenes from Claude.ai

Render Blender scenes from Claude.ai

In Claude.ai, add https://render.janction.jp/mcp as a custom connector (Plugins (older menu: Customize → Connectors) → Add custom connector). Press Connect, and a free key is created. Then describe a scene: Claude writes the bpy script, previews it on a JANCTION GPU in a few seconds and renders the final MP4. Each new key starts with a welcome credit of up to 500 JPY (14 days); after that, previews stay free up to 2 GPU-minutes a day and finals cost 0.1 JPY per GPU-second.

Updated 2026-11-12

What it does From an AI app over MCP: the bpy script the AI wrote, or your own .blend or 3D file, rendered on a cloud GPU. Preview, fix, estimate, then the final. The price is shown before rendering, and a paid render starts only after you approve it. Without a connector, let the AI write the script and paste it at /start.
What it does not do Not a tool for editing 3D inside that app (a local Blender is driven by a separate MCP such as blender-mcp). Until it is connected and authenticated, the AI cannot render.

Paste your AI's script and tryTry your own file for free

Browser only; no connector or CLI needed. A 100 JPY welcome credit for a new key (14 days, no card; one per network every 30 days, further keys on the same network share what is left), and 400 JPY more for saving a card that is not charged (once per card); after that, previews stay free up to 2 GPU-minutes a day and finals cost 0.1 JPY per GPU-second.

Setup

  1. Claude.ai → Plugins (older menu: Customize → Connectors) → Add custom connector.
  2. Name "JANCTION Render", URL https://render.janction.jp/mcp, Add.
  3. Press Connect. The consent page creates a free API key (no account, no card).
  4. In a chat, make sure the connector's tools are enabled and ask.

On a Claude Team or Enterprise plan, only an owner can add a custom connector for the organization; ask the owner to add the URL above once, then each member presses Connect and gets their own free key.

Claude does not pass files you attach in the chat to connectors. For a .blend on your computer, drop it at /upload and paste the link into the chat.

Prompt to try

Using JANCTION Render, build a glossy red cube rotating on a gray floor and show me a 4-frame preview.
If it looks right, render 24 frames at 1280x720 as an MP4.

To render a .blend or 3D file that is on your computer, drop it at /upload to get a 12-hour link (no sign-up) and tell the AI "Render this file: <link>". To test the connection first: "Render a preview of https://render.janction.jp/samples/cube_scene.py".

What Claude does

  1. scene_info reads the scene without rendering: cameras, frame range, objects, missing files.
  2. render_preview renders 1-4 frames at 720p in a few GPU seconds and returns the image, so the agent can look, fix the script and try again.
  3. render_estimate says how long the final render takes ("about 3 minutes") and whether it fits the free GPU time left (the welcome credit while it lasts, then up to 2 preview GPU-minutes a day).
  4. 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.
A 4-frame preview rendered by JANCTION Render (a rotating red cube)
The 4-frame preview Claude.ai got from that prompt: 4 GPU seconds. The 24-frame 720p MP4 that followed took 58 GPU seconds (2026-10-01, RTX PRO 6000).

A 40-second recording of this exact flow: demo.mp4.

How long it takes

jobGPU timenote
preview, 4 frames (720p split in 4 tiles, 16 samples, denoised)about 4 sround trip about 8 s; the image comes back inline
final, 24 frames at 1280x720, 64 samples → MP4about 60 smeasured 2026-09-30 / 10-01 (59 s and 58 s)
final, one 1920x1080 frame at 128 samplesabout 11 sthe estimator's baseline; heavy scenes take longer

These are individual observations of simple scenes (2026-09-30 to 10-01 UTC, NVIDIA RTX PRO 6000 Blackwell Max-Q Workstation Edition, 96 GB). The 4-GPU-second example used a rotating cube, four 640x360 tiles and 16 samples. GPU time includes Blender startup and scene loading; it is distinct from completion time including queue and transfers. See conditions, round trips and reproduction files. These are not speed guarantees.

render_estimate gives the number before rendering; once a scene has been rendered once, the estimate uses that scene's own measurement.

Free limits

Pricing (since 2026-10-08): Each new key gets 100 JPY of GPU time free with no card (1,000 GPU-seconds, 14 days) for previews and finals, and 400 JPY more once a card is saved on a Stripe page that charges nothing (once per card): up to 500 JPY in all. After it is used up or expires, previews are free up to 2 GPU-minutes per key per day and final renders are paid from prepaid credit at 0.1 JPY per GPU-second. Top-ups (paid) start at 100 JPY. The first top-up during the 14-day welcome period counts 1.5x, with the bonus capped at 500 JPY (100 JPY buys 150 JPY of credit). Top-ups of 2,000 JPY or more get 10 to 20% extra (not combined with the first-top-up bonus; the larger one applies). Top-up bonuses are separate from the welcome credit and the card-saving credit. Payment is on a Stripe Checkout page. One full welcome credit per network every 30 days; further keys from the same network use what is left of that network's credit. A job without enough credit gets HTTP 402 payment_required with a checkout_url. Final renders go up to 3,000 frames per instruction (automatically split internally under one job id), 1080p (1920x1080) on free time and up to 4K (3840x2160) on prepaid credit. The free preview time resets at 00:00 UTC (09:00 JST). No sign-up: connecting creates a key. Inputs and results are deleted 24 hours after last use (normally 7 days for keys that have paid 500 JPY or more in total) and never used for training.

Claude Code and the desktop app

Claude Code (terminal) uses claude mcp add --transport http janction-render https://render.janction.jp/mcp or the stdio server for local files; see Claude Code + Blender. The Claude desktop and mobile apps share the connectors you add on claude.ai.

Without a connector

If you cannot add a connector to your AI (plan or administrator settings), the same result is one step away: send the prompt below to the AI and paste the code it returns into the paste-and-render page. The preview needs no payment.

Write a Blender 5.0 bpy script that builds <describe your scene here>. Add a camera and set scene.camera, and add one light. Do not call render and do not change render settings. Reply with the code only.

To fix something, give the AI the preview's notes (too dark, cut off, no light) and paste the rewritten script again.

FAQ

Which Claude plans can add custom connectors?

Custom connectors are available on paid Claude plans (Pro, Max, Team, Enterprise) as of October 2026; check Anthropic's help center for the current list.

Does Claude see the rendered image?

Yes. render_preview returns the image inline, so Claude can judge the camera, lighting and materials and fix the script before the final render.

Where do I get the MP4?

render_download returns links that need no key and work for about 24 hours (call it again for fresh links; files stay 24 hours after last use, 7 days, normally, for keys that have paid 500 JPY or more in total). Open them in the browser or let Claude show them.

Related

Overview · All guides · llms.txt