An Autodesk Vault MCP server that reads Vault PLM files, items and change orders under the asking user's permissions

What we build

A first Autodesk Vault tool list, written as the manifest your IT team signs

Built on what Autodesk documents: folders and folder contents, files and file versions, items, item versions and bill of materials, change orders, lifecycle states, search results. Backends named below are documented resources; "confirmed in blueprint" means the vendor documentation sits behind a login and the resource is checked against your release first.

# autodesk-vault-mcp-server: tool manifest, draft for blueprint week 1
# Every tool runs as the person asking. Nothing is written without a person confirming.
tools:
  get_server_info:    # -> product name and product version of this Vault server
    backend: GET /server-info
    mode: read
  list_folder:        # vault id, folder id -> files and subfolders
    backend: GET /vaults/{vaultId}/folders/{id}/contents
    mode: read
  get_file_version:   # vault id, file version id -> that file version
    backend: GET /vaults/{vaultId}/file-versions/{id}
    mode: read
  get_item_bom:       # vault id, item version id -> child items
    backend: GET /vaults/{vaultId}/item-versions/{id}/bill-of-materials
    mode: read
  list_change_orders: # vault id -> change orders
    backend: GET /vaults/{vaultId}/change-orders
    mode: read
audit: every call logged with user, tool, arguments and the Autodesk Vault response

The manifest is the contract. A question that needs an operation not on it gets a new line and a review, not a wider permission.

Checked 15 October 2026

Autodesk Vault at a glance: interfaces, access and what exists for AI

Autodesk (US). Engineering teams that keep released CAD files, items and change orders in an on-premises Autodesk Vault. Autodesk describes Vault as PDM that integrates with Autodesk design tools and other CAD systems.

Why Autodesk Vault is hard for agents

Where a Autodesk Vault connection needs engineering, not configuration

Autodesk Vault holds the records. An assistant without a governed way in answers from whatever someone pasted into the chat. The connector is the governed way in: named operations, the person's own permissions, every call logged.

Start with the Readiness Blueprint.

Two weeks, €4,900 fixed price. Week one agrees the tool list with your Autodesk Vault owners and checks every backend against your release and licence. Week two tests whether a person's own Autodesk Vault permissions reach through the connector. You keep the manifest and a costed build plan, whoever builds it. All prices are net and exclude VAT.

What we need from you: a named Autodesk Vault administrator, a test or sandbox system we may call, and one business owner who can say which questions the assistant should answer first. The first production connector is usually a use-case pilot from €15,000; it runs in your environment, and the code is yours.

Sources: Vault Data API overview · Autodesk: what Vault is · Vault Data API samples (Autodesk) · Vault Data API OpenAPI 2.0.17 · Autodesk public MCPs (15 April 2026) · Autodesk Vault 2027 and Assistant (26 March 2026) · MuhammadTaimur/Vault-MCP. Read 15 October 2026. Vendor documentation changes; verify against the current release.

Related

• Connectors for 100 source systems — the dated catalogue this page belongs to
• Aras Innovator connector — PLM / CAD, Aras Corporation
• CONTACT Elements connector — PLM / CAD, CONTACT Software GmbH
• EPLAN connector — PLM / CAD, EPLAN GmbH & Co. KG, part of the Friedhelm Loh Group
• Claude MCP server development — how we build an MCP server for any internal system