Does Cursor need Blender installed?
No. The remote MCP server runs Blender (5.0 by default, 5.2 or 5.3 on request) on a JANCTION GPU; Cursor only writes the script and calls the tools.
In Cursor, add the MCP server https://render.janction.jp/mcp (the button below or Settings → Tools & MCP → Add). Cursor's agent then has 13 render tools: it writes a bpy script, calls render_preview, looks at the image, fixes the scene, and calls render_final for the 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-17
What it does Your own .blend, bpy script or 3D file (glTF/GLB, FBX, USD, OBJ...) rendered to images or video on a cloud NVIDIA GPU, from an AI app, the terminal or the browser. The first preview needs no payment.
What it does not do It does not speed up the Blender viewport on your machine, does not take non-Blender video, simulations or general GPU jobs, and an AI that is not connected cannot render on its own.
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.
One click: Add to Cursor Add to VS Code Add to LM Studio. Cursor opens, shows the server, and you confirm. The first tool call opens the OAuth consent page, which creates a free key.
By hand, in ~/.cursor/mcp.json (global) or .cursor/mcp.json (per project):
{
"mcpServers": {
"janction-render": { "url": "https://render.janction.jp/mcp" }
}
}
Settings → Tools & MCP should list janction-render with its tools (scene_info, render_preview, render_estimate, render_final, render_status, render_download, render_cancel, render_share, render_unshare, asset_search, billing, render_info). If the auth step did not open, click the server and choose Login.
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".
Or, with an existing file: "Upload scene.blend from this project to JANCTION Render, preview frame 1, then render frames 1-48 at 1080p as an MP4." (Remote tools take an https URL or a bpy script; to send a local .blend from Cursor, let the agent run the CLI: pip install janction-render, then janction-render render scene.blend --frames 1-48 --wait.)
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 script and try again.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).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.
| job | GPU time | note |
|---|---|---|
| preview, 4 frames (720p split in 4 tiles, 16 samples, denoised) | about 4 s | round trip about 8 s; the image comes back inline |
| final, 24 frames at 1280x720, 64 samples → MP4 | about 60 s | measured 2026-09-30 / 10-01 (59 s and 58 s) |
| final, one 1920x1080 frame at 128 samples | about 11 s | the 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.
401 on the first call: finish the OAuth consent in the browser window Cursor opened; a free key is created there.402 payment_required: the job goes past the free GPU time left (the welcome credit while it lasts, then up to 2 preview GPU-minutes a day) and the credit is short; show the user checkout_url, or render a smaller job. 400 beta_limit: split the instruction (up to 3,000 frames per instruction (automatic internal parts), 1080p on free time and 4K on prepaid credit).environment='studio' or add a camera and a sun (see bpy rules).Delete the janction-render entry from mcp.json (or the server from Settings → Tools & MCP). To revoke the key the consent page created: POST https://render.janction.jp/v1/keys/revoke with the key, or disconnect the app under /v1/connections.
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-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.
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.
No. The remote MCP server runs Blender (5.0 by default, 5.2 or 5.3 on request) on a JANCTION GPU; Cursor only writes the script and calls the tools.
The remote tools take an https URL or a bpy script. For a local .blend, let the agent use the CLI (pip install janction-render) or the stdio MCP server, which uploads the file.
Yes. It is a cursor:// deep link; Cursor opens and asks you to confirm the server. If nothing happens, paste the mcp.json entry instead.
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 from prepaid credit. Every estimate says what a job would be charged (cost.estimated_yen); see the pricing page.