Connect your AI to Construction Takeoff

1. Choose Export connection files… and save them in a folder you will keep. The connection runs those files, so leave that folder in place.
2. Choose Choose Python… and select the python3 executable from your Python 3.10+ installation. In the file picker, press ⌘⇧G to enter its folder.
3. Choose Copy configuration. It includes your selected Python and exported file paths.
4. Add it to your client’s settings below. Merge it with existing settings, preserving other servers. Quit and reopen the client, then run the connection check.

Common Python locations: /Library/Frameworks/Python.framework/Versions/Current/bin/python3 for Python.org, or /opt/homebrew/bin/python3 for Homebrew on Apple silicon. Select the executable that exists on your Mac. Exporting does not install Python or change client settings.

1. Choose Set up for your client. Continue in the Construction Takeoff AI Setup window.
2. Review the prerequisite checks. If Python is missing, install it using the provided link and choose Check again.
3. Choose Install connection. The helper installs the companion and the selected client connection. Claude Code also needs its command-line tool; Codex desktop and Claude Desktop do not.
4. Follow the client reload instructions. For Codex, if the plugin is not enabled, open Plugins, select the local source and install Construction Takeoff. Start a new chat and run the connection check below.

Local setup checked confirms the helper passed its check. Your AI session still needs to load and call it. Manual export and diagnostics are available under Advanced setup & help.

The app copies TOML for Codex. Merge its [mcp_servers.construction-takeoff] section and environment section into ~/.codex/config.toml. Avoid adding a second section with the same name. Restart Codex and start a new local chat.

If using an installed Construction Takeoff plugin, keep that connection instead of adding a duplicate manual server. Official Codex MCP configuration.

Open Claude → Settings → Developer → Edit Config. Merge the copied construction-takeoff entry into the existing mcpServers object in ~/Library/Application Support/Claude/claude_desktop_config.json.

Save, fully quit and reopen Claude Desktop, then enable the connection in a new conversation. This is separate from Claude Code and needs no Claude Code installation. Local MCP setup reference.

For a project connection, merge the copied mcpServers JSON into .mcp.json at that project’s root. Start Claude Code in that project, approve the project server when prompted, and use /mcp to check its status. Keep machine-specific paths out of shared configuration.

For a personal connection across projects, use claude mcp add-json --scope user construction-takeoff '…', replacing … with only the server object under mcpServers.construction-takeoff, not the entire copied document. See Claude Code’s JSON configuration instructions.

Merge the copied entry into mcpServers in ~/.cursor/mcp.json for all projects, or .cursor/mcp.json for one project. Preserve other servers. Run Developer: Reload Window, check the connection in Customize, then start a new chat.

If native setup installed the local plugin, find Construction Takeoff in Customize instead of adding a second manual entry. Cursor MCP configuration.

Check for an app update. Older builds may use 3D Model → AI tools → Export MCP companion or Export AI setup; follow the instructions bundled with that export. The separate Codex preview download documents the older plugin route. Installing a plugin alone does not install its companion.

Fully restart the AI client and start a new local chat. Check that the exported folder still exists and that the configured Python is 3.10+. Re-select Python and copy the configuration again if needed. Fix JSON/TOML syntax errors without replacing unrelated settings. If your build offers it, use Advanced setup & help → Copy diagnostics.

An empty project list can be a working connection. Save the project in the app’s library, then check the folder reported by health. A custom library can be configured through TAKEOFF_PROJECTS_DIR. For missing linework tools, install PyMuPDF in the exact Python environment selected for the connection, then restart the client. Basic connection checks do not require PyMuPDF.

Keep one working registration: either the plugin or the manual MCP entry. Disable an older duplicate only after the new connection passes its check. If health reports multiple app instances, save your work and close the extra copy, or have your AI client select the intended project and app instance.

This companion has no HTTP endpoint or remote sign-in. Use a local client on the Mac. Cloud-only access needs a separately supported, authenticated bridge; it is not provided by this connection setup.