Skip to main content
Glama
Sign In
3D New Era AI

3D New Era AI

by leandrodaf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

Related Servers

Alternatives to 3D New Era AI

No user-submitted related servers found.

    Related Servers

    • WalkMyPlan MCP Server

      yaniv-fink
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables users to create and edit 3D floor plans conversationally, describing rooms and layouts or uploading DWG/PDF drawings, then view them in 2D/3D via a live link.
      4
      MIT

    • Atelier

      lebac-svg
      A
      license
      Not graded
      quality
      C
      maintenance
      Converts spoken descriptions into standards-compliant floor plans and furnished 3D models, enabling real-time collaborative editing through a live browser editor with Claude AI.
      9 npm
      Apache 2.0
    • Luw MCP Server

      Luw MCP Serverofficial

      Luvi-io
      A
      license
      A
      quality
      B
      maintenance
      Enables AI-driven interior, exterior, and landscape design, photoreal rendering, image editing, video generation, and 3D model creation directly inside Claude, Cursor, VS Code, and other MCP clients. It also supports virtual staging, sketching to render, texture and pattern generation, background removal, and architectural consultation through natural language.
      24
      149 npm
      MIT
    • @getfacade/mcp

      @getfacade/mcpofficial

      getfacade
      A
      license
      A
      quality
      B
      maintenance
      Enables an AI agent to create a building from a photo, generate a facade design, and order a line-by-line cost estimate and documentation album, using country-specific materials and construction norms.
      21
      116 npm
      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

    A3.5/5.0

    Scored across 57 tools

    Disambiguation4/5

    Most tools are cleanly separated by domain and by read vs. write/review vs. render, and descriptions often explicitly point to the companion tool. A few boundaries remain fuzzy—generic `update` vs. domain `edit_*`, `joinery`/`cabinet_run`/`embed`, and `model`/`catalog`/`library`—but they are usually resolvable from the text.

    Naming Consistency4/5

    Names are consistently snake_case and follow a systematic read/action convention: bare noun for inspection (`levels`, `cameras`, `materials`) and `edit_noun` for mutation (`edit_levels`, `edit_cameras`). It is not a pure verb_noun scheme because many operation tools are single verbs or verb_noun, but the convention is readable and predictable.

    Tool Count2/5

    At 57 tools, this is far above the typical 3–15 range and creates a large selection/context burden for an agent. The broad CAD/review/rendering domain justifies many capabilities, but several clusters could be merged or split into focused servers to make the set more manageable.

    Completeness4/5

    The surface covers the core lifecycle very thoroughly: project/file management, geometry creation/editing, levels, variants, annotations, reviews, rendering, exports, models/library, and plugins. Minor gaps exist, such as direct editing of wall types/finish patterns and catalog management, but most agent workflows have a path.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources