Connect Codex to INK TO BRICK with MCP

Conceptual model only. Not a survey or construction document.

Connect Codex to the INK TO BRICK MCP server, authorize read access, and understand which project and Design Option tasks it supports.

Connect Codex to INK TO BRICK when you want to inspect an existing floorplan project from a conversation. The connection uses the remote MCP resource at https://mcp.inktobrick.com/mcp. MCP is included on paid plans under the same plan features and usage limits, with no separate MCP credits. A self-service Codex connection receives read access, and reading an existing project does not use an import. Free projects do not include MCP.

Add the server in Codex

1. Open Codex settings, choose MCP servers, and add https://mcp.inktobrick.com/mcp as a streamable HTTP server. Codex desktop, the CLI and the IDE extension share the same MCP configuration.
2. From the CLI, use codex mcp add inktobrick --url https://mcp.inktobrick.com/mcp --oauth-client-registration dcr, then run codex mcp list or open /mcp to check the connection.
3. Run codex mcp login inktobrick --scopes lodnor.floorplan.read,offline_access --oauth-client-registration dcr and sign in when Codex opens the authorization flow. Public dynamic client registration grants read access and offline renewal only.

OpenAI documents both streamable HTTP and local STDIO MCP servers for Codex. The Codex MCP guide also explains the matching config.toml entries.

After connecting, choose Astra in Codex for the conversation; Codex handles the MCP connection. Astra is the model, while Codex is the client that connects it to INK TO BRICK.

What Codex can do after connecting

• Read a floorplan workspace and revision history after you supply its project ID from the dashboard URL.
• Search the fixture catalog and review saved aesthetic options.
• Prepare questions about saved Design Options and review the current state.

Worth checkingSelf-serve Codex connections are read-only. Contact us to register an editing client that supports preview and confirmation. The server also does not upload a floorplan, start reconstruction, generate a photoreal image, export a scene or control Blender. Use the web app or API for those operations. Blender automation needs Blender Python or a separate Blender MCP server.

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 repeatable examples that respect the preview-and-confirm boundary, continue with MCP floorplan workflows.