API & MCP

Everything a person can do on IFC4 Export for Room Plans (BIM), a program or AI agent can do with the same inputs and get the identical result.

HTTP API

IFC4 Export for Room Plans (BIM)

Convert a room model (centre-line walls, doors, windows, spaces, furniture) into an IFC4 STEP file for BIM software: storeys, walls with material layers, openings that void the walls and are filled by doors and windows, floor and roof slabs, spaces with base quantities and furniture as bounding boxes. The file is re-read by an independent parser and checked against the IFC4 schema subset.

Inputs of IFC4 Export for Room Plans (BIM)
FieldTypeDefaultDescription
roomtextarea"{\n \"format\": \"kerfwise-room\",\n \"version\": 1,\n \"name\": \"L-shaped flaRoom model JSON (or a Kerfwise project). Storeys with centre-line walls {points, thicknessMm, layers}, openings {wallId, segment, kind, offsetMm, widthMm, heightMm, sillMm}, spaces {name, at, usage} and furniture. A .kerfwise.json project is converted from its kitchen plan.
datetext—File date (optional, YYYY-MM-DD). Written into the IFC header. Empty = 1970-01-01, so the same plan always gives the same file.

Every result contains

inputs (normalised, defaults applied), summary, result (validated against the published schema), units, assumptions, sources, warnings, computedAt and links.

MCP (Model Context Protocol)

{
  "mcpServers": {
    "kerfwise-ifc-export": { "type": "http", "url": "https://kerfwiseifcexport.usefulweb.app/mcp" }
  }
}