Construction AI

Agents

Your agent. Your projects.

Connect Claude, Microsoft 365 Copilot or any MCP client to Construction AI. It reads your projects with your permissions and does the work in your system of record, so an answer in a chat window is a change in the programme, a row in the rate book, a figure from the ledger.

Connect your agentSee the 149 tools
ClaudeConstruction AI connected
Message Claude…
Construction AI·Library › Rate books › Master rates 2026
Library › Schedule of Rates › 001
001 — Master rates 2026
Construction AISavedExport
Nett
£1,686.42
cost before markup
Sell
£1,747.97
what tenders receive
Margin
£61.55
3.5% margin
6 sections · 18 rates+ Add column
RefDescriptionQtyUnitUtil %RateTotal
7Mechanical — Copper pipework(8)£296.90
7.001Copper tube 15 mm, BS EN 1057 R250, clipped to wall1m10018.40£18.40
7.002Copper tube 22 mm, BS EN 1057 R250, clipped to wall1m10024.10£24.10
7.003Copper tube 28 mm, BS EN 1057 R250, on brackets1m10031.60£31.60
7.004End-feed elbow 15 mm1nr1006.20£6.20
7.005End-feed equal tee 22 mm1nr1009.80£9.80
7.006Isolation valve 15 mm, full bore lever1nr10014.50£14.50
7.007Pipe insulation 22 mm, 25 mm wall, foil faced1m1007.30£7.30
7.008Pressure test and flush per circuit1item100185.00£185.00

Connector URL

https://app.constructionai.io/api/mcp

How it works

Bring your agent, or use ours. Either way it works inside your system of record.

Construction AI·Claude › Settings › Connectors
Claude› Settings › Connectors
Your connectors
Google DriveConnected
SlackConnected
Construction AI Connected · Sam Okafor
+ Add custom connector
Add custom connector
Construction AI
No API key. You sign in when you connect.Add
app.constructionai.io › Sign in
sam@northgate.build Access granted
01

One URL. A sign-in. No installer.

Claude, Microsoft 365 Copilot or any MCP client adds Construction AI as a connector. You sign in as yourself, and from then on the agent acts as you, with your access and nothing more.

  • Nothing on your machine: your client holds a token you can revoke at any time.
  • Claude Desktop, Claude on the web and Copilot are tested end to end; scripts use an API key instead.
  • The same 132 tools are there for every client, read and write, under your permissions.
Connect Claude
Construction AI·Mission Control › Sam Okafor
Mission Control
Sam Okafor · Thursday 10 September · briefed at 06:30
Construction AI
Two things need you today and one needs a decision. RFI-042 has been open nine days and Marlow cannot fix the deck steel without it; certificate 4 is ready to sign. The plinth drawing moved without an RFI — that is the one to look at.
Needs you · 3
Answer RFI-042 on the AHU plinth loads — Marlow are waiting on it before the deck steel is fixed
RFI-042 · 9 days openDue Fri
Confirm the reception bulkhead detail before CCI 003 is instructed
Diary DB-035 · CCI 003 draftDue Mon
Sign certificate 4 — £437,204 net, final date for payment 27 Sep
Application 4Due 24 Sep
Escalations · 2
Drawing 63001 revised to P05 without a linked RFI while RFI-041 and RFI-042 on the same plinths sit unanswered
Drawings · RFIs
Inspection IN-012 two days overdue with the crane lifts a fortnight away
Inspections · Programme
Briefings can be wrong. Every line cites its source; the record is the truth.
02

Agents that run without being asked

Inside the platform, agents read the project on a schedule: the brief, the knowledge and its Time Machine, the weekly and monthly summaries, and each person's Mission Control briefing.

  • A briefing is written for one person: what needs them, what needs a decision, with every line cited.
  • Nothing acts silently. An agent's output is a version with its trail; a person signs it off.
  • The programme and take-off agents build and measure inside the product when you ask.
Why oversight has to change
Construction AI·app.constructionai.io › Grant access
Claude Desktop is asking to access Construction AI
as Sam Okafor · Northgate Contracts
Access requested
  • Projects
  • Drawings and specifications
  • Programme
  • Communications, RFIs and submittals
  • RAMS
  • Site management
  • Tender packages
  • Library and project knowledge
  • Financial headers
