Construction AI: the standard your BIM tools quietly plugged into goes official today, and UK architects hit an AI tipping point

Here's a launch that won't make the trade press front pages and probably should. Today, 28 July, the Model Context Protocol publishes its 2026-07-28 specification. The release candidate went out on 21 May, and the maintainers call this the largest revision of the protocol since it launched. If you've never heard of MCP, that's fine. What it is, plainly, is the common connector that lets an AI assistant read and act inside a piece of software without someone hand-building a one-off integration for every tool.

And this is where it stops being an abstract standards story and becomes a construction one. Over the last few months the AEC vendors have quietly wired themselves into it. Autodesk shipped a Revit MCP server in technical preview as part of Revit 2027, read-only for now, seven tools that let an assistant query the model, pull element data and export views, and it auto-configures with Claude Desktop and Cursor on install. Bentley released MCP servers for STAAD.Pro and MicroStation. Bluebeam Max plugs Claude into Revu so you can drive markup workflows in plain English. Trimble's SketchUp connector lets you model from a photo or a sketch. Different companies, different products, one standard underneath. That's the point of a standard.

So what actually changed today? Two things worth caring about. The protocol goes stateless, which means the old session handshake and the session-id header are gone, and any request can land on any server. In practice that makes these servers cheaper to host and far easier to scale, which matters because it's the difference between a vendor demo and something that holds up when your whole team hits it at once. The second thing is the one a regulated sector should read twice: authorisation now aligns with OAuth 2.1 and OpenID Connect, and the Enterprise-Managed Authorisation extension has been promoted to stable. What that means on the ground is your IT team can control which agents reach which systems through the identity provider you already run, rather than every tool inventing its own back door. I'm not going to pretend the Revit server is finished, it's read-only, and the write version that would let an agent actually change your model is a separate piece still in development. But the direction is set.

The comparison I keep coming back to is the day the industry settled on a common thread for scaffold fittings. Dull, invisible, nobody wrote a headline about it. It's also the reason kit from three different suppliers now clips together on your job. MCP is that, for AI and your software. The person who benefits isn't the CTO reading the spec. It's the QS who wanted the takeoff tool to read the model rather than chat about it, and the document controller who'd quite like one assistant that works across Revit, the CDE and the drawing store instead of three that don't talk.

Today's action: next time a vendor pitches an "AI assistant" for your BIM or document tools, ask two things. Does it speak MCP, and does it use the new enterprise authorisation so we can govern it centrally? If the answer's a shrug, you've learned what you're buying.

Around 23 July, RIBA published the third round of its AI survey of members, and the headline number is a genuine step change. The share of practices using AI on most of their projects has gone from 59% in 2025 to 74% in 2026. On the upside, 75% report a productivity improvement and 57% say they're seeing a positive return. Adoption like that, in a profession that's usually cautious about new kit, isn't noise. It's a line crossing.

But read past the adoption figure and the mood is careful, not celebratory. 59% of practices think AI will lead to staff reductions across the profession. And 61% agree it'll make life harder for early-career people trying to build the skills and experience that make them any good. That second one is the number I'd sit with. The way you learn to run a job, in architecture or on site, is by doing the slow manual version first, badly, and feeling where it goes wrong. We're quietly automating away exactly that version, and nobody's quite worked out how the next generation gets the reps instead.

Now, I'd hedge on the productivity self-reports. People always feel faster with a new tool, and "75% report an improvement" is a feeling, not an audited timesheet. The comparison only goes so far, but it's a bit like asking drivers if the new sat-nav made them quicker, they'll say yes whether or not it did. The adoption jump, though, is a hard behavioural number, and it's steep. Worth noting this lands the same week the RICS mandatory AI standard, live since 9 March, is already requiring firms to keep a written risk register and dip-sample their AI outputs. So the profession that's adopting fastest is also the one already being told to document how it's doing it. That's the healthy version of this.

The reason a contractor should read an architecture survey is timing. Design tends to run a couple of years ahead of construction on tools like this. So treat these numbers as your weather forecast. The person it lands on isn't the practice principal quoted in the press release. It's the Part 1 who now spends less time on drudgery, and, without anyone deciding it, less time learning what the drudgery was quietly teaching them.

Practical bit: if you employ or train junior staff, write down which tasks your AI tools now do that people used to learn from, and decide deliberately how those people still get that learning. Don't let it happen by accident.

Put the two stories side by side and they're the same story from opposite ends. Today's MCP standard makes it cheap and easy to point an AI agent at your systems. RIBA's survey shows the profession is doing exactly that, fast. The thing sitting between "we adopted it" and "we can stand behind what it produced" is a record. Not a policy binder nobody opens. An actual, working discipline.

The RICS standard already spells out what that discipline looks like, and it's been mandatory since 9 March, so this isn't me inventing homework. Keep a written risk register for any AI used in a way that materially affects the work, and review it. Where the AI churns out volume, dip-sample the outputs at intervals and check them by hand. Tell the client, in writing, where AI touched their job. Add to that the new enterprise authorisation MCP just made stable, so you can say which agent reaches which system, and you've got the shape of it. Speed on one side, a record you'd put your name to on the other. That's what it's about.

A practical step: this week, pick one AI tool your team already uses and answer three questions on paper. Is it on our risk register, do we sample what it produces, and does the client know it's involved? If any answer is no, that's your Monday.