For thirty years, construction has been building files.
RVTs, PDFs, IFCs, contracts, specifications. Terabytes of project knowledge accumulated across tools that were never designed to talk to each other. The US industry alone loses $16 billion annually to poor interoperability. Up to 90% of project data goes unused. Teams spend more than half their day not designing — just translating between systems.
We do not have a data problem. We have an access problem.
The answer is not a new platform. It is a coordination layer — one that wraps what already exists and makes it readable by the agents that can finally help us act on it. That layer is called MCP. Model Context Protocol turns your existing APIs, tools, and documentation from static to surfable.
The thing that gets chosen is not the best product. It is the most readable one.
We saw this play out in software: tools that structured their documentation for agents became the default recommendation across millions of AI interactions — not because they were better, but because they were easier to reach. The same logic applies to AEC. The winners will not be those with the best systems. They will be the most agent-ready data interface in the room.
Autodesk is moving. The APS MCP server is now in beta, with working examples of how to wrap AEC data into a layer that agents can access and act on.
But a single MCP server is a pipe. The real capability comes when you compose it: a Skill that teaches the agent your domain, an MCP server that handles authentication and structured retrieval and an MCPApp that renders results directly in the conversation. Not three separate tools. One Extension Bundle. No rip-and-replace. The data you already have has finally become surfable.
The files are not changing. The models are not changing.
What is changing is that the data is finally becoming surfable.
What is changing is that the data is finally becoming surfable.