Skip to main content
Glama
aidenlab

Hello3DMCP Server

by aidenlab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to Hello3DMCP Server

No user-submitted related servers found.

    Related Servers

    • spz-mcp

      redDwarf03
      A
      license
      A
      quality
      B
      maintenance
      MCP server that lets an LLM agent drive StableProjectorz, a 3D modeling app, by inspecting the loaded model, app state, viewport screenshots, and triggering UI actions via a loopback socket bridge.
      1
      1
      MIT

    • Touch Flow Base (MCP Counter

      jobinpjoseph707
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables AI agents to execute sandboxed JavaScript code to control external web applications in real-time. It utilizes WebSockets to synchronize script execution with frontend animations, allowing complex UI interactions to be handled in a single agent turn.
      -

    • BlenderMCP

      SolonaBot
      A
      license
      B
      quality
      D
      maintenance
      An MCP server that enables AI models to directly control Blender for 3D modeling, scene manipulation, and material management through natural language. It supports advanced workflows including Python code execution, viewport visualization, and integration with external asset libraries like Poly Haven and Hyper3D.
      22
      1
      MIT

    • Three.js MCP Triangle

      mithun-tagde
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server that lets you control a Three.js triangle in the browser via natural language, including setting colors, vertex colors, and transformations (position, rotation, scale), with live updates via WebSocket.
      -
    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.4/5.0

    Scored across 61 tools

    Disambiguation3/5

    The tools are mostly distinct by target (model, key light, fill light, camera, background), but there is significant overlap in light manipulation: swing_*, walk_*, move_*_toward_direction, set_*_position_spherical, and set_*_distance all adjust light position in different but confusingly similar ways. The swing/walk/move/nudge/rotate families for lights can be hard to distinguish without deep reading.

    Naming Consistency3/5

    The naming is mostly verb_noun (change_model_color, set_key_light_intensity, get_camera_fov), but there is inconsistency: some use 'change_', some 'set_', some 'get_', some 'swing_', 'walk_', 'nudge_', 'rotate_', 'dolly_', 'increase_', 'decrease_'. The verb families are semantically different but the pattern is not uniform, and 'dolly_camera' vs 'dolly_camera_in/out' is slightly redundant.

    Tool Count2/5

    61 tools is far too many for a 3D scene manipulation server. The surface is heavily fragmented: light controls alone account for dozens of tools, with separate tools for every direction and relative/absolute variants. This could be consolidated into parameterized tools (e.g., set_light_position with direction and amount).

    Completeness4/5

    The domain is 3D scene manipulation (model, lights, camera, background), and the coverage is quite thorough: model color/size/rotation/scale, key and fill light color/intensity/position/size, camera dolly/FOV, background color, and connection URL. Minor gaps: no model loading/selection, no camera rotation/orbit, no rim light or environment controls, but for the apparent scope it's fairly complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources