Skip to main content
Glama
kleinicke

3D Visualizer

by kleinicke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to 3D Visualizer

No user-submitted related servers found.

    Related Servers

    • Data MCP Server

      patrickoleary
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables scientific data introspection and visualization of VTK datasets with format-adaptive metadata extraction and interactive 3D visualization through MCP tools.
      1
      MIT

    • 3d-eyes

      murphy977
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables coding agents to visually inspect and diagnose 3D files (meshes and Gaussian splats) for defects like flipped normals or floaters, without GPU dependencies.
      MIT

    • CityDPC-MCP

      HamerCode
      A
      license
      A
      quality
      B
      maintenance
      MCP server for inspecting, analysing, and editing CityJSON and CityGML building datasets.
      19
      Apache 2.0

    • rupa3d

      tiranyx
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents and MCP clients to perform 3D asset creation and verification: exact b-rep CAD, GLB validation with embedded certificates, mesh inspection, and physics scenes, with most tools running without Blender.
      36
      45 npm
      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.1/5.0

    Scored across 27 tools

    Disambiguation3/5

    Several tools occupy near-adjacent roles: set_3d_camera vs navigate_3d_view for camera control, capture_3d_view vs preview_3d_views for image inspection, and manage_3d_views vs manage_3d_scene_states for saved state. The long descriptions help, but an agent must carefully compare multiple tools before selection. The app-only transport tools (submit_viewer_reply, read_viewer_data) also blur the boundary between domain actions and internal communication.

    Naming Consistency4/5

    The naming is generally very consistent: snake_case verb-first names such as open_3d_files, set_3d_camera, and manage_3d_scene_states create a clear pattern. Minor divergences like open_depth_image, visualize_points, submit_viewer_reply, and read_viewer_data do not use the same 3d marker, but the overall verb_noun convention remains predictable.

    Tool Count2/5

    With 27 tools, the surface is too large; only a handful of related verbs are needed for the core workflows. Many tools could be grouped or filtered into a smaller, more focused set. The breadth may be useful, but the agent-facing tool count creates too much decision overhead.

    Completeness4/5

    The domain is broadly covered: opening local, remote, and depth data; inspecting, updating, closing, transforming, aligning, measuring, selecting, exporting, comparing, and animating scenes. Minor gaps include lack of explicit per-object deletion and a couple of internal app-only transport tools that do not fit the domain surface.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources