Skip to content

About

Help AI agents (Claude Code, Codex and other MCP clients) work with Autodesk Inventor: an MCP server that drives the running Inventor, and an agent-friendly API reference generated from the interop DLLs. Inventor 2024 to 2027.

Topics

Resources

Stars

0 stars

Watchers

0 watching

Forks

Repository files navigation

InventorBridge logo

InventorBridge

Help AI agents work with Autodesk Inventor.

MIT license

InventorBridge logo above an excerpt of the generated reference: the ExtrudeFeatures interface in pseudo-C#

A bridge between AI agents (Claude Code, Codex and other MCP clients) and Autodesk Inventor: API documentation designed for agents and an MCP server that lets an agent drive the Inventor you have open.

Independent project, not affiliated with Autodesk. Autodesk and Inventor are registered trademarks of Autodesk, Inc.

What exists today

  • API reference for Inventor 2024 to 2027, generated from the interop DLLs:
    • one page per object and per enum, with the interface in pseudo-C#;
    • COM inheritance ("ExtrudeFeature inherits from PartFeature"), which the interop does not show;
    • an example path from Application to each object;
    • what returns each object and where each enum is used;
    • a // since 20xx mark on members that do not exist in every version;
    • members.tsv, one member per line, for grep.
  • The reference generator (src/InventorBridge.ReferenceGenerator).
  • MCP server (src/InventorBridge.Mcp, first version): connects Claude Code, Codex or any MCP client to the Inventor running on your computer. The agent writes C# against the Inventor API, the server runs it inside Inventor, and you watch the result in your own Inventor window. The agent looks up the API with api_lookup instead of guessing names, and reads short guides served by the server.

The full plan is in ARCHITECTURE.md.

Using it with Claude Code

Requirements: Windows, Autodesk Inventor 2024 or later, and the .NET 8 SDK.

  1. Clone the repository and build the server. It references Autodesk.Inventor.Interop.dll from the Inventor 2024 installation (or from lib/inventor/2024/, see below):

    dotnet build src/InventorBridge.Mcp -c Release
  2. Register it in Claude Code for every folder (adjust the path to where you cloned it):

    claude mcp add inventor --scope user -- C:\path\to\InventorBridge\src\InventorBridge.Mcp\bin\Release\net8.0-windows\InventorBridge.Mcp.exe
  3. Optionally, install the skill that tells the agent how to work with these tools, by copying skills/inventor-api to %USERPROFILE%\.claude\skills\inventor-api. With Codex or another agent, put the text of skills/inventor-api/SKILL.md in your project's AGENTS.md. The server also sends short instructions of its own and serves the guides through the guide tool.

  4. Open Inventor, open Claude Code and ask, for example: "create a new assembly with two tubes and a 90° bend, and connect the three".

Tool What it does
inventor_status Connects to the Inventor you have open: version, active project and workspace folder, default templates, open documents, and other Inventor processes running (such as one left over from a crash)
inventor_start Starts Inventor (visible) when it is not running, and waits until it is ready
run_csharp Compiles and runs a C# script against the Inventor API. It runs as one undo step on the active document and is rolled back on an error (undoable: false skips the undo step for scripts that only read), with Inventor's own dialogs silenced; if an add-in's dialog holds the script, the call returns with its title. Compilation errors come back with line and column. The result lists what changed (documents, features, occurrences, constraints), and an optional expect checks volume, size, bodies, occurrences or free degrees of freedom
script_result Waits for a script that was still running after 60 s and returns its result
inspect Structured summary of the active document: iProperties and file state of any document; features, parameters, mass, material and sheet metal flat pattern of a part; occurrences, constraints and free degrees of freedom of an assembly; sheets, views, parts lists and dimensions of a drawing. Says which lists were cut
bom Bill of materials of the active assembly with quantities rolled up through the levels, plus the totals per part number; read from the Model Data view, so the document is not changed
export Writes an open document to STEP, IGES, STL or SAT, a sheet metal flat pattern to DXF, or a drawing to PDF, DWG or DXF, without changing the document; never replaces a file unless told to
check Finds what is broken in a document and everything it references: missing files, features and constraints with errors, documents that need an update, broken flat patterns, detached dimensions and balloons
undo_last Undoes the last script like Ctrl+Z, only when the last step in Inventor's undo list is a script's
ilogic_list, ilogic_set, ilogic_run, ilogic_script List a document's iLogic rules, write one without running it, run a rule or an external rule file, and run iLogic code given as text with values returned; all in a transaction, so undo_last undoes them; iLogic's error dialogs are closed and their errors returned, with line numbers as in the code
vault_info Autodesk Vault state of files (version, revision, lifecycle state, category, who has them checked out, whether the local copy matches the vault), read through the vault connection the user's Inventor already has; reads only
vault_search Find files and folders in Autodesk Vault by exact name or pattern (*, ?), optionally under one vault folder: vault path, working-folder path, version, state and check-out of each file found, the folders found, and the names not found; reads only
vault_change Check out, check in (adding new files with their dependencies), undo a check-out, get the latest version, or change the lifecycle state, through the same connection and with the user's rights; reopens the files it rewrote and refreshes Inventor's Vault browser
log_note Writes the agent's note (the user's feedback, a missing tool, a guide that did not fit) to the session log, when the server logs (INVENTORBRIDGE_LOG)
topology Faces and edges of a part or of one occurrence (also inside subassemblies, by path), with positions, cylinder axes and circle centers in mm, so a script can pick them; split cylinders are merged with their ends, and bends (tori) are listed with theirs
screenshot An image of the Inventor view, so the agent sees what you see; work planes and sketches are hidden for the capture, and on a drawing it can zoom to a view, the parts list, the title block or a region
api_lookup Looks up the API reference: an object's or enum's page, some members of a type, or a search by name. It hides members that the running Inventor version does not have, and works without Inventor
guide Short guides: the workflow, parts, assemblies and constraints, API pitfalls

