Skip to content
BIMpedia
Chapter 3 · Lesson 2 of 2Topic: AI in BIM

MCP and AI assistants in BIM tools

MCP lets an AI assistant call a BIM tool's actions: read elements, set parameters, create sheets. Powerful for questions and reviewed edits, risky without permissions and checks.

3 min read3 quiz questions
Skip to the quiz
  • Watch out
  • What it costs
  • Experienced readers
  • Remember
  • In BIMpedia
Adadata and automation lead
Even if you do this every day, watch for this: Edits at scale. The risk isn't a wrong answer you can check; it's a confident edit to 2,000 elements. Preview, confirm, copy first.

AI assistants became much more useful when they could use tools, not just write text. MCP (Model Context Protocol) is the open standard most of them use for it. Connected through MCP, an assistant can ask Revit for the doors on Level 3, read their properties, and, if you let it, change them.

How an AI assistant uses a BIM tool through MCP
  1. 1You ask“Which fire doors on Level 3 have no rating?”
  2. 2Assistant plansChooses the server’s tools to call
  3. 3MCP server actsCalls the software’s API: get_elements
  4. 4Results returnElements and properties, as data
  5. 5You checkSpot-check before trusting or approving changes

What it looks like

You type: "Which fire doors on Level 3 have no fire rating?"

  1. The assistant sees the MCP server's tools: get_elements, get_parameters, set_parameter, create_schedule…
  2. It calls get_elements with category = doors, level = Level 3, then get_parameters for FireRating.
  3. It answers: 14 doors, with their marks and rooms.
  4. You ask it to set them to EI 30. It shows the 14 proposed changes; you confirm; it calls set_parameter.
Basics

MCP was published as an open protocol in late 2024 and is supported by many AI assistants. MCP servers exist for desktop BIM tools (often community add-ins for Revit or Archicad), for cloud platforms (Autodesk has published samples built on APS), and for open formats like IFC. Quality and maintenance vary.

Good uses

  • Questions about model data in plain language, checked against a schedule.
  • Repetitive edits you can describe precisely and preview before applying.
  • Joining tools together: read open issues, summarise them, draft the meeting notes.
  • Prototyping an automation before writing it as a proper script.
Adadata and automation lead
Your turn. Give it about 15 min and work it out on your own before you open the model answer: that is where it sticks.
Exercise: Set the rules for an assistant 15 min

Your team wants to connect an AI assistant to Revit through a community MCP server. The server offers these tools: get_elements, get_parameters, set_parameter, delete_elements, create_sheet, export_schedule, run_python.

  1. Which tools would you allow freely, which only with preview and confirmation, and which would you disable? Why?
  2. Write three other rules for the team.

Key takeaways

  • An MCP server exposes a tool's actions; the assistant chooses which to call from your request.
  • Start read-only; allow edits only with a preview and your confirmation, on copies first.
  • Check where the assistant runs and what it sends; contracts may forbid models leaving the company.
  • For repeatable, audited jobs, turn what worked into a proper script.

Your notes

Related tool

Open an IFC file in the browser: structure, elements, properties and required-property checks.

Open IFC Inspector →

Check yourself

3 questions · 2 right to complete
  1. 1. What does an MCP server do?
  2. 2. What's the safest default for an assistant connected to a live Revit model?
  3. 3. An MCP-based routine worked well for renaming views. The team will run it every week. What now?
0 of 3 answered