Knowledge · Technology
What MCP means for builders,
your AI assistant, inside your jobs.
MCP is the open standard that lets the AI assistant you already use read your jobs, costs and claims from your construction software and draft records in it, while a person still sends, approves and pays. This reference explains the protocol plainly, lists what a builder can actually ask, draws the line at what an agent should never be allowed to do, and records which construction software has a server today.
Written by Brad Caldon, Founder, VIABUILD. Licensed builder (NSW) · Registered Building Practitioner (Class 1 to 9) · B.Construction Management (Hons) · Last reviewed 15 September 2026
01 / Overview
What MCP is
MCP, the Model Context Protocol, is an open standard that gives an AI assistant a consistent way to find out what tools another system offers and to call them. For a builder it means Claude, ChatGPT or another assistant can ask your construction software a question about a live job and get an answer computed from the real records, or draft a purchase order, a bill or a claim that lands in the software as a draft for a person to check. It is not the intelligence inside the software; it is the door that lets the intelligence you already use reach it.
The protocol was published by Anthropic in late 2024 as an open specification and has since been adopted across the major AI clients, which is why one server can serve several assistants. A vendor that runs an MCP server has decided, tool by tool, what an outside agent may read and what it may change. That decision is the whole product. The same word covers a connector that can only list jobs and one that can pay bills, and the questions in this reference are how you tell them apart.
Why it matters to a building business
Most of what a builder asks of their software is a question, not an action. Where is this job against budget. What have we claimed. What is owed to this supplier. Today those questions are answered by opening the right screen, reading the right report and sometimes reconciling two of them. An assistant connected through MCP answers them in a sentence, from the same numbers the screen would show, because the software computed them. The assistant did not remember a figure from a PDF it read last month, which is the failure mode that makes general-purpose chatbots dangerous around money. The value is not that the AI is clever; it is that it is finally looking at the record.
02 / How it works
The protocol, plainly
Six steps from a question in plain English to an answer from your own records, and the two design decisions that decide whether a connector is safe.
- 01
Your software runs a server
The vendor exposes an MCP server for your workspace. It publishes a list of tools, each with a name, a plain description and the fields it accepts, for example list_jobs or get_claims_position. The server decides what each tool returns and what it is allowed to change.
- 02
Your AI client connects to it
Claude, ChatGPT or another assistant that supports MCP is given the server’s address and a credential. It asks the server what tools exist. Nothing is copied into the assistant; the tool list is all it learns at this point.
- 03
You ask a question in plain English
The assistant works out which tool answers it, calls that tool with the right arguments, and reads the result. “Which jobs are over budget” becomes a call to the profitability tool for each active job, then a sentence you can read.
- 04
The answer comes from live records
The figures are computed by your construction software on the server at the moment you ask, not remembered by the model from a document it once saw. That is the difference between an assistant that knows and one that guesses.
- 05
Writes preview before they land
Where a server allows the assistant to create something, a well-designed one returns a preview first and writes only when asked again. The record then appears as a draft in the software, exactly as if a person had typed it.
- 06
A person still commits
Sending an order, approving a bill, paying, and writing to the ledger are the actions a server should keep for people. If a connector can do those on its own, that is a control problem, not a feature.
Two details do most of the work. The first is that the server publishes descriptions of its tools, so the assistant can choose the right one without a developer wiring it up; that is what separates MCP from an ordinary API, which needs someone to write code against it. The second is that the server, not the assistant, decides what a tool returns and what it may change, so the controls live with the vendor of the record rather than with whoever built the chatbot. Read a vendor's MCP page for those two things: the tool list, and the write rules.
03 / In practice
What a builder can ask Claude or ChatGPT about their jobs
Eight questions a connected assistant answers from live records, taken from what VIABUILD’s connector exposes today. The first six are reads; the last two draft something for a person to finish.
Where do my active jobs sit against budget?
Budget, committed, actual and forecast per cost code, read from the job, so the answer names the codes that moved rather than a total.
What have I claimed, been paid, and still have to claim on each contract?
The claims position per job, computed live, so the assistant’s answer matches the screen.
What have I spent with this supplier this year, and what is still on open orders?
Invoiced spend ranked by supplier plus open commitments, which is the number you want before a pricing conversation.
What is starting on site this week, and what is overdue?
Upcoming and overdue tasks across jobs, including the critical path, without opening the schedule.
Which supplier bills are waiting for approval, and which have no purchase order?
The accounts payable queue with each bill’s match state, so the unmatched ones are the ones you look at.
Draft the orders for the frame package on Lot 14.
A draft purchase order per supplier, bound to the cost code, previewed first. You send them from the software when you are ready.
How did the estimate on this job compare with what it actually cost?
Estimate line items against the job’s actuals, which is the close-out comparison most builders never get around to.
Log a lead for the couple I met on Saturday.
A lead record with the details you dictate, created as a draft the office can pick up on Monday.
04 / The line
What an agent should never be allowed to do
Controls that belong in the server, enforced by the vendor, not left to the assistant’s good behaviour.
Send anything to a supplier or client
A purchase order, claim or email leaves only when a person sends it from the app.
Approve or pay a bill
Approval workflows, payments and writes to Xero stay with people, by design.
Change a sent order’s amounts
Once an order has gone to a supplier, its identity is read-only to any agent.
See a workspace it was not given a token for
A token belongs to one workspace and carries only the scopes it was issued with; banking details are never returned.
These are the guardrails from AI guardrails in construction applied to a connector: a human commits everything, high stakes forces review, and the system says no rather than guessing. A connector that previews every write and refuses to send, approve or pay is not a cautious version of the idea. It is the idea, done properly, because accountability for a raised claim or a paid bill stays with the business whatever software prepared it.
05 / The field
Which construction software has an MCP server
Each line records what the vendor’s own product or developer pages documented when checked on 3 September 2026. Where nothing was found, the wording is “no vendor MCP found”, which is a statement about the vendor’s pages, not its roadmap.
| Dimension | VIABUILD | What it covers |
|---|---|---|
| VIABUILD | Yes. VIABUILD MCP, part of the platform: read tools over jobs, costs, claims, estimating, purchasing, contacts and documents; draft writes with preview first; every call logged. Verified claude.ai, Claude Desktop and Claude Code. | Included in the subscription, enabled per workspace. |
| BuildPass | Yes. BuildPass MCP, documented on the BuildPass site. Runs as the signed-in user with their permissions and audit trail, over site safety, quality and site records. | Site records, not estimating, orders, bills or claims. |
| JobTread | Yes. JobTread AI Connector, an MCP server, launched 16 April 2026. | United States product; confirm the tool list for Australian workflows. |
| Bluebeam | Yes. Bluebeam MCP server, Revu 21.9 or later, Bluebeam Max subscription, desktop only. | Markups and measurements on the desktop, not a job or cost record. |
| Autodesk Construction Cloud | Beta. Autodesk support (15 January 2026) says trusted MCP servers are planned, with beta prototypes via its feedback programme. | Not generally available when checked. |
| Procore | Unable to verify a Procore MCP server. Procore AI acts as an MCP client, taking custom server connections for live record access. | The direction of the connection is the other way around. |
| Buildertrend | No vendor MCP found. AI Client Updates and AI Bill Capture are the shipped AI; an agentic platform is a stated direction after its July 2026 acquisition. | “Buildertrend MCP” is a search, not a product, at the time of writing. |
| Buildxact, Wunderbuild, Nexvia, Databuild and the rest of the field | No vendor MCP found on their own product or developer pages. Buildxact publishes an API and webhooks; most publish neither. | An API is not an MCP: it needs a developer, not an assistant. |
Sources, dimension by dimension with URLs, are on each product's comparison page under AI agent connectivity, for example BuildPass, JobTread and Buildertrend. Vendors ship quickly here; confirm current availability directly before you decide.
06 / Practical example
A Monday morning, connected
Illustrative only. A builder running six homes opens Claude on the phone before the first site visit and asks which jobs are committed beyond budget. The assistant calls the profitability tool for each active job and answers: two jobs, frame on Lot 14 by $3,500 after the subcontract was let, and electrical rough-in on the Smith renovation by $1,100 on a variation not yet priced. The builder asks what is outstanding to the framing subcontractor and gets the open orders and the unpaid bills. Then: draft the variation for the Smith electrical change at $1,650 plus GST. The assistant previews the variation, the builder says go, and a draft appears in the software. In the office an hour later, someone opens it, checks the wording and sends it to the client from the app. Nothing was sent, approved or paid by the assistant; three screens and one report were never opened.
07 / FAQ
Common questions.
MCP, the Model Context Protocol, is an open standard that gives an AI assistant a consistent way to discover and call the tools another piece of software offers. Your construction software runs a server that lists what it will let an assistant do, the assistant asks it questions or asks it to draft records, and the software answers from live data and decides what may change. It is the door between the AI you already use and the system that runs your jobs.
No. Intelligence inside the product, Oryn in VIABUILD’s case, reads plans and invoices and brings context to the screen you are on, whether or not any external assistant is connected. MCP is the connection that lets an assistant outside the product reach the same understanding. One is a feature of the software; the other is a way in for the tools you already open every day.
Through a well-designed server, no. Sending, approving, paying and writing to the ledger are the actions a construction system should keep for people, and VIABUILD’s connector does not expose them. An agent can draft the order or file the bill; a person sends and approves in the app. If a vendor’s connector can pay a bill on its own, ask how that is controlled before you connect it.
On the vendors’ own product and developer pages as at 3 September 2026: VIABUILD, BuildPass, JobTread and Bluebeam document one. Autodesk Construction Cloud has one in beta. Procore’s AI is a client rather than a server. Buildertrend, Buildxact, Wunderbuild, Nexvia, Databuild and the rest of the Australian field publish none. Vendors ship quickly in this area, so treat the table on this page as a dated check rather than a permanent verdict.
It depends on what the connector exposes and how it is controlled. Look for scopes, so a token can be read-only or limited to one area; per-workspace isolation; a log of every call; and the ability to revoke a token instantly. Never returning banking details is a good sign. Personal information in job records, client names and addresses for example, is still yours to protect under the Privacy Act, so treat the assistant as a third party you are sharing it with and read its data terms. This is general information, not legal advice.
08 / Terms
Glossary for this topic
MCP server (the vendor's side, which publishes tools and enforces the rules), MCP client (the assistant that connects), tool (one named action or query the server offers), scope (the set of tools a credential is allowed to use), dry run or preview (a write that returns what it would do without doing it), token (the credential that identifies a workspace and its scopes), audit log (the record of every call). The wider vocabulary lives in the construction glossary. What VIABUILD's own connector reads and writes, tool by tool, is on the VIABUILD MCP feature page.
09 / Keep reading
Related knowledge, features and comparisons
Ask your jobs a question.
VIABUILD includes an MCP server, so the assistant you already use can read live job, cost and claim data and draft records with a preview first. Sending, approving and paying stay with a person. Enabled per workspace, no extra charge.