Inventor must stay open while the agent works: the server talks to it through COM, out of process, so nothing is installed inside Inventor.

Company guides

The general guides cannot know a company's own rules: how files and part numbers are named, which iProperties are required, the templates, the vault's rules, the codes the ERP uses. Keep them as Markdown guides in a folder of your own, in your own (private) repository, and point the server at it when you register it:

claude mcp add inventor --scope user -e INVENTORBRIDGE_GUIDES=C:\path\to\company\guides -- C:\path\to\InventorBridge\src\InventorBridge.Mcp\bin\Release\net8.0-windows\InventorBridge.Mcp.exe
  • Several folders are separated with ;. A README.md in a folder is for people and is not served.
  • Each guide starts with # Title and a > one-line summary line, like the general ones.
  • The guide tool lists them apart from the general guides, and the server tells the agent to read them before creating, naming, saving or exporting files, and that they win where they differ.
  • Larger material, such as product standards converted to Markdown, can go in subfolders: it is not listed, and a guide points to each file by its path, which the agent reads with guide("standards/Conveyor") (for standards\Conveyor.md). Files outside the guide folders cannot be read this way.
  • A company guide cannot take the name of a general one; the list says so if one tries. Edits show up without restarting the server; new guides are named in the server's instructions at the next start.
  • This repository's tests do not compile the C# in company guides: run those examples on Inventor.

Logging a pilot

To learn from a trial with real users, set INVENTORBRIDGE_LOG to a folder where the server is registered. The server then writes, in a file per day (2026-11-17-server.jsonl), one JSON line per tool call (the arguments, such as the scripts sent, the result, errors and the time it took) and per note the agent writes with log_note: the user's feedback on a task, a tool or guide it missed, a guide rule that did not fit, a fix the user made by hand. The server's instructions then ask the agent to write those notes. Without the variable nothing is written and log_note records nothing.

The log stays on the user's computer, in the folder you chose, and holds what was sent to Inventor: tell the people in the trial. With Claude Code, register the server in a project's .mcp.json with the variable, so only the chats opened in that folder are logged; the folder's CLAUDE.md and hooks can add the user's requests and ask for feedback after each task.

Generating the reference

The Autodesk interop DLLs are not in the repository. Put one per version at lib/inventor/<year>/Autodesk.Inventor.Interop.dll:

Version Where to get it
2024 and earlier The Inventor installation: C:\Program Files\Autodesk\Inventor <year>\Bin\Public Assemblies\
2025 and later The interop downloads page on Autodesk support ("Inventor Interop binary files")

Then, from the repository root (requires the .NET 8 SDK):

dotnet run --project src/InventorBridge.ReferenceGenerator

The generator does not run Inventor and does not need it installed: it only reads the DLLs' metadata. Building InventorBridge.Mcp copies the generated pages next to the server, for api_lookup.

Tests

dotnet test

The tests do not need Inventor. They cover the API lookup, the guides (every C# example must compile as a run_csharp script), script compilation, and the server itself: they start it over stdio and check that every tool declares all four MCP hints. Like the build, they need Autodesk.Inventor.Interop.dll, from the Inventor 2024 installation or lib/inventor/2024/.

Layout

src/InventorBridge.Mcp/
  Connection/  COM connection: STA thread, retry of busy calls, attaching to or starting Inventor
  Scripting/   compiling and running run_csharp scripts (Roslyn), transactions
  Reading/     inventor_status, inspect and screenshot
  Reference/   api_lookup and guide: serving the reference and the guides
  Tools/       the MCP tools
src/InventorBridge.ReferenceGenerator/
  Reading/     reading the DLLs and inheritance.txt
  Model/       per-version model and combined model
  Analysis/    version merging, inheritance, reverse indexes, access paths
  Output/      Markdown pages, index, members.tsv and JSON
  inheritance.txt   derived/base pairs extracted from the object model poster legend
docs/reference/     generated output (do not edit by hand)
docs/guides/        hand-written guides served by the guide tool
skills/inventor-api/  skill telling an agent how to work with the tools
AGENTS.md           instructions for agents changing this repository
tests/InventorBridge.Mcp.Tests/   tests that run without Inventor
InventorInterop.props             where the build finds Autodesk.Inventor.Interop.dll
assets/             logo and social preview (SVG sources and PNG)
docs/cover.svg      README and portfolio image (rendered to docs/cover.png)

License

MIT. The license covers the code and documentation in this repository, not the DLLs or any other Autodesk material, which remain under Autodesk's own terms.

About

Help AI agents (Claude Code, Codex and other MCP clients) work with Autodesk Inventor: an MCP server that drives the running Inventor, and an agent-friendly API reference generated from the interop DLLs. Inventor 2024 to 2027.

Topics

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Contributors

Languages