mcp · Global

ifcx-mcp

MCP server for authoring IFC5/IFCX building information models through AI assistants. Supports spatial structures, geometry, materials, classifications, validation, glTF/Three.js preview, and multiple IFCX export formats.

Visit source ↗GitHub repository ↗

Claim this listing

Represent ifcx-mcp? Send a claim for review so we can discuss listing updates. Claims do not automatically grant ownership or verification.

Explore paid sponsorship →

What's in it

Data offered docs-verified: IFCX model authoring: spatial structure, types, element occurrences · geometry: mesh, procedural, BRep, curve · materials and PBR data · IFC5 standard properties · classifications with bSDD resolution · georeferencing via EPSG or WKT · IFC5 compliance, IDS and IFClite validation · BCF issue packages · glTF and Three.js preview export · layer history and patch-effect explanation
Formats docs-verified: IFCX alpha JSON (.ifcx) · IFCX tiered (index.ifcx + NDJSON tables) · IFCX zipped post-alpha (.ifcx ZIP package) · glTF (scene.gltf + scene.bin) · Three.js preview (index.html) · BCF (.bcfzip) · MCP stdio
Access docs-verified: Local install from source: git clone, npm install, npm run build, then run as a stdio MCP server. No credentials documented in README. Licence not stated in metadata.

Useful for

Use cases llm-inferred: Author an IFC5 pipe or services network with distribution ports for a design coordination check · Attach Uniclass or bSDD classifications to walls and elements, then run IDS validation before handover · Georeference a civils or building model with an EPSG code and export a glTF or Three.js preview for client review · Use patch layers and layer-history explanations to report design changes between model revisions
Audience llm-inferred: BIM coordinators · BIM/civils engineers · drainage engineers · GIS analysts

Limitations

Constraints docs-verified: Drafts are held in memory only; they are lost when the server stops · Live publishing is a risk: only use it against an API endpoint you control · Publishing defaults to dry-run and needs dryRun: false to upload · Older tool names are kept only as aliases while the interface settles · The buildingSMART viewer is not treated as the target spec for export checks

Licence: Unknown — check provider terms
Authentication: No credentials documented in README
GitHub stars: 25
Last commit: 12/04/2026
Last successful page check: 14/10/2026
Page health: healthy
Package: Not recorded
Verification: Not independently verified

Provenance & evidence

Tools/install/auth auto-extracted from README; quality score heuristic (stars, recency, tool count, licence).

Metadata observed 15/10/2026 · research sweep: github-search