AI connectors

What a connector is

SitesAI publishes two MCP servers (Model Context Protocol — the open standard AI assistants use to reach external systems). Once you connect one, you can ask your AI assistant questions about your own worksite data in plain language — “which jobs are quoted but not scheduled?”, “what did we cut on the Kilsyth site?” — and it answers from the live records in your account.

• SitesAI App connector — your field-operations data: leads and quotes, tasks, sites, services and items, worktime and rostered shifts, signed dockets, members, site documents and subcontractor compliance, NFC/QR tags, processes and checklists. Endpoint: https://app.sitesai.net/api/mcp/mcp (add ?profile=full for every tool — see tool profiles)
• SitesAI Estimate connector — your takeoff and estimating projects: plan layers, sheets, take-off groups, earthworks elements and the estimate itself. Endpoint: https://takeoff.sitesai.net/api/mcp

Both speak MCP streamable HTTP over HTTPS and support OAuth 2.1 (authorisation code + PKCE) as well as personal API keys.

Turning a connector on

Connectors are off by default — nothing is shared with any AI assistant until you deliberately connect one.

1. Check your plan. The SitesAI App connector requires the AI add-on on your company; SitesAI Estimate requires the AI plan on your account — or start the free 14-day AI trial in the app (Account menu → Start free AI trial; no card, one per account).
2. Add the connector in your AI client using the endpoint above, then complete the sign-in it prompts for. On the SitesAI App the consent screen is restricted to company owners and managers, and it is where you choose what the connection can do — read-only, or read and write. Write access is never automatic: unless an owner or manager picks the read-and-write option on that screen, the connection is read-only and every write tool refuses.
3. Or use an API key — create one at app.sitesai.net/ai-keys (SitesAI Estimate: Account menu → AI assistant access (MCP)) and paste it into your AI client. A key can be read-only or read-and-write, and belongs to one company.

SitesAI Estimate, client by client

The connector address is https://takeoff.sitesai.net/api/mcp. Keep a signed-in SitesAI Estimate tab open while the assistant works — changes render in front of you.

• Claude (claude.ai or the desktop app) — Settings → Connectors → Add custom connector → paste the address → sign in with your SitesAI Estimate login. No token.
• Claude Code — claude mcp add --transport http 3dx https://takeoff.sitesai.net/api/mcp; a browser window opens to sign in.
• Codex (desktop) — in the app: Account menu → AI assistant access (MCP) → Create token. In Codex: Connect to a custom MCP → Name 3DX, Type Streamable HTTP, the address, and one header Authorization: Bearer <your token>.
• Codex CLI — in ~/.codex/config.toml: [mcp_servers.threedx] url = "https://takeoff.sitesai.net/api/mcp" http_headers = { Authorization = "Bearer <your token>" }.
• ChatGPT — Settings → Apps & Connectors → Advanced → turn on Developer mode → Create a connector with the address → sign in. (Menu names checked 3 October 2026; they move between releases — the address and the sign-in do not.)

Want the assistant to price jobs with your rates and factors every time? Read Teach Claude or Codex to price jobs your way and download the starter skill.

Revoking access: every key and every OAuth connection is listed at app.sitesai.net/ai-keys and can be revoked at any time — it stops working immediately.

What a connected assistant can and cannot see

• It sees the data of one company only — the company the key or consent belongs to. Every request is scoped to that company on our servers, so a connector can never reach another company's records.
• Read tools and write tools are separate tools, each labelled with what it does, so your AI client can ask you before anything is changed. A read-only key or OAuth connection cannot call the write tools at all.
• Requests are rate-limited per key and recorded in the company's AI audit log (purged after 90 days).
• Data returned to your AI client is then handled by that provider under their policy — see our Privacy Policy, section 8.

SitesAI App — tools

The App connector exposes 148 tools: 71 read tools and 77 write tools. Every one is listed below.

Tool profiles. Some AI hosts cap how many tools a connector may offer, so the App connector serves a chosen subset — add ?profile= to the endpoint. ops (91 tools) is the default and needs no query string: the everyday operating set. lite (18 tools) is the small inbox / phone-agent set, and full (148 tools) is everything, including the builder and admin tools. Same key, same data — only the tool list differs, and every tool listed on this page is in full.

Read tools (safe, never change anything):

Write tools (only reachable with a read-and-write key or connection; each is a single, narrow action). They come in three kinds, and each tool carries that kind as a machine-readable MCP annotation, so your AI client knows which is which before it runs one:

Add something new — creates a record and overwrites nothing (annotated not destructive): create_lead, create_lead_type, create_quote, add_quote_line, create_account, create_contact, offer_action, add_comment, create_process, create_sop, add_sop_next, create_checklist, assign_flow, register_tag, file_capture, create_doc_type, create_document, submit_document, assign_to_site, grant_site_company, add_process_step, start_flow_offer, create_job_site, create_contract, record_stock_use, create_action, assign_action, plan_shift_actions, create_sow_item, import_quote_sow, issue_progress_claim.

Change or remove something that already exists — annotated destructive, so your AI client can ask before it runs: attach_lead_contact, detach_lead_contact, update_lead_type, update_quote_line, delete_quote_line, update_account, delete_account, update_contact, delete_contact, update_worktime, delete_lead, delete_task, update_comment, delete_comment, update_process, update_sop, remove_sop_next, unassign_flow, revoke_tag, update_capture, update_doc_type, set_site_document_requirements, review_submission, revoke_site_company, remove_process_step, move_process_step, set_process_steps, delete_process, delete_sop, void_contract, update_action, update_sow_item, unassign_action.

Reaches a person outside the app — these email or notify someone as well as changing a record, so they are annotated destructive and open-world (the message cannot be recalled): update_quote, create_task, create_shift, respond_shift, cancel_shift, reoffer_shift, create_shifts_bulk, reassign_shift, update_lead, update_task, add_member, send_contract_for_signature, send_variation_for_approval.

SitesAI Estimate — tools

SitesAI Estimate can run live in your open browser tab (changes appear as the assistant makes them) or in background mode without a tab. Deeper technical notes are in the product's MCP documentation.

Things to ask

• “Which leads came in this month and which of them still have no quote?”
• “Who is rostered on the Ringwood site tomorrow, and did anyone not show up today?”
• “Summarise the worktime logged against job 142 last week.”
• “Which dockets from last week are still unsigned, and who was the operator on each?”
• “Whose licences and insurances expire in the next 30 days, and which sites are they short on?”
• “Open my Kilsyth plan, calibrate the scale from the 10 m bar and give me the cut and fill volumes.”
• “Price the bulk excavation line at $28/m³ and show me the new estimate total.”

Questions, answered

Support

Trouble connecting, or a tool doing something you didn't expect? Email admin@sitesai.net — we usually reply within one business day. See also our support page and privacy policy.