Skip to main content
Glama

Related Servers

Alternatives to JANCTION Render

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      Enables AI clients to control Blender through its official MCP add-on: running arbitrary bpy code or background CLI jobs, auditing scenes and blend files, searching Blender API and manual docs, capturing screenshots and renders, and searching or importing free Poly Haven models, HDRIs and textures at real-world scale. All 28 tools are served over one stdio connection to a single Blender instance.
      28
      GPL 3.0
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to drive a live Blender session over MCP by inspecting scenes, creating and modifying objects, assigning materials, rendering images, and fetching PolyHaven assets. It also exposes prompt-based scene building and review workflows backed by a provider-agnostic LLM layer (Ollama, LM Studio, llama.cpp, OpenAI-compatible endpoints, Azure) that can be switched at runtime.
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to drive a live Blender session over MCP — inspecting and creating scene objects, applying materials, rendering, executing code, and fetching PolyHaven assets. It also exposes prompt, provider, and model tools backed by a provider-agnostic LLM layer (Ollama, LM Studio, llama.cpp, OpenAI-compatible, Azure) that can be switched at runtime.
      -
    • 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
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to control a live Blender session, including scene and object operations, rendering, and PolyHaven asset workflows. Supports provider-agnostic LLM backends that can be switched at runtime through MCP tools.
      -

    TDQS

    A4.2/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but the set has several 'check' tools (render_status, render_info, render_estimate, billing) whose boundaries are only clarified by lengthy descriptions. render_preview and render_review also overlap in that both return visual checks, though the descriptions distinguish preview rendering from 4-side model QA.

    Naming Consistency4/5

    Ten of thirteen tools follow a consistent render_ verb/noun pattern, and the remaining three (billing, scene_info, asset_search) are readable domain-specific names. The mix is minor and predictable rather than chaotic.

    Tool Count5/5

    Thirteen tools is well within the sweet spot for a render service with preview, final, estimate, status, download, cancel, share, and supporting utilities. Each tool corresponds to a meaningful step or check in the render lifecycle.

    Completeness5/5

    The surface covers the full lifecycle: scene inspection, asset search, preview, review, estimate, final render, status polling, download, cancellation, sharing/unsharing, billing, and service health. No obvious dead ends or missing core operations for a cloud Blender rendering service.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues