ifc-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| load_ifc_fileA | Load an IFC file from the given path. Returns model_id for subsequent queries. |
| list_loaded_modelsA | List all IFC models currently loaded in memory. |
| unload_ifc_fileC | Unload an IFC model from memory to free resources. |
| get_spatial_structureA | Get the full spatial hierarchy: Project > Site > Building > Storey > Space. |
| get_element_containmentA | Get the spatial containment chain for an element (Space > Storey > Building > Site). |
| get_elements_by_typeA | Get elements of a given IFC type (e.g. IfcWall, IfcDoor). Supports pagination via limit/offset. |
| get_element_by_idB | Get full details for a single element by its GlobalId. |
| search_elementsB | Search elements with optional filters: IFC type, name substring, pset_name (must own this pset), property_name/property_value (property within that pset or any pset). Supports pagination via limit/offset. |
| get_property_setsB | Get all property sets (Psets) for an element as {pset_name: {prop_name: value}}. |
| get_quantitiesB | Get all quantity sets for an element as {qset_name: {quantity_name: value}}. |
| get_materialA | Get material information for an element. Returns {name, layers, category} — layers is a list of {name, thickness} for layered assemblies, or None for simple materials. |
| get_model_statisticsA | Get element counts by IFC type, storey names, schema version, and total count. |
| get_bounding_boxA | Get the bounding box (min/max XYZ and dimensions) of an element in project coordinates. |
| get_element_placementA | Get the world-space placement of an element: insertion point (XYZ) and orientation axes (X/Y/Z unit vectors). Useful for position, rotation, and aim direction of elements like luminaires. |
| get_element_local_bboxA | Get the local-space bounding box of an element (no world transform applied). Returns min/max XYZ and dimensions in the element's own coordinate system. Use for mounting axis prediction and recessed fixture detection. |
| get_element_body_mappingA | Get the body mapping matrix for an element with IfcMappedItem geometry. Returns: has_mapped_item, body_mapping_matrix (4x4), world_transform (OPM × body mapping), world_transform_determinant, is_mirrored (det<0 means Y-negation needed). Essential for detecting baked rotations in luminaire imports. |
| get_property_sets_detailA | Get property sets split by source: instance-level psets vs type-level psets. Use to determine whether a property was overridden at instance level or inherited from the type. |
| get_element_by_labelA | Look up an element by its integer IFC entity label (#NNN from the STEP file). Returns the same response as get_element_by_id. Use to cross-reference import log output like '[OK] #16535 LightGraphix...' directly against MCP queries. |
| get_representationA | Get the representation structure of an element without tessellating geometry. Returns representation type, identifier, and items with IfcMappedItem details (mapping_target_is_identity, mapping_target_matrix). Use to detect baked rotations before geometry extraction. |
| get_elements_batchA | Batch query for multiple elements by GlobalId. include options: 'entity_label', 'placement', 'property_sets', 'local_bbox'. Default: ['entity_label', 'placement']. Avoids individual round-trips for files with 200+ fixtures. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/WolfzTech/Ifc-Mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server