Advanced — commercially sensitive
  • Financial detail — CVR, margin, valuationsoff by default
  • Pricing — tender and contract pricingoff by default
  • Purchase ledgeroff by default
  • Write: library, projects, documents, contactsoff by default
  • Ask the in-app assistantoff by default
Restrict to projects
All my projects Selected: Larkspur House
Grant expires in90 days ▾
Grant access
03

You decide what it can see, per client, per project

The consent screen is the whole contract. Standard scopes are on; commercially sensitive reads and every write are off until you tick them; you can limit a grant to particular projects and say when it ends.

  • A connection never has more access than the person who granted it.
  • Different clients can have different grants: read-only for one, writes for another.
  • Every call lands in the audit log against you, with the tool, the scope and the project.
What your agent can see
Construction AI·Tool catalogue
  • find_team_plan_actionsSearch project plan activities across one project or the whole portfolio. This is how to answer "what is overdue and who is holding it", "what does a person owe", or "what is unassigned".
  • get_cost_codeGet a single cost code by its code string (e.g. "4.3.2"). Returns description, parent code/description, hierarchy level, and category metadata. Org-scoped — the same code may resolve differently per tenant.
  • get_projectGet full details for a single project by its UUID. Returns name, status, client, location, and date span — but never internal financial figures (contract sum, margin, forecasts).
  • get_project_activityList recent activity log entries — agent actions recorded across all surfaces (MCP clients, Dave, dashboard UI).
  • get_project_contextFetch the project's claude.md rulebook — per-project rules and conventions the agent should respect.
  • get_project_knowledgeFetch the project's auto-synthesised operational-state knowledge — what's open, what's drifting, what's anomalous right now.
  • get_project_look_aheadForward-facing 14-day view of items needing attention — RFIs due in the next 14 days, submittals due, RAMS pending approval, variations sitting un-agreed for more than 14 days, plus any overdue items.
  • get_project_monthly_rollupFetch the latest auto-synthesised monthly rollup for a project — themes and patterns across the prior month's weekly summaries. Generated on the 1st of each month at 17:00 UTC.
  • get_project_overviewFetch the project's auto-synthesised scope overview — what IS this project. Headline, scope of works by trade, programme summary, likely tender packages, constraints noted in specifications.
  • get_project_summarySingle-call roll-up of project state — counts of key entities (open vs total) across PM, Site, Tenders and Financial modules. The "give me an overview" tool — answers what would otherwise need 10+ separate list_* calls.
  • get_project_weekly_summaryFetch the latest auto-synthesised weekly summary for a project — "what changed and what mattered this week". Generated every Friday at 17:00 UTC for knowledge-enabled projects.
  • get_team_planRead one project plan in full — every activity with owner, due date, status, phase, priority, progress and recurrence.
  • list_cost_codesThe organisation's cost codes, the NRM breakdown that connects every module, so names resolve to codes.
  • list_project_documentsList documents stored under a project — drawings, specs, contracts, H&S policies, anything the user has uploaded. Returns metadata only (name, content_type, size, folder path, version).
  • list_projectsThe projects you can see, by name or number, so every other tool has the project it needs.
  • list_team_plansList the project plans on a project, each with its open / closed / overdue counts. A project can hold several plans — procurement, daily duties, pre-construction. Use find_team_plan_actions to see the activities.
  • read_documentFetch a project document's metadata plus a signed download URL. Optionally inline the bytes when include_content=true and the file is under 1 MiB (base64 for binary, plain text for text/markdown/csv/json).
04

149 tools, generated from the server itself

Every module is reachable: 124 reads and 25 writes, grouped by the scope that unlocks them. The list on this page is built from the server's own tool files, so it cannot drift from the product.

  • Reads cover projects, drawings, specifications, programme, communications, RAMS, site, tenders, the library and the ledgers.
  • Writes cover the library, project context, documents, contacts, pricing and the purchase ledger.
  • Building a system integration instead? The same data is on the public REST API.
Public API overview

Every tool, by what you allow

