What’s actually slowing this PC down?

Pick the symptom - the matching free tool is one click away.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more

JANCTION Render is a hosted service for rendering Blender scenes on JANCTION GPUs, exposed through the Model Context Protocol (MCP). The available setup examples show two different connection patterns: Claude Code connecting to a remote HTTP endpoint, and Codex launching a local stdio server. Treat both commands below as examples, not verified current instructions: confirm the endpoint and syntax in JANCTION’s current operator documentation and the relevant client documentation before using them.

What JANCTION Render does

The Official MCP Registry describes JANCTION Render as an MCP service for rendering Blender scenes on JANCTION GPUs. Its listed output types include previews, frames, and MP4 video. A secondary directory describes scene files and scripts as inputs, but the precise supported formats should be confirmed with JANCTION before relying on a particular file type.

This is JANCTION Render, not Render.com’s infrastructure MCP server. The endpoint surfaced for JANCTION Render is https://render.janction.jp/mcp; because that address comes from a secondary listing, verify it against current JANCTION operator documentation before connecting.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Choose a connection mode

Client example Transport shown Configuration location Local runtime shown Authentication and file transfer
Claude Code Remote HTTP Added through the claude CLI No separate local server launcher appears in the example Not established by the listing; check current JANCTION and Claude Code instructions
Codex Local stdio launcher ~/.codex/config.toml uvx and the janction-render package are shown Not established by the listing; check current JANCTION and Codex instructions

Remote HTTP and stdio are distinct MCP transports, not interchangeable spellings of the same setup. The examples do not establish how authentication works or how a local scene reaches the hosted service, so do not assume that configuring a server automatically grants file access or uploads a project.

Connect Claude Code using the surfaced HTTP example

The secondary directory’s example registers JANCTION Render as a remote HTTP MCP server:

claude mcp add --transport http janction-render https://render.janction.jp/mcp
  1. Check JANCTION’s current operator documentation for the official endpoint and any required authentication or account setup.
  2. Check Claude Code’s current MCP instructions to confirm the supported transport and command syntax for your installed version.
  3. If those sources confirm the example, run it in a terminal where the claude command is available.
  4. Use Claude Code’s current MCP server listing or status interface to confirm that janction-render is available. The exact verification command can vary by client version; follow its current documentation.

The example is an endpoint registration, not proof that a scene file is uploaded or that rendering will succeed. Confirm JANCTION’s documented method for supplying scene files, scripts, or URLs before starting a job.

Connect Codex using the surfaced stdio example

The secondary listing shows Codex launching a local server process with uvx, while passing the JANCTION service URL through an environment variable. Its example for ~/.codex/config.toml is:

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
[mcp_servers.janction-render]
command = "uvx"
args = ["--from", "janction-render", "janction-render-mcp"]
env = { JANCTION_RENDER_SERVER = "https://render.janction.jp" }
  1. Confirm the current Codex MCP configuration format and JANCTION’s supported installation instructions before editing the file.
  2. Confirm that uvx is installed and available to Codex if the current JANCTION instructions still require it.
  3. Add the configuration to ~/.codex/config.toml, adjusting the location only if your Codex installation uses a different documented config path.
  4. Restart or reload Codex as its current documentation requires, then verify that the server starts and its tools are available.

This example uses stdio: Codex starts a local process rather than connecting directly to the /mcp HTTP endpoint shown in the Claude Code example. The configuration alone does not establish file-transfer behavior. Follow JANCTION’s instructions for providing the Blender scene and any scripts.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Before rendering a Blender scene

The registry lists previews, individual frames, and MP4 among the service’s possible outputs. The secondary directory mentions Blender scene files and Python scripts, as well as other 3D scene formats, but that listing does not establish a definitive compatibility matrix. Check the operator’s current documentation for accepted formats, size limits, Blender version requirements, scene-upload workflow, and any required job parameters.

  • Verify the exact endpoint and transport supported for your client.
  • Find out whether authentication, an account, or an API credential is required and how to configure it safely.
  • Confirm how local files or remote URLs are made available to the hosted renderer.
  • Check current pricing on JANCTION’s pricing page: since October 8, 2026, a new key gets a welcome credit of up to ¥500, previews are free up to 2 GPU-minutes a day, and finals cost ¥0.1 per GPU-second. Capacity and availability are not guaranteed.
  • Run a small test scene first and confirm where the service returns its preview or rendered output.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply. Prices as of November 19, 2026 3:12 pm GMT.