Toggle Nav
 

Archi Automate 27.23 · Updated 31 August 2026

Connect Archi Automate to Autodesk Forma and ACC/BIM 360

This guide contains the Autodesk-side administrator setup and the user-side MCP connection steps. The public identifiers below are required configuration values, not passwords or client secrets.

Public integration identifiers

ValueUse
APS applicationArchi Automate
APS Client IDNzaIlycoSd2iK0cj1K3JDeX4Wzz3zy2yxIgRsquL3xi7CIHT
Forma extensionArchi Automate
Forma extension IDb101cba9-fad5-4375-8a93-c9fb06f54f2f
OAuth callbackhttp://localhost:53750/forma/callback (local loopback on the user's computer)

Archi extension admin

Owns and configures the shared Forma extension and allow-lists customer projects.

Customer Autodesk admin

Installs the prepared Forma extension or adds the ACC Custom Integration.

Normal user

Restarts the AI client, completes Autodesk consent, and selects/registers the project.

Autodesk Forma

If Archi Automate is not visible in Forma: open the target project in Forma Site Design, copy the pro_… ID from the design-mode URL, and send it to Archi support. The Archi extension administrator must allow-list that project unless the extension is enabled for all Forma users. Do not create a second APS app or replacement extension.

1. Archi prepares the extension once

  1. Create/configure the Archi Automate Forma extension from a Forma-licensed account and accept the App Store Publisher Agreement.
  2. Set Owner to the APS application Archi Automate. If the Forma administrator uses a different Autodesk account from the APS app owner, first add that account as an Editor collaborator on the APS application.
  3. Add the APS Client ID above to Service accounts.
  4. Allow the customer's pro_… project, or choose All users of Forma. An empty Only specific projects list blocks installation even for the extension creator.
  5. Complete Owner, Service accounts, and project grants before installation.

The extension does not have to be marketplace-published for an explicitly allow-listed project. Publishing controls general marketplace discovery.

2. The customer's Forma project admin installs it

  1. Open the target Forma site.
  2. Open App Store → Archi Automate → Add → Agree.
  3. If Service accounts or project grants change later, remove and reinstall the extension. Forma snapshots those grants at installation.

3. The user connects the MCP tools

  1. Install Archi Automate 27.16 or later (27.23 is current). In Hub, connect the AI client, then fully restart/reconnect it so the MCP tool list reloads.
  2. Open the project in Forma Site Design and copy the pro_… ID from the design-mode URL. Do not use the up_… overview ID.
  3. Run forma_ping.
  4. If disconnected, run forma_connect and complete Autodesk browser consent.
  5. Run forma_add_project with the pro_… ID. Archi Automate checks US and EMEA.
  6. Verify with forma_list_sessions and forma_list_documents.

OAuth success alone does not grant project access. A persistent 403 AccessDenied normally means the extension is not allowed/installed for that exact project, was installed before its grants were configured, or the wrong project ID/region is being used.

Capability note: Archi Automate can contribute integrate geometry such as footprint-and-height massing or GLB, but it does not author every Forma-native object or native floor-stack building. Forma exposes no unrestricted native delete endpoint.

Autodesk Construction Cloud and BIM 360

ACC/BIM 360 does not use the Forma extension ID. The Autodesk account administrator adds a Custom Integration using the APS application name and Client ID above.

1. The Autodesk account admin authorizes Archi Automate

  1. Open Autodesk Account Admin for the target ACC or BIM 360 account.
  2. Go to Settings → Custom Integrations → Add Custom Integration.
  3. Enter app name Archi Automate and Client ID NzaIlycoSd2iK0cj1K3JDeX4Wzz3zy2yxIgRsquL3xi7CIHT.
  4. Grant Document Management. Also grant Account Administration when project creation or membership management is required.
  5. Save and repeat for every Autodesk account/hub the users need. Accounts in different data regions must be authorized separately.

2. The user connects the MCP tools

  1. Restart/reconnect the AI client after installing or updating Archi Automate.
  2. Run acc_ping.
  3. If disconnected, run acc_connect and complete Autodesk browser consent.
  4. Run acc_list_sessions, then acc_list_projects and acc_list_documents.

If sign-in succeeds but a hub is missing, the Custom Integration is normally absent from that exact Autodesk account/region, or the signed-in user lacks membership. Adding it to one hub does not authorize another.

Related