What is MCP and why it changes how we talk to CAD software

Asking Inventor for an assembly in plain language is no longer science fiction. And the key piece has a name: MCP.

The USB port of AI

MCP (Model Context Protocol) is an open standard that defines how a language model connects to applications and data. The analogy I use with clients: it is the USB port between the LLM and your software. A standard connector, instead of a hand-soldered cable for every device.

Before, every integration was a custom build: one bridge for Vault, another for Inventor, another for the ERP. Each with its own format, its own maintenance and its own way of breaking. Fragile and expensive.

With MCP, the model discovers which tools exist, which parameters they accept and what they return. Intelligence stays on one side; operations stay on the other. And the same pattern works for any application with an API.

How I use it in real products

VaultPilot, built together with Avant Leap: 28 tools in 9 categories to operate Autodesk Vault by conversation. Search, lifecycles, properties, bulk operations, BOMs, ECOs, jobs, ERP and reports, all behind a typed catalog the model cannot invent around.

AI Design Assistant: parametric parts and assemblies in Autodesk Inventor from natural language, with a 3-layer architecture: Inventor API + MCP + LLM.

The detail that matters

The LLM never touches your CAD directly. It asks. The tool layer validates and executes. If the model asks for something that does not exist, the call dies at the contract, not in your file.

That is why MCP is not just an integration convenience: it is a security boundary. It defines exactly what AI can and cannot do to your software. The next years of "AI in CAD" will be built on this piece, and whoever understands the pattern today will evaluate everything they are sold tomorrow much better.