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

    • 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
      Not graded
      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

      tattooinmtl
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables any MCP client to drive Blender 5.2 LTS through natural language, with tools for scene inspection, object creation and transformation, material and modifier handling, rendering, viewport capture, and guarded Python execution.
      2
      MIT

    • BlenderMCP

      clanker25
      A
      license
      A
      quality
      C
      maintenance
      Enables connecting Blender 3D to AI assistants via MCP, allowing prompt-driven 3D modeling, scene editing, and real-time manipulation. Supports object/material control, scene inspection, viewport screenshots, and integrations with Poly Haven, Sketchfab, and AI model generators.
      22
      MIT

    • Blender MCP Server

      BlkDem
      A
      license
      A
      quality
      C
      maintenance
      Enables AI clients to control a running Blender instance through the Model Context Protocol, allowing scene inspection, object creation and editing, rendering, and execution of Blender Python. It works locally via a WebSocket bridge between the MCP server and a Blender add-on.
      15
      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

    A3.9/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: scene inspection (scene_info), preview rendering (render_preview), estimation (render_estimate), final rendering (render_final), job lifecycle (render_status/download/cancel), account (billing), and service health (render_info). The only superficially similar names (scene_info vs render_info) target entirely different domains—Blender scene contents vs JANCTION connection—and descriptions make the boundary explicit.

    Naming Consistency4/5

    Almost all tools use a consistent snake_case, mostly render_* prefix pattern (render_preview, render_final, render_status, render_download, render_cancel, render_info). Minor deviations: scene_info uses a different prefix and billing is a lone noun with no action suffix, but the overall style remains uniform and readable.

    Tool Count5/5

    Nine tools is well-scoped for a cloud Blender rendering service. Each tool maps to a concrete step in the render workflow (inspect, estimate, preview, final, poll, download, cancel, billing, service status) with no redundant or filler tools.

    Completeness4/5

    The lifecycle is essentially complete: scene inspection, preview, cost/time estimation, final render, job status, download, cancel, billing, and connection health are all covered. Minor gaps exist—there is no tool to list or retrieve past render jobs/history, and no explicit cleanup management beyond automatic 24h expiry—but core workflows are fully served.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources