Skip to main content
Glama
ifcopenshell-mcp

ifcopenshell-mcp

ifcopenshell-mcp

License: MIT Python 3.10+ MCP Compatible

Talk to your BIM models in natural language. An open-source MCP server for IfcOpenShell — query, validate, convert, and compare IFC files through AI agents.


For Architects (no coding required)

What does this do?

Drag an .ifc file into Claude and ask questions like:

"How many fire doors are on Level 2?"

Claude reads your model and answers:

Found 2 IfcDoor elements with FireRating=R60:
- Fire Exit GF (Ground Floor)
- Fire Exit L2 (Level 2)

No Revit. No Navisworks. No SQL. Just drag, ask, get answers.

What can I ask?

You ask...

It does...

"Summarize this model"

Shows project name, total elements, spatial structure

"How many walls on Ground Floor?"

Counts and lists them with IDs

"Validate that all elements have materials"

QA/QC report: PASS / FAIL / WARNING per element

"Extract concrete quantities for Level 1"

Area, volume, length organized by element

"What changed since last week's version?"

Diff report: added, removed, modified elements

"Convert this to GLB for web viewing"

Creates a 3D file viewable in any browser

Complete tool list at the bottom of this page.

How to install (5 minutes, one time only)

Step 1: Install uv (a tiny installer). Open your terminal once and paste:

Windows (PowerShell):

powershell -c "irm https://astral.sh/uv/install.ps1 | iex"

Mac (Terminal):

curl -LsSf https://astral.sh/uv/install.sh | sh

Step 2: Download this tool. In the same terminal:

git clone https://github.com/Daviidro/ifcopenshell-mcp.git
cd ifcopenshell-mcp
uv sync

Step 3: Tell Claude about it. Open Claude Desktop → Settings → Developer → Edit Config, and paste:

{
  "mcpServers": {
    "ifcopenshell": {
      "command": "uv",
      "args": ["run", "ifcopenshell-mcp"],
      "cwd": "D:/ifcopenshell-mcp"
    }
  }
}

Restart Claude Desktop. Done. Drag any .ifc file and start asking.

Is this safe?

Yes. Your files never leave your computer. Period.

  • Everything runs 100% locally — no cloud, no accounts, no internet needed

  • It only reads IFC files you explicitly drag into Claude — nothing else

  • It cannot write files outside your project folder

  • It cannot access system files

  • The code is open source (MIT) — anyone can inspect every line

  • Built on IfcOpenShell, trusted by thousands of architects and engineers since 2011

No telemetry. No analytics. No hidden anything.


Related MCP server: Bonsai-mcp

For Developers (contributing code)

Tools

Tool

Description

Example question

query_ifc_elements

Search by type, level, or properties

"Show all fire doors"

get_ifc_statistics

Model overview and class distribution

"Give me a summary"

get_element_properties

Full properties of one element by GUID

"Details of wall 3GQqVv..."

list_ifc_spaces

All rooms/spaces

"List all rooms"

validate_ifc_model

QA/QC: materials, properties, containment, naming

"Validate this model"

compare_ifc_models

Diff between two IFC versions

"What changed?"

extract_ifc_quantities

Quantity takeoffs (markdown/CSV/JSON)

"Concrete volume?"

convert_ifc_to_gltf

IFC to GLB for web visualization

"Make it viewable online"

Supported formats

  • IFC2x3, IFC4, IFC4.3 (.ifc, .ifczip, .ifcxml)

  • Output: markdown, CSV, JSON

  • GLB: requires IFC files with geometric representations. Semantic-only IFCs report conversion failure.

Setup

git clone https://github.com/Daviidro/ifcopenshell-mcp.git
cd ifcopenshell-mcp
uv sync
uv run pytest tests/ -v    # 19 tests, all must pass

Tests

uv run pytest tests/ -v
# Expected: 19 passed (13 functional + 6 error handling)

Roadmap

  • Clash detection (bounding box)

  • COBie spreadsheet export

  • IFC to Revit roundtrip via Speckle

  • Classification system validation (Uniclass, OmniClass)

Contributing

See CONTRIBUTING.md. Built on IfcOpenShell (LGPL-3.0) and MCP. Also check out the official IfcOpenShell MCP.

Ecosystem

License

MIT — see LICENSE file.

Available Tools

8 tools
compare_ifc_modelsA

Compare two IFC versions and report added, removed, and modified elements.

Inputs: ifc_path_v1 (required), ifc_path_v2 (required). Returns: result

convert_ifc_to_gltfA

Convert an IFC model to glTF/GLB for web visualization, optionally with Draco compression.

Inputs: ifc_path (required), compress, output_path, max_elements. Returns: result

extract_ifc_quantitiesB

Extract quantity takeoffs (lengths, areas, volumes, counts) as markdown, CSV, or JSON.

Inputs: ifc_path (required), storey, output_format, quantity_type. Returns: result

get_element_propertiesB

Get all property sets and quantities for a specific element by its GlobalId.

Inputs: ifc_path (required), global_id (required). Returns: result

get_ifc_statisticsB

Get comprehensive IFC model statistics: project name, schema, elements, class distribution, spatial structure.

Inputs: ifc_path (required), detail_level. Returns: result

list_ifc_spacesA

List all spaces/rooms in the IFC model, optionally filtered by storey.

Inputs: ifc_path (required), storey. Returns: result

query_ifc_elementsA

Search/filter IFC elements by type, storey, or properties. E.g. 'How many fire doors on Level 2?'

Inputs: ifc_path (required), limit, storey, element_type, +1 more. Returns: result

validate_ifc_modelA

Run QA/QC validation: materials, properties, containment, naming. Returns PASS/FAIL/WARNING report.

Inputs: ifc_path (required), checks. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.8/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct operation: searching elements, getting model stats, retrieving properties for one element, listing spaces, validating, comparing, converting, and extracting quantities. There is no overlap in their purposes, and the descriptions make their boundaries clear.

    Naming Consistency5/5

    All tool names follow a clear verb-first snake_case pattern (query, get, list, validate, compare, convert, extract) with descriptive nouns. The pattern is consistent and predictable, making it easy to guess what each tool does.

    Tool Count5/5

    With 8 tools, the set is well-scoped for an IFC model analysis and conversion server. Each tool provides a distinct and necessary capability without redundancy or bloat, fitting comfortably within the ideal range.

    Completeness5/5

    The tool set covers the full lifecycle of IFC model interaction: querying, inspecting, validating, comparing, converting, and extracting quantities. It addresses both high-level statistics and granular element details, leaving no obvious gaps for typical IFC use cases.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      AI-powered MCP server that enables Claude and other LLMs to interact directly with construction documents, drawings, and specifications through advanced RAG and hybrid search capabilities.
      8
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      MCP server for Speckle that enables AI-powered AEC interoperability, letting users manage Speckle projects, models, and versions through natural language, with guidance for data push/pull via native connectors.
      8
      MIT