Skip to main content
Glama
tiranyx

rupa3d

by tiranyx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to rupa3d

No user-submitted related servers found.

    Related Servers

    • mcp-printable

      AaronGoldsmith
      A
      license
      A
      quality
      B
      maintenance
      Connects MCP-capable agents to Blender and OpenSCAD for AI-driven 3D modeling, with tools and rules optimized for FDM-printable geometry.
      29
      2
      MIT

    • Battenmark

      halsyourpal422
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents and software to create, edit, inspect, validate, and export CAD geometry through MCP using backend-neutral typed operations, with FreeCAD/OpenCascade as the authoritative B-rep backend and JSCAD preview.
      1
      Apache 2.0

    • robosimtools-mcp

      RahulRajelli
      A
      license
      A
      quality
      B
      maintenance
      Exposes 12 robotics/simulation tools from robosimtools.com as MCP tools, enabling AI agents to perform conversions (quaternion, URDF, MJCF), validation, and CAD imports locally.
      12
      1
      MIT

    • Blender-Mind-MCP

      xiaohai-uid
      A
      license
      A
      quality
      C
      maintenance
      Enables AI-driven 3D modeling in Blender by providing tools to create primitives, apply modifiers and materials, set up lighting and cameras, capture viewport snapshots, export assets, inspect scenes, and execute Python commands via natural language.
      10
      MIT

    • blender-ue-bridge

      malinaa1
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server for AI-driven Blender↔Unreal Engine bridge, providing 62 tools for 3D modeling, scene validation, and asset transfer across both engines.
      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.6/5.0

    Scored across 36 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (modeling, CAD, scene assembly, inspection), but there is some overlap between rupa_lihat and rupa_adegan_lihat (both involve viewing/checking the scene), and between rupa_ukur and rupa_cad_ukur (both measure objects). The descriptions are detailed enough to disambiguate, but an agent could hesitate between these pairs.

    Naming Consistency4/5

    The naming follows a consistent rupa_ prefix with snake_case verbs (rupa_baru, rupa_muat, rupa_ukur, rupa_ekspor). The CAD and scene subdomains use rupa_cad_* and rupa_adegan_* prefixes, which is a clear pattern. Minor deviation: rupa_cad_daftar and rupa_adegan_lihat use nouns rather than verb_noun, but the overall pattern is strong.

    Tool Count3/5

    36 tools is on the heavy side, but the server covers three distinct domains (core modeling, CAD kernel, scene assembly/publishing) plus inspection tools. Each tool has a specific job, but the count is high enough that an agent will need careful routing. It is not excessive for the scope, but it is at the upper edge of reasonable.

    Completeness5/5

    The tool surface is remarkably complete: modeling (create, import, script, measure, render, export, LOD, collision, bake, topology, texture), CAD (status, primitives, boolean, edges, fillet, sketch, transform, measure, export, import), and scene (new, assets, nodes, lights, camera, environment, publish). The only minor gap is no explicit tool for deleting individual objects outside the scene node tool, but rupa_adegan_node covers add/update/delete. The domain is fully covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources