A hybrid AI workflow for modeling a house from a floor plan
Reconstruct a floor plan, review it through MCP, export GLB, then use GPT-6 Astra through Blender Python or MCP for bounded scene work.

On this page
Use the floor plan to establish the rooms, check the reconstructed model, then take it into Blender for custom geometry, materials and lighting. This workflow shows where INK TO BRICK, its MCP connection and an AI assistant working in Blender each fit, including the checks needed between tools.
Compare the total setup work with manual modeling
Use one source and one destination task for the comparison. Record preparation time, reconstruction checks, supported corrections, export and cleanup in the receiving application. Stop the clock only when the file opens at the right scale and contains the geometry needed for that task. A quick first result can lose its advantage if you must rebuild doors or reorganize every object afterward.
Keep good CAD geometry when it already carries useful units and layers; do not rasterize it merely to fit an AI demonstration. When you start from a scan, preserve the source and the assumptions about heights. The hybrid route is useful only if the reviewed handoff saves work compared with drawing or importing directly.
1. Reconstruct and check the source
Upload the complete floor plan to INK TO BRICK. Compare the exterior outline, room names, walls and openings with the drawing. Check scale against a known dimension and verify critical measurements on site. Fixing an uncertain source after adding furniture and materials multiplies the cleanup.
2. Use MCP for project context
Connect Codex or another compatible MCP client with read access to https://mcp.inktobrick.com/mcp. Copy the project ID from its dashboard URL, then ask the client to read that workspace, summarize rooms, compare revisions or search the fixture catalog. The MCP server does not list projects. Self-serve Codex connections start read-only. To prepare edits you confirm, sign in again with the design-option write and select scopes.
3. Export for the work ahead
- GLB for the simplest Blender handoff: one file with geometry, materials and textures.
- Packaged glTF when you want separate, inspectable texture and buffer files.
- DXF or DWG for a layered 2D CAD plan, with no claim that it recreates the original CAD file.
- IFC for a semantic BIM reference on Pro and Team, without claiming native Revit fidelity.
4. Give Astra a narrow Blender brief
Give Astra access to Blender through the Blender Python API or a separate Blender MCP server, import the GLB into an empty scene and save a working copy. Ask for one bounded change at a time: rename collections, clean selected mesh topology, replace one material family, place cameras, or prepare lighting. Require the agent to describe which objects it changed and inspect the scene after each step.
This hybrid keeps a reviewable floorplan-derived starting point while leaving bespoke modeling to the authoring tool. It also makes failure easier to locate: a room-topology error belongs before export, while a lighting or subdivision problem belongs in Blender. Read the cost and time comparison before treating model-token arithmetic as a project quote.
Decide where the editable source will live
If Blender is for final lighting and rendering, keep the architectural model in INK TO BRICK and export a new GLB after layout changes. If you remodel the mesh in Blender, record that handoff: importing it back does not recover the original wall and opening parameters automatically. Choose which project owns later geometry changes before both versions diverge.
Inspect a reference in 3D
Orbit the model and zoom toward an opening. Which spaces does it connect, and what is hidden from the opposite angle?



