Connect Codex to INK TO BRICK when you want to inspect an existing floor plan project from a conversation. The connection uses the remote MCP resource at https://mcp.inktobrick.com/mcp. MCP is included on Pro and Team under their plan features and usage limits, with no separate MCP credits. New connections request read access by default, and reading an existing project does not use an import. Home, Home Max, Plural and Core do not include MCP.
Add the server in Codex
- Open Codex settings, choose MCP servers, and add
https://mcp.inktobrick.com/mcpas a streamable HTTP server. Codex desktop, the CLI and the IDE extension share the same MCP configuration. - From the CLI, use
codex mcp add inktobrick --url https://mcp.inktobrick.com/mcp --oauth-client-registration dcr, then runcodex mcp listor open/mcpto check the connection. - Run
codex mcp login inktobrick --scopes lodnor.floorplan.read,offline_access --oauth-client-registration dcrand sign in when Codex opens the authorization flow. This default requests read access and offline renewal.
OpenAI documents both streamable HTTP and local STDIO MCP servers for Codex. The Codex MCP guide also explains the matching config.toml entries.
Codex handles the MCP connection independently of the model you choose for the conversation.
What Codex can do after connecting
- Read a floor plan workspace and revision history after you supply its project ID from the dashboard URL.
- Search the fixture catalog and review saved aesthetic options.
- Prepare a supported Design Option change, inspect its exact preview, and apply it only after you confirm it in Codex.
- Request a pinned JSON or GLB export, check the job status, and retrieve its short-lived delivery when it is ready.
Start with a read request: copy the project ID from its dashboard URL, ask Codex to open that workspace and summarize its rooms and saved Design Options. The server does not provide a project-list tool. For examples that respect the preview-and-confirm boundary, continue with MCP floor plan workflows.
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
After login, supply a project ID you recognize and ask only for its workspace, current revision and room names. Compare that response with the dashboard before granting write scopes. If sign-in succeeds but tools return an access error, check the consented workspace and Pro access first. Connection success is complete only when that read returns the intended project; do not paste browser tokens into chat to work around an error.
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.
