What Is MCP (Model Context Protocol) for AEC & BIM?
MCP — the Model Context Protocol — is the piece of plumbing that turns an AI chatbot into something that can actually operate your software. For AEC and BIM, that changes the game: instead of asking an assistant about Revit or AutoCAD, you ask it to do things in them. This is the plain-English explainer: what MCP is, why it matters for the built environment, and where to start.
What MCP is
The Model Context Protocol (MCP) is an open standard for connecting AI assistants to external applications and data. Its core idea is simple: an application exposes its capabilities as a set of tools — small, well-described actions the AI can call, each with defined inputs and outputs. The AI reads your request, decides which tools to invoke and in what order, and calls them. The application does the work and hands back a result the AI can reason over.
Because MCP is an open standard, any compliant AI client can talk to any compliant server. That is what makes it powerful: one protocol, many apps. An MCP client — Claude Desktop, Cursor, VS Code or Windsurf — can connect to a server for Revit, a server for AutoCAD, a server for your file system, and orchestrate across them in a single conversation.
Why it matters for AEC and BIM
Building-industry software is unusually rich and unusually locked-in. A Revit model carries thousands of parameterised elements; a Navisworks federation holds clash tests and viewpoints; an AutoCAD drawing has layers, blocks and precise geometry. All of it sits behind proprietary APIs that historically required Dynamo graphs, C# add-ins or AutoLISP to reach. Most designers and engineers never had time to learn those.
MCP removes that barrier. When Revit's or AutoCAD's capabilities are exposed as MCP tools, you drive them with sentences. "Find every door without a fire rating and set it to 60 minutes." "Run the MEP-vs-structure clash test and summarise the top 10 by severity." The AI translates intent into the right sequence of tool calls. The repetitive, rule-based, high-volume work that eats hours — QA passes, bulk parameter edits, takeoffs, coordination triage, documentation — is exactly what this handles well.
Read vs write — the distinction that matters
Not every MCP connector can change your model. This is the single most important thing to check:
- Read-only connectors let the AI query and reason over your model — list elements, report parameters, summarise a clash report — but not modify anything. Safe and useful for analysis. Autodesk's official Revit MCP Server is read-only today; see Revit MCP.
- Read-and-write connectors also let the AI create and edit real data — place levels, set parameters in bulk, draw entities, update clash status. This is where the biggest time savings live, and it is what turns "ask about the model" into "change the model".
How HuskyBIM uses MCP
HuskyBIM is a family of free MCP connectors that let Claude operate AEC software in plain language — and they read and write. Each connector runs on your own Windows machine and drives the software over a local connection; the AI client sends your request text and the tool results to Anthropic's models to reason over them, the same as any Claude chat. The line-up:
- Revit — 488 tools across elements, geometry, views, sheets, schedules and export (builds for 2024–2027). See AI for Revit.
- AutoCAD — 386 tools for drafting, dimensions, layers, takeoffs and the verticals. See AI for AutoCAD.
- ArchiCAD — 217 tools for elements, zones, layers, properties and views. See AI for ArchiCAD.
- Navisworks — 82 operations for ClashDetective, viewpoints and reporting. See AI clash detection.
- MS Project (244), Sigma Estimates (103) and Dalux (141) round out scheduling, estimating and the common data environment.
Where to start
Getting going takes three steps: install an MCP client (Claude Desktop, Cursor, VS Code or Windsurf), add the HuskyBIM connector for your software, and sign in with your email — it's free. Then open your model and start typing instructions. If you're weighing what's realistic before you install, read AI for BIM: What's Actually Possible Today for an honest tour of the current capabilities and limits.
Start with MCP for BIM — free
Create a free HuskyBIM account, install a connector for your software, and let Claude operate Revit, AutoCAD, ArchiCAD or Navisworks in plain language.
Frequently asked questions
What does MCP stand for?
MCP stands for Model Context Protocol. It is an open standard for connecting AI assistants to external applications and data by exposing an app's capabilities as callable tools, so the AI can act on real software instead of only chatting about it.
Why does MCP matter for AEC and BIM?
AEC software like Revit, AutoCAD and Navisworks holds rich, structured model data and powerful commands behind their own APIs. MCP gives an AI assistant a standard way to reach those capabilities, so you can query, edit, coordinate and document a model in plain language rather than learning Dynamo, LISP or a scripting API.
Does MCP let AI change my model, or only read it?
It depends on the connector. MCP itself supports both reading and writing; each connector decides which tools it exposes. Some are read-only, while HuskyBIM's connectors read and write — they can create and edit real elements, not just report on them.
How do I start using MCP with my BIM tools?
Install an MCP client such as Claude Desktop, Cursor, VS Code or Windsurf, then add a connector for your software. HuskyBIM offers free connectors for Revit, AutoCAD, ArchiCAD, Navisworks, MS Project, Sigma Estimates and Dalux; you sign in with your email and give instructions in plain language.