MCP Connector for Revit

What it does

A Revit add-in that lets your existing AI assistant read and edit the model that is open on the user's machine. You bring your own AI subscription. Supported on Revit 2022 to 2027.

How edits are controlled

The AI does not have unattended access to the model. Every tool call is initiated from the AI client by the user, in a session the user is watching.

The free tier cannot create, change or delete model elements or their parameters. Its tools query and report on the model, change the selection and the active view, and can hide or isolate elements in a view.

Pro tools that modify the model run inside standard Revit transactions. Every change appears in the Revit undo history and can be reversed with Undo, and a failed operation rolls back rather than leaving a partial change. A small number of batch tools commit one transaction per item so that one failed item does not discard the others, and report which items succeeded.

Where Revit would show a warning dialog, the connector accepts the warning or applies Revit's own default resolution so the tool can complete unattended. Errors Revit cannot resolve roll the transaction back.

The connector never saves, synchronises or relinquishes on its own. Those actions happen only through the tools whose purpose is to save, synchronise, relinquish, close or enable worksharing, and there is no autosave or timed synchronisation. Worksharing permissions and element ownership apply to AI-driven changes exactly as they do to manual ones: the connector never takes over another user's elements, and an element it cannot edit is skipped and reported.

Where model data goes

To whichever AI provider you already use, under your existing contract with that provider. AUTOM8LABS never receives your model data, never stores it, and is not a processor of it.

The add-in runs inside Revit on the workstation. The component that talks to your AI client has no third-party dependencies and makes no outbound network connections of its own.

What AUTOM8LABS receives

The machine identifier is a SHA-256 hash of hardware values. The underlying hardware identifiers never leave the machine.

What is stored

On the workstation

• No listening port. The add-in communicates with your AI client over a Windows named pipe, not a network socket.
• Access restricted to the same Windows user. The pipe carries a single access control entry, for the account Revit is running under. If that account cannot be resolved, no pipe is created.
• No log file by default. Diagnostics are off unless a user enables them for troubleshooting. When enabled, the log records tool requests, which can include model file paths and element identifiers, and it never leaves the machine.
• Stored credentials are encrypted. The licence and entitlement caches are protected with Windows DPAPI.
• No elevated privileges are required at runtime.

Supply chain

All third-party components are widely used libraries from the official NuGet ecosystem. Every component declares a licence. All are MIT except one, which is Apache-2.0. There are no copyleft licences in the shipped product.

A CycloneDX Software Bill of Materials is produced for each supported Revit version, because the dependency set differs between them. At version 3.6.3 no shipped component carries a known vulnerability, and the build fails if that stops being true.

SBOMs are available on request from security@autom8labs.io.

Assurance

Every binary and installer is code-signed as AUTOM8LABS LTD through Azure Trusted Signing.

See the Trust Center for the full assurance position and the sub-processor list.