An MCP client can turn an existing INK TO BRICK project into a working conversation: inspect rooms, compare revisions, search catalogs, prepare supported Design Option changes, and request pinned JSON or GLB exports. Keep uploads, reconstruction and other export formats in the web app or API.
Begin with read-only context
- Using this project ID from my dashboard URL, open its workspace and summarize its rooms, openings, scale status and current revision.
- Compare the current Design Option with its previous revision. List only fields that changed.
- Search the fixture catalog for choices that fit this brief, without changing the project.
Preview before a supported change
- Preview a warmer oak floor in the saved living-room Design Option. Do not apply it.
- Show the proposed change, the option and revision it targets, and anything that could not be resolved.
- After I confirm, apply that exact preview.
- If I reject the result, restore the prior Design Option revision and show the new current revision.
Use a second tool for Blender
Request a pinned GLB export through INK TO BRICK MCP, or use the web app or API for the broader export library. Then give your chosen model access to Blender through its Python API or a separate Blender MCP server and ask it to import that file, save a new .blend file and work in a copy. The two MCP servers have different jobs: INK TO BRICK supplies project context and supported design decisions; the Blender server controls Blender.
Do not ask the assistant to infer that a visual change is structurally safe or dimensionally exact. Check scale, room topology, wall and opening positions, object names, materials and normals after every file handoff. Connect Codex first, then follow the Blender import checks.
Use the authenticated tool catalog as the source of available operations and permissions. Pro and Team include MCP, and Team includes API access. Model reads, proposed changes and export delivery are distinct operations; obtain the actual delivery before saying an export is ready. Confirm the project and revision before any change.
Try it and check your result
First compare the returned project and revision with the web app. Then request one supported material preview and read the exact target before confirming; discard it once to check that the revision stays unchanged. If you later apply a fresh preview, read back the new revision and inspect it in the model. For an export, obtain the delivery and open the actual file before asking another tool to continue it.
Inspect a reference in 3D
Orbit and locate an opening before describing a change. Which element and context would you name? This viewer does not execute assistant, API or MCP commands.
