HuskyBIM for Dalux
HuskyBIM for Dalux connects Claude Desktop to Dalux — the construction-management and field-BIM platform (Dalux Build + Dalux Field/FM). With 141 tools you can browse projects, dashboards, tasks, QC issues, files, handover, locations and daily logs, and upload AEC files of any format into Box — all in plain language, without manual navigation.
How it works — two layers
HuskyBIM for Dalux works in two complementary ways. Some tools drive the running Dalux Desktop app directly; others use Dalux's official REST API once you provide your company's API key.
With the Dalux Desktop app open and logged in, Claude can browse your projects, dashboards, tasks, QC issues, files, handover, locations and daily logs. It can also upload files of any AEC format — Revit .rvt, IFC, BCF, PDF, DWG, point clouds — into Box, with verified read-back, and create Box comments and issues.
Provide your company's Dalux API-identity key and a built-in REST API layer unlocks full create and update across Dalux Build and Dalux FM — projects, tasks, tickets, work orders, assets, buildings, files and forms. Set the key via the DALUX_API_KEY environment variable or a ~/.huskybim-dalux-key file.
Requirements
• Claude Desktop — download at claude.ai/download
• Node.js — standard runtime, bundled with the extension flow
• A Dalux account — for Dalux Build and/or Dalux Field/FM
• Dalux Desktop — open and logged in, for the live layer
• Optional: a Dalux API key — to enable the official REST create/update layer
• Free HuskyBIM account — sign up
Installation
Download the extension
Sign in to your account page and download HuskyBIM_for_Dalux_v0.4.2.mcpb from the Downloads section.
Install in Claude Desktop
Open Claude Desktop. Go to Settings → Extensions and click Install extension. Select the downloaded .mcpb file, or drag and drop it onto the Extensions panel. It appears as an extension.
Enter your extension token
In the HuskyBIM Dalux extension settings, enter your extension token. Find your token at huskybim.com/account under Extension Token. Optionally add your DALUX_API_KEY here to enable the REST create/update layer.
Start (or restart) Dalux Desktop
Open the Dalux Desktop app and log in. The extension automatically enables Dalux Desktop's local connection interface the first time it runs (a one-time, per-user Windows setting — no admin rights needed). If Dalux Desktop was already running when you installed the extension, close it completely — including the tray icon — and start it again: the setting is picked up when Dalux starts. Then return to Claude Desktop and the HuskyBIM for Dalux tools are ready.
What you can do
HuskyBIM for Dalux provides 141 tools across a full read surface driven from the running Dalux Desktop app, verified multi-format file upload into Box, and — with an API key — an official REST create/update layer for Dalux Build and FM.
Example workflows
Show me the active Dalux project — its dashboard, open tasks and any QC issues that need attention.Upload the IFC file at C:\Models\Building-A.ifc to the Box files area of the current Dalux project and confirm it landed.Using the Dalux REST API, create an FM work order for asset AHU-03 titled "Replace filter" and assign it to the maintenance team.Troubleshooting
Ensure the Dalux Desktop app is open and logged in before making calls. The live layer drives the running app through a local connection interface that the extension enables automatically the first time it runs — but Dalux only picks the setting up at startup, so after installing the extension, close Dalux Desktop completely (including the tray icon) and start it again. If a tool call still fails, ask Claude to run debug_connection — since v0.4.2 the error messages state exactly what to do.
To verify the connection interface yourself: with Dalux Desktop running, open http://localhost:9222/json in a browser — you should see a JSON list mentioning field.dalux.com. This interface is scoped to the Dalux app only and listens on localhost only; nothing is exposed to the network. On company-managed PCs the automatic setup can be blocked entirely — see the next section.
On centrally managed Windows devices (Intune or similar), the automatic setup may fail with "Access is denied" — the device policy prevents the extension from writing the setting for the current user. Claude will tell you when this happens and show the fix. A local administrator (or your IT department) applies the setting machine-wide instead: open Command Prompt as administrator and run
reg add "HKLM\Software\Policies\Microsoft\Edge\WebView2\AdditionalBrowserArguments" /v "Dalux.exe" /t REG_SZ /d "--remote-debugging-port=9222" /fThen close Dalux Desktop completely (including the tray icon) and start it again. The setting only affects the Dalux app and only opens a localhost interface.
Note for IT: if your organization syncs Windows policies centrally, a later policy refresh can remove manually applied settings — if the live tools stop working again after some days, add the setting to your device baseline instead. In Intune, deploy the same command as a Platform script or Proactive remediation running in SYSTEM context, or set the equivalent policy value (AdditionalBrowserArguments, value name Dalux.exe) under Microsoft Edge WebView2 in your configuration profile.
The full create and update operations require the official Dalux REST API. Add your Dalux API-identity key via the DALUX_API_KEY environment variable or a ~/.huskybim-dalux-key file, then restart Claude Desktop.
Check that your extension token is correctly entered in Claude Desktop → Settings → Extensions → HuskyBIM Dalux. Tokens are case-sensitive and must not contain spaces. Find your token at huskybim.com/account.
If the extension does not appear after installation, ensure you are using Claude Desktop (not the web app). Go to Settings → Extensions and verify the extension is enabled. Re-install the .mcpb file if needed.