Every name here opens a real repo. That sounds like a low bar. It is not: when I first assembled this list, a third of it did not exist.
Most AI tool lists are written by an AI that never checked whether the tools exist.
I found this out the hard way. I built this list the way everyone builds these lists: asked for research, got back twenty-one confident names with tidy one-line descriptions, and laid them out.
Then, before publishing, I checked every one against GitHub.
Seven of them were not real. Not obscure. Not renamed. Not real. bid-tabulator and subcontract-writer returned zero results across the whole of GitHub.
Here is the part worth your attention, because it will happen to you.
The fakes were not wild. Every one sat directly next to a real tool, wearing a slightly better name.
A model asked to list construction tools produces the names such tools would have. It is pattern-matching a plausible shape, and a plausible shape is exactly what slips past a reviewer who is skimming.
A wrong answer that looks wrong is harmless. A wrong answer that looks right is the whole problem.
This is the same failure mode as a fabricated case citation or an invented Australian Standard clause number. It costs you nothing when you catch it and everything when a client does.
If an AI names a tool, a standard, a clause or a source, click it before you repeat it.
The verified list comes from two places, and knowing which is which changes how you install them.
Fifteen are Claude Skills inside one open repository from DataDrivenConstruction. It holds 221 skills for construction, MIT licensed. Each one is a folder with a plain-text SKILL.md inside. You can read every line before you run it.
Six are standalone MCP servers, each its own project. An MCP server is different from a Skill: a Skill is saved instructions, an MCP server is a live connection to software. revit-mcp talks to an open Revit session. pyp6xer-mcp opens a P6 file. That is the difference between telling the assistant how to do something and giving it hands.
Read before you run. These are community projects, not vendor software. Nobody is supporting them and nobody is liable for them. Point them at a copy of your data first, not the live job.
Every link goes straight to the source: the repo for an MCP server, the exact skill folder for a Skill. All twenty-one were checked the day this was published.
For the fifteen Skills, there is no installer. A Skill is a folder. You clone the repo, copy the folder you want into your project, and call it by name.
Start with one. Pick the document you file most often, find the skill closest to it, and read its SKILL.md before you run it. Most of them will need editing to match how your practice actually works, and that editing is the point. A skill you have adapted to your templates beats a generic one every time.
Look at the list again and notice the shape of the hole in it.
Everything above works on open formats. IFC. XER. Excel. PDF. The moment a format is open, the tooling is strong: ifc-lite has 276 stars, revit-mcp has 440.
Now try to find the equivalent for the platform your project probably actually runs on. There is no official Procore MCP. The community ones sit at five, four and three stars, and the most complete of them is a personal side project that needs a 41MB spec file you have to supply yourself. Autodesk Construction Cloud is no better: the ACC servers I found have two stars, one star, and zero.
The open tooling is strong wherever the data is open, and absent wherever it is locked behind a vendor.
That is not a coincidence and it is not a gap that community developers can close. You cannot build a good open connector to a platform whose API you have to beg for. Procore has announced Agentic APIs and is signalling MCP support through its developer portal, which will change this the moment it lands. Until then, the honest answer for the biggest platform in construction is: not yet.
So the practical read is this. The work that is automatable today is the work sitting in open formats, which is more of your week than you would guess. The model file. The programme. The spec. The cost report. Start there, because that is where the tools are real.
Twenty-one is not the interesting number in this article. Seven is.
Seven fabricated tools survived research, a first draft, and a layout, and would have gone out to several thousand people if nobody had clicked the links. They only died because someone opened GitHub and searched.
That check took an afternoon. Do it on anything you are about to put your name to.
Comment "Skills" and I will point you at the one on this list closest to your week, and how to adapt it to your templates.
If a colleague is about to publish an AI-researched list, send them this first.