# A Modular Reference Architecture for MCP-Servers Enabling Agentic BIM Interaction

arXiv: https://arxiv.org/abs/2601.00809 · HTML: https://mlsanity.com/paper/2601.00809/

## Key facts

- Cited by 1 papers in the map (data through 14 Oct 2026).
- Placed in Tool learning and function calling, one of 16 directions in LLM agents and tool use.
- Builds on 3 of its 15 references that are in the map.
- First posted on arXiv 21 Dec 2025.

## Placed in

- LLM agents and tool use / [Tool learning and function calling](https://mlsanity.com/agents/tool-learning-and-function-calling/)

## Builds on (most cited first, 3 of 3)

- [Text2BIM: Generating Building Models Using a Large Language Model-based Multi-Agent Framework](https://mlsanity.com/paper/2408.08054/) (2024)
- [Towards a copilot in BIM authoring tool using a large language model-based agent for intelligent human-machine interaction](https://mlsanity.com/paper/2406.16903/) (2024)
- [Text-to-Layout: A Generative Workflow for Drafting Architectural Floor Plans Using LLMs](https://mlsanity.com/paper/2509.00543/) (2025)

## Built on by (most cited first, 1 of 1)

- [A Building as a Repository: KIR, a Typed Intermediate Representation for Agent-Authored Building Information Models](https://mlsanity.com/paper/2609.14578/) (2026)

## Abstract (arXiv)

Agentic workflows driven by large language models (LLMs) are increasingly applied to Building Information Modelling (BIM), enabling natural-language retrieval, modification and generation of IFC models. Recent work has begun adopting the emerging Model Context Protocol (MCP) as a uniform tool-calling interface for LLMs, simplifying the agent side of BIM interaction. While MCP standardises how LLMs invoke tools, current BIM-side implementations are still authoring tool-specific and ad hoc, limiting reuse, evaluation, and workflow portability across environments. This paper addresses this gap by introducing a modular reference architecture for MCP servers that enables API-agnostic, isolated and reproducible agentic BIM interactions. From a systematic analysis of recurring capabilities in recent literature, we derive a core set of requirements. These inform a microservice architecture centred on an explicit adapter contract that decouples the MCP interface from specific BIM-APIs. A prototype implementation using IfcOpenShell demonstrates feasibility across common modification and generation tasks. Evaluation across representative scenarios shows that the architecture enables reliable workflows, reduces coupling, and provides a reusable foundation for systematic research.