Skip to main content
Glama
architectural_modeling_workflow

architectural_modeling_workflow

by Lsc1123

Related Servers

Alternatives to architectural_modeling_workflow

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      C
      maintenance
      Enables LLMs such as Claude to drive Blender through high-level tools for real-world-scale modeling, PBR texturing, lighting, rendering, rigging/animation, and UE5 game-asset baking and export. It also provides asset-library search, reference comparison, quality inspection, and import/export of common 3D file formats.
      58
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables a shared 3D workspace where humans and AI agents co-design in real time, with scene awareness, goal-level tools, visible proposals, deterministic reviews, and approval-gated changes.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI-driven 3D modeling and scene creation in Blender, allowing LLMs to create, modify, and manipulate objects, materials, and assets through natural language.
      31
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables LLMs to perform architectural spatial modeling through natural language, including creating, manipulating, and analyzing 3D building models using TopologicPy.
      22
      AGPL 3.0
    • A
      license
      C
      quality
      D
      maintenance
      Enables AI-driven 3D modeling, analysis, diagnostics, and Grasshopper integration within Rhino 3D through 90+ tools via the Model Context Protocol.
      105
      3
      MIT

    TDQS

    C2.8/5.0

    Scored across 41 tools

    Disambiguation4/5

    Most tools target distinct resources and actions, with clear domain prefixes separating project, SketchUp, asset, evidence, and job operations. A few read/inspect/export tools overlap conceptually (project_get vs sketchup_state vs get_capabilities; sketchup_export vs handoff_export), but descriptions generally clarify boundaries.

    Naming Consistency4/5

    The set overwhelmingly follows a snake_case resource_action pattern (project_get, sketchup_create, stage_advance, evidence_register), which is predictable despite not being verb_noun. Occasional outliers like get_capabilities and mixed noun/verb phrasing keep it from a 5.

    Tool Count2/5

    The domain is broad and many tools are specialized, but 41 tools is heavy and exceeds a practical set size. Several low-level SketchUp operations and status/cancel pairs could likely be consolidated without losing capability.

    Completeness4/5

    The surface covers project lifecycle, stage gates, decisions, evidence, checks, SketchUp modeling/export/save, Blender asset jobs, and handoff. Minor gaps exist around asset inspection/listing and project deletion or archival, but core workflows appear well covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues