MCP Connector for 3ds Max

What it does

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

How edits are controlled

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

The free tier cannot modify scene data. Its tools query and report on the scene, change the selection or the viewport, and capture a viewport image to a path named in the call.

Tools that modify the scene run inside named 3ds Max undo contexts, so each tool call appears in the undo history and can be reversed with Undo. If a tool fails, its undo context is cancelled and its changes are discarded. Scene-wide settings such as units and render settings, and file operations such as renders and exports, sit outside the undo history.

The Pro tool that runs MAXScript supplied by the AI is not sandboxed. It can do anything a script run by the user could, and it is the only tool with that reach.

The connector never saves or overwrites the user's scene file on its own. Writing to the scene file happens only through the tool whose purpose is to save. Before the first scene-changing Pro tool of a session, the connector saves a snapshot of the scene into its own folder under the user's local application data, so the session start point can be restored. The user's file and its path are not touched by that snapshot.

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 3ds Max on the workstation. The component that talks to your AI client 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 is scoped to the account 3ds Max is running under, and no other account on the machine can open it. A pipe that cannot be scoped that way is never created.
• No log file by default. Diagnostics are off unless a user enables them for troubleshooting. When enabled, the log records lifecycle and licence events, 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 .NET components are widely used libraries from the official NuGet ecosystem. Every component declares a licence, and all are MIT.

The component that talks to your AI client is a self-contained executable built on a pinned Node.js runtime. Its own dependency set is MIT, ISC or BSD licensed. There are no copyleft licences in the shipped product.

A CycloneDX Software Bill of Materials is produced for each supported 3ds Max version, because the dependency set differs between them, and a further one for the bridge executable. At version 1.2.3 no shipped component on either side 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.