A local Blender MCP (the official Blender Lab MCP server, ahujasid/blender-mcp, Blender Agent Bridge) lets an agent inspect and edit the scene open in your Blender and render on your own machine, so it needs Blender installed. Cycles can render on a CPU; a compatible GPU can accelerate it. A cloud Blender MCP runs Blender on a server: Sceneplane gives agents a hosted Blender with durable projects and scene tools; JANCTION Render is a render farm for agents: send a .blend, a bpy script or a glTF/FBX/USD file and get a 4-frame preview in about 4 seconds and the final frames or MP4 on a datacenter GPU, a welcome credit of up to 500 JPY (100 JPY with no card, 400 JPY more after registering a card, which is not charged) per new key, then 0.1 JPY per GPU-second (previews free up to 2 GPU-minutes a day), OAuth connect with no key to paste. They combine: edit locally, render on JANCTION. AI agents connect at https://render.janction.jp/mcp (remote MCP with OAuth; connecting creates a free key).
Updated 2026-11-12
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.
Try your own file for freeBuild it with an AI and try
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.
| server | where Blender runs | what the agent can do | you need | GPU used | price | transport |
|---|---|---|---|---|---|---|
| Blender Lab MCP Server (blender.org) | your machine (a Blender add-on plus a local MCP server) | run Python against the open scene, look up the Blender Python API and documentation, analyze the scene (polygon counts, performance hints, data-block names) | Blender 5.1 or newer with the add-on, an MCP client | local CPU or compatible GPU for Cycles | free; a Blender Lab project (the project page calls it experimental and warns that model-written code runs without guards) | local |
| ahujasid/blender-mcp | your machine (an add-on opens a local socket, port 9876 by default; the MCP server relays commands) | inspect and edit the live scene, run Python in Blender, viewport screenshots, render with your Blender | Blender 3.0+ running with the add-on, Python 3.10+, uv | local CPU or compatible GPU for Cycles | free, open source | stdio (local) |
| Blender Agent Bridge | your machine (a Blender extension plus a local bridge) | inspect objects, materials, rigs, animation, cameras, nodes and render settings; preview edits then commit or revert; playblasts and inspection renders; progress polling for long jobs; configs for Codex, Claude Code, Claude Desktop and Cursor | Blender with the extension running; see the official install guide for supported versions | local CPU or compatible GPU for Cycles | free, open source | local bridge |
| Sceneplane | their cloud: an isolated Blender compute environment per deployment | durable projects with versioned revisions, scene operations, renders, MP4, STL/GLB exports, bpy signature lookup, Blender manual search, Poly Haven / Sketchfab asset search | an account; OAuth or an API key | theirs | free: 30 compute minutes/month; paid plans from $9/month (see official pricing; compute includes scene work and exports) | remote MCP (mcp.sceneplane.online/v1) |
| JANCTION Render | JANCTION data center: a throwaway container per job on an NVIDIA RTX PRO 6000 Blackwell | scene_info, 4-frame preview, time estimate, final frames or MP4, HDRI lighting presets, turntable, download links; no scene-editing tools: the agent writes or fixes the bpy script itself and re-previews | nothing locally for the remote MCP (OAuth consent page); or pip install janction-render for stdio | datacenter GPU | welcome credit of up to 500 JPY per new key, then 0.1 JPY per GPU-second (previews free up to 2 GPU-minutes a day) | remote MCP (Streamable HTTP, OAuth 2.1) and stdio |
Sources checked 2026-10-02: Blender Lab MCP Server, blender-mcp (now mcp-for-blender), Blender Agent Bridge, Sceneplane features and pricing. CPU rendering: Blender manual. Hardware, plans and features may change; tell us at the support page if a row is out of date.
| from | how |
|---|---|
| A file on this computer (.blend, 3D file) | Drop it at /upload to get a 12-hour link (no sign-up), then tell the AI "Render this file: <link>". From inside Blender use the add-on; from a terminal the CLI uploads directly |
| Claude.ai (web / desktop / mobile) | Plugins (older menu: Customize → Connectors) → Add custom connector → https://render.janction.jp/mcp. "Connect" opens a page that creates a free key |
| Claude Team / Enterprise | An owner adds https://render.janction.jp/mcp under Organization settings → Connectors; each member then presses Connect with their own account. In organizations that turn Skills off, Claude Desktop also blocks plugins from November 30 (use the connector URL, or ask the admin to turn Skills on) |
| ChatGPT | Plugins (left sidebar) → Add → Create plugin → https://render.janction.jp/mcp (OAuth). Attach your .blend to the chat. On Business workspaces an admin adds it and shares it |
| Claude Code | claude mcp add --transport http janction-render https://render.janction.jp/mcp, then /mcp to authenticate |
| Claude Code on the web (claude.ai/code) | The same connector as Claude.ai: Plugins (older menu: Customize → Connectors) → Add custom connector → https://render.janction.jp/mcp. Works without changing the session's network settings (guide) |
| Codex | codex mcp add janction-render --url https://render.janction.jp/mcp (the sign-in page opens right away; if Codex later says the server needs login, run codex mcp login janction-render; with a key, add --bearer-token-env-var JANCTION_RENDER_API_KEY) |
| Cursor / VS Code | Add to Cursor Add to VS Code Add to LM Studio The button opens the editor; confirm and it is added. Manual: Streamable HTTP at https://render.janction.jp/mcp |
| Antigravity CLI / Gemini CLI | agy plugin install https://github.com/JasmyLab-JANCTION/janction-render or gemini extensions install https://github.com/JasmyLab-JANCTION/janction-render (the MCP server and the workflow skill) |
| Kimi Code (Kimi K3 and other models) | /plugins install https://github.com/JasmyLab-JANCTION/janction-render (the MCP server and the workflow skill), or add https://render.janction.jp/mcp as a url entry under mcpServers in ~/.kimi-code/mcp.json and run /mcp-config login janction-render (OAuth). Guide |
| OpenCode | Add https://render.janction.jp/mcp under mcp in ~/.config/opencode/opencode.json with "type": "remote", then opencode mcp auth janction-render (OAuth). Guide |
| Qwen Code | qwen extensions install https://github.com/JasmyLab-JANCTION/janction-render (the MCP server and the workflow skill), or qwen mcp add --transport http janction-render with https://render.janction.jp/mcp (stored as httpUrl). Guide |
| GitHub Copilot CLI | copilot mcp add --transport http janction-render with https://render.janction.jp/mcp, then /mcp auth janction-render in copilot (OAuth). With the skill: copilot plugin marketplace add JasmyLab-JANCTION/janction-render, then copilot plugin install janction-render@janction-render. Guide |
| DeepSeek Harness (dsh) | One @deepseek-ai/dsh-mcp-client entry: transport: streamable-http, url: https://render.janction.jp/mcp, headers Authorization: Bearer with a key from POST /v1/keys (no OAuth). DeepSeek guide (API function calling too) |
| Grok / Perplexity / Le Chat | Add a custom (remote MCP) connector with https://render.janction.jp/mcp in each app's Connectors settings (Grok: Plugins → New connector → Custom, guide; Perplexity: Settings → Connectors → Custom → Remote, Pro / Max / Enterprise, OAuth; Le Chat: workspace admin, OAuth or a Bearer key) |
| Gemini app (gemini.google.com) | On the web: Settings → Connected Apps → Custom apps, add the MCP URL https://render.janction.jp/mcp (web only, English interface, with activity saving on). Sign-in is the OAuth consent page |
| Manus | Connectors → Create → Add MCP by URL with https://render.janction.jp/mcp (remote MCP only; OAuth or a Bearer key) |
| MiniMax (MiniMax Code) | One streamable-http entry in the MCP settings: url https://render.janction.jp/mcp, and Authorization: Bearer jr_… in headers |
| Notion (Notion Agent) | Business / Enterprise: Settings → Connections → Discover → Add Custom MCP → https://render.janction.jp/mcp, then sign in (the button shows when a workspace admin allows custom MCP servers) |
| JetBrains (AI Assistant, Junie) | AI Assistant: Settings → Tools → AI Assistant → Model Context Protocol (MCP) → Add → connect over HTTP with {"mcpServers": {"janction-render": {"url": "https://render.janction.jp/mcp"}}}. Junie: the same url in ~/.junie/mcp/mcp.json (Authorize opens the browser), or "headers": {"Authorization": "Bearer jr_…"} |
| Kiro (IDE, CLI) / Amazon Q Developer CLI | Kiro: "url": "https://render.janction.jp/mcp" under mcpServers in ~/.kiro/settings/mcp.json (in the IDE, open a folder: MCP SERVERS appears in the Kiro panel and the authorization page opens; in the CLI, /mcp auth janction-render). With a key: "headers": {"Authorization": "Bearer ${JANCTION_RENDER_API_KEY}"} (add the variable to Mcp Approved Env Vars). Amazon Q Developer CLI: "type": "http" and the same url in the agent configuration, then /mcp to sign in |
| Microsoft Copilot Studio | Tools → Add a tool → New tool → Model Context Protocol → Server URL https://render.janction.jp/mcp. Authentication: OAuth 2.0 with Dynamic discovery, or API key (Header, name X-API-Key, value jr_…). Set the agent's Settings → Generative AI → Orchestration to Yes (generative orchestration), or it will not use the tool |
| LM Studio (0.3.17 or later) | Program tab → Install → Edit mcp.json: {"mcpServers": {"janction-render": {"url": "https://render.janction.jp/mcp", "headers": {"Authorization": "Bearer jr_…"}}}} |
| Cherry Studio | Settings → MCP Servers → Add → Import from JSON: {"mcpServers": {"janction-render": {"type": "streamableHttp", "baseUrl": "https://render.janction.jp/mcp"}}}. Turn it on and press "Sign-in required." to open the consent page in the default browser. If no tools show after signing in, turn the server off and on again (with a key: "headers": {"Authorization": "Bearer jr_…"}) |
| Windsurf, Cline, Goose, Amp, Auggie, Warp, Zed, Roo Code, Continue and other MCP clients | Streamable HTTP at https://render.janction.jp/mcp; OAuth or Authorization: Bearer <api key> |
| Claude Desktop and other stdio-only clients (npm) | npx -y janction-render (in the client's mcpServers: {"command": "npx", "args": ["-y", "janction-render"]}). The npm package janction-render bridges stdio to https://render.janction.jp/mcp with OAuth; --key jr_… for a key you have, --local for the Python stdio server through uv |
| Terminal (stdio, sends local files) | claude mcp add janction-render -e JANCTION_RENDER_SERVER=https://render.janction.jp -- uvx --from janction-render janction-render-mcp |
| Inside Blender (for people) | The add-on; extension repository https://render.janction.jp/extensions/index.json. Maya / Houdini / Cinema 4D: submit tools |
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".
Yes. They are separate MCP servers; add both. Edit with blender-mcp, save the .blend, and ask the agent to render it with JANCTION Render.
No. It renders what you send. The agent edits by changing the bpy script or the .blend and sending it again; the sha256 lookup skips re-uploading unchanged files.
No. Claude.ai, ChatGPT and Codex open a consent page that creates a free key; the CLI gets one with janction-render key.
For editing, yes: it works on the open scene with no upload. For rendering it depends on your GPU; our measured times are on the benchmarks page.