Every tool sits under a scope. Read scopes for the everyday modules are on by default; commercially sensitive reads and every write are off until you grant them. Generated from the server itself.

  • find_team_plan_actionsSearch project plan activities across one project or the whole portfolio. This is how to answer "what is overdue and who is holding it", "what does a person owe", or "what is unassigned".
  • get_cost_codeGet a single cost code by its code string (e.g. "4.3.2"). Returns description, parent code/description, hierarchy level, and category metadata. Org-scoped — the same code may resolve differently per tenant.
  • get_projectGet full details for a single project by its UUID. Returns name, status, client, location, and date span — but never internal financial figures (contract sum, margin, forecasts).
  • get_project_activityList recent activity log entries — agent actions recorded across all surfaces (MCP clients, Dave, dashboard UI).
  • get_project_contextFetch the project's claude.md rulebook — per-project rules and conventions the agent should respect.
  • get_project_knowledgeFetch the project's auto-synthesised operational-state knowledge — what's open, what's drifting, what's anomalous right now.
  • get_project_look_aheadForward-facing 14-day view of items needing attention — RFIs due in the next 14 days, submittals due, RAMS pending approval, variations sitting un-agreed for more than 14 days, plus any overdue items.
  • get_project_monthly_rollupFetch the latest auto-synthesised monthly rollup for a project — themes and patterns across the prior month's weekly summaries. Generated on the 1st of each month at 17:00 UTC.
  • get_project_overviewFetch the project's auto-synthesised scope overview — what IS this project. Headline, scope of works by trade, programme summary, likely tender packages, constraints noted in specifications.
  • get_project_summarySingle-call roll-up of project state — counts of key entities (open vs total) across PM, Site, Tenders and Financial modules. The "give me an overview" tool — answers what would otherwise need 10+ separate list_* calls.
  • get_project_weekly_summaryFetch the latest auto-synthesised weekly summary for a project — "what changed and what mattered this week". Generated every Friday at 17:00 UTC for knowledge-enabled projects.
  • get_team_planRead one project plan in full — every activity with owner, due date, status, phase, priority, progress and recurrence.
  • list_cost_codesThe organisation's cost codes, the NRM breakdown that connects every module, so names resolve to codes.
  • list_project_documentsList documents stored under a project — drawings, specs, contracts, H&S policies, anything the user has uploaded. Returns metadata only (name, content_type, size, folder path, version).
  • list_projectsThe projects you can see, by name or number, so every other tool has the project it needs.
  • list_team_plansList the project plans on a project, each with its open / closed / overdue counts. A project can hold several plans — procurement, daily duties, pre-construction. Use find_team_plan_actions to see the activities.
  • read_documentFetch a project document's metadata plus a signed download URL. Optionally inline the bytes when include_content=true and the file is under 1 MiB (base64 for binary, plain text for text/markdown/csv/json).

Building your own integration? The same data is on the public REST API.

Questions

Which agents can connect?
Any client that speaks the Model Context Protocol over HTTP with OAuth sign-in. We have tested Claude Desktop, Claude on the web and Microsoft 365 Copilot end to end. Scripts and headless agents connect with an API key instead of a sign-in.
What can my agent see?
Exactly what you grant on the consent screen when you connect it, and never more than you can see yourself. Standard scopes such as projects, drawings, RFIs and RAMS are on by default. Commercially sensitive scopes such as pricing, financial detail, the purchase ledger and every write scope are off until you turn them on. You can limit a grant to particular projects and set when it expires.
Can it change my data?
Only through the 25 write tools, only when you have granted a write scope, and only within the projects you allowed. Every write is attributed to you and recorded.
Does it cost anything extra?
The connector is part of the platform. The agent itself is yours: Claude or Copilot bill you for the conversation as they always do. Asking our in-app assistant through the connector uses your own Claude key.
Is my data shared with the agent provider?
Your agent receives the answers to the calls it makes, the same as a person reading the screen. Nothing is shared in bulk, nothing leaves your tenant except in answer to a call you authorised, and your organisation’s data is isolated from every other tenant.

Ready to manage construction properly?

Tier-one processes for the whole business. One platform, every user, AI included — priced to your business.