Skip to main content
Glama
WolfzTech

ifc-mcp

by WolfzTech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to ifc-mcp

No user-submitted related servers found.

    Related Servers

    • ifc-mcp

      flinker-app
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to inspect, create, and report on IFC/BIM files locally, and to open models in a viewer with BCF viewpoint support.
      5
      129 npm
      13
      Apache 2.0

    • IFCX MCP

      louistrue
      A
      license
      C
      quality
      D
      maintenance
      Enables AI assistants to create, edit, and export IFC5/IFCX building information models through natural language, handling spatial structure, elements, geometry, metadata, validation, and export.
      73
      10 npm
      25
      Apache 2.0

    • ifc-ruhsat

      BerkantACUN
      A
      license
      A
      quality
      B
      maintenance
      Enables natural-language validation of IFC models against Türkiye's building-permit BIM regulation, including compliance checks, EK-9 form generation, and queries about required classes and properties.
      6
      40 PyPI
      2
      MIT

    • OpenStudio MCP Server

      roruizf
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables AI assistants to interact with OpenStudio building energy models through natural language, allowing users to load, inspect, and manipulate OSM files including building geometry, HVAC systems, materials, schedules, and internal loads.
      11
      MIT

    • ifcopenshell-mcp

      Daviidro
      A
      license
      A
      quality
      B
      maintenance
      An MCP server that lets users query, validate, convert, and compare IFC/BIM files using natural language. Runs fully locally and integrates with AI agents like Claude.
      8
      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 20 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (loading, spatial structure, element queries, properties, geometry). The only potential confusion is between get_element_by_id and get_element_by_label (both return element details) and get_property_sets vs get_property_sets_detail, but the descriptions explicitly differentiate them by input and level of detail.

    Naming Consistency5/5

    All 20 tool names follow a consistent snake_case verb_noun pattern (load_ifc_file, list_loaded_models, get_element_placement, search_elements). The verbs are uniform: load/list/unload for lifecycle, get for queries, search for search, with no mixed conventions or vague action words.

    Tool Count4/5

    With 20 tools, the server is slightly over the ideal 3-15 range but still well-scoped for the complex domain of IFC model analysis. Each tool addresses a specific aspect of querying building data, and the count is justified by the breadth of information exposed.

    Completeness4/5

    The toolset covers the full read-only lifecycle: loading/unloading models, querying spatial hierarchy, elements, properties, quantities, materials, geometry context, and batch operations. Minor gaps exist, such as no direct query of elements by spatial level or retrieval of raw geometry tessellation, but the core analytical workflows are well supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources