Skip to main content
Glama
tylerart3d

MoonRay MCP

by tylerart3d
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to MoonRay MCP

No user-submitted related servers found.

    Related Servers

    • vred-mcp

      krngrover6
      A
      license
      Not graded
      quality
      C
      maintenance
      A local MCP server that enables MCP-compatible AI clients to inspect and control the currently open scene in a running Autodesk VRED Professional 2027 instance via a secure bridge, supporting read-only inspection and gated mutations like selection, visibility, transforms, and screenshots.
      MIT

    • resinsight

      hnil
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to watch and drive a running ResInsight, query reservoir simulation models, and render pictures and plots without touching the GUI.
      GPL 3.0

    • nscr-houdini-mcp

      nscrdev
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to connect to multiple SideFX Houdini 22 sessions, including GUI and headless, to build, render, cache, and verify scenes against reference images.
      MIT

    • Bonsai MCP

      Show2Instruct
      A
      license
      A
      quality
      B
      maintenance
      Connects MCP clients to a local Blender + Bonsai (BlenderBIM) session for scene inspection, IFC project querying, viewport screenshots, and executing Python code in Blender.
      8
      7
      MIT

    • blender-ai-mcp

      alexandervi1
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects MCP-compatible clients to a live Blender scene for AI-assisted 3D workflows, enabling inspection and controlled operations on objects, materials, cameras, lights, render settings, animation, UVs, Geometry Nodes, imports, exports, and Python execution.
      1
      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

    B3.2/5.0

    Scored across 25 tools

    Disambiguation5/5

    Each tool targets a distinct action and resource: viewer controls, scene inspection, render lifecycle, and comparison are clearly separated. Even similar-sounding tools like capture_interactive_viewer_snapshot and capture_render_snapshot are differentiated by their target context.

    Naming Consistency3/5

    The set mixes verb-first names like start_render and validate_scene with noun-first names like render_status and moonray_resources. The pattern is readable, but it is not fully consistent; some query tools would be clearer with a get_ or list_ prefix.

    Tool Count3/5

    At 25 tools, the surface is on the heavy end, though the breadth of MoonRay workflows partially justifies it. The tools cluster into coherent subdomains, but the overall count feels somewhat large for an MCP server.

    Completeness4/5

    The set covers the core render lifecycle, interactive viewer controls, scene preflight, and comparison workflows. Minor gaps include no explicit render job listing or general render-setting adjustment, but agents can work around these with existing status and capability tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources