Skip to main content
Glama
JasmyLab-JANCTION

JANCTION Render

by JasmyLab-JANCTION
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to JANCTION Render

No user-submitted related servers found.

    Related Servers

    • IRSofka Blender MCP

      irsjofka-alt
      A
      license
      Not graded
      quality
      C
      maintenance
      Lets an AI engine drive a Blender instance the user runs themselves over stdio JSON-RPC, enabling scene inspection, viewport capture and picking, sandboxed code execution, and gated asset search/import and 3D generation. Telemetry is disabled before import, outbound tools are withheld until per-run network consent, and VRAM gating plus a surface-policy tool report what is live and what a station has cleared.
      Business Source 1.1

    • Blender Open MCP

      Naokid132
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to control a live Blender session through MCP tools for scene and object operations, rendering, PolyHaven asset handling, and LLM prompting. Supports multiple configurable and runtime-switchable provider backends, including Ollama, LM Studio, llama.cpp, OpenAI-compatible endpoints, and Azure.
      -

    • blender-server-mcp-docker

      BATTLEHAWK00
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables remote control of Blender through MCP, allowing code execution, scene manipulation, rendering, and file transfer in a containerized environment.
      1
      -

    • blender-unified

      sajjadbeygi
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP-compatible clients to control Blender for modeling, materials, animation, physics, rendering, scene inspection, documentation search, and asset/generation service integration. It exposes a stdio endpoint with many Blender operations for creating and editing 3D content.
      AGPL 3.0

    • Blender MCP Bridge

      oddyseex
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to drive a live Blender session over MCP by creating and transforming primitives, building and assigning materials, inspecting scenes and objects, capturing viewport screenshots, and executing arbitrary bpy Python. Commands are relayed over a local TCP bridge to a Blender add-on and executed on Blender's main thread, supporting multiple simultaneous AI clients.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools map to clearly distinct stages of the cloud rendering workflow: estimate, preview, review, final render, status, download, cancel, share, info, billing, and asset search. The main ambiguity is between render_preview and render_review, which both return preview images and checks, and between render_status, render_info, and billing, which all report service or account state. Descriptions explicitly differentiate these, so an agent can tell them apart with care.

    Naming Consistency4/5

    Almost all tools use consistent snake_case, and most render operations share the predictable render_ prefix. The few deviations are scene_info, asset_search, and billing, which drop the verb prefix or use a different domain noun, but they remain readable and unsurprising. Overall the naming is coherent with minor inconsistencies.

    Tool Count5/5

    13 tools is well-scoped for a cloud Blender rendering service. The set covers the full workflow from scene inspection and estimation through preview, review, final render, download, cancel, sharing, and billing without obvious bloat. Each tool appears to earn its place.

    Completeness5/5

    The tool surface covers the rendering lifecycle comprehensively: scene_info, render_estimate, render_preview, render_review, render_final, render_status, render_download, render_cancel, render_share, render_unshare, render_info, billing, and asset_search. There are no obvious dead ends for the stated cloud rendering domain. Minor gaps like an explicit job-list tool are handled by render_status without job_id.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources