Your Cart
Loading

đź”’ AI-Driven BIM Compliance Checking with Claude & Autodesk APS

In this step-by-step article, we show how Claude can be connected to Autodesk’s AEC Data Model API to perform automated BIM compliance checks.


Instead of manually comparing specifications with model data, Claude can read a PDF requirement, query the live BIM model, identify missing elements, and visually highlight the issue inside a 3D viewer.


A link to the repository is provided at the end of the article so you can explore and test the workflow yourself.


Watch a short demo from Anthony Sertorio:



The Technical Stack

  • Claude Desktop: The interface where reasoning, analysis, and interaction take place.
  • MCP (Model Context Protocol): An open standard that allows Claude to interact with external tools, APIs, and databases.
  • AEC Data Model API: Autodesk’s GraphQL-based API for querying building data without downloading or parsing full Revit models.
  • APS (Autodesk Platform Services) Viewer: Autodesk’s web-based 3D viewer used to visualize model data and highlight discrepancies.


Step 1: Configure the Autodesk Developer Environment

Before Claude can interact with a BIM model, the Autodesk environment must be configured.


  1. Create an APS Application: Create a new application through the Autodesk Developer Portal.
  2. Generate API Credentials: Store the generated Client ID and Client Secret securely.
  3. Enable the AEC Data Model: Ensure the Autodesk Construction Cloud (ACC) or Autodesk Forma hub has access to the AEC Data Model API.


Step 2: Install and Configure the MCP Server

Claude does not natively communicate with Autodesk APIs. An MCP Server acts as the bridge between the AI model and the BIM environment.


Clone the MCP Connector

Download a compatible connector such as the APS AEC Data Model MCP Server.


Build the Server

Compile the project using the required runtime, typically .NET or Python.


Configure Claude Desktop

Update the claude_desktop_config.json file with the server configuration and API credentials:


"mcpServers": {

"autodesk-aec": {

"command": "dotnet",

"args": ["path/to/your/server/bin/ApsMcpServer.dll"],

"env": {

"APS_CLIENT_ID": "YOUR_ID",

"APS_CLIENT_SECRET": "YOUR_SECRET"

}

}

}


Once configured, Claude gains access to Autodesk-related “Skills” through the MCP connection.


(...)


Join Pro Access to view the full article →