
Autodesk Inventor
io.github.cenituPublished by GitHub account cenituv1.0.1Updated Nov 1, 2026
Parametric 3D modeling in Autodesk Inventor: sketches, features, sheet metal, assemblies
The publisher's own server: Autodesk Product Help MCP
Overview
Drives Autodesk Inventor on Windows through its COM API, letting an assistant build parametric parts, sheet metal, assemblies and drawings in natural language.
- What you can do
- Sketch and model parts: sketches, extrude/revolve, holes, fillets, chamfers, patterns, parameters
- Build sheet metal: flanges, corner rounds, flat patterns, DXF/DWG export
- Assemble: place and constrain components, import STEP parts, check interference and measure
- Inspect and verify: capture model views as images, find faces and edges, report volume deltas
- Produce outputs: PDF drawings, BOM CSV, part properties
- Run arbitrary Python against the live Inventor connection as an escape hatch
- When to use it
- Useful when you want an assistant to create or modify real Inventor models, sheet-metal parts and assemblies on a Windows workstation, including standard-part recipes and shop-floor outputs like flat patterns and BOMs.
- Requirements
- Windows with Autodesk Inventor installed (developed on 2026, verified on 2027); Python 3.12+ with the mcp and pywin32 packages; a local MCP client such as Claude Code or Claude Desktop; Inventor must be running or startable by the server.
Installation
In SourceWeft
- Open Autodesk Inventor in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
inventor-mcp-server
[PyPI] [CI] [License: MIT] [Contributions welcome]
Maintained continuation of NeonGlay/inventor-mcp. The original repository has had no activity since its initial release (June 2026), and fresh installs there fail on MCP SDK 2.x. This repo carries the full original history plus the fixes and features that were submitted upstream as PRs and never reviewed. If the original author returns, everything here is available to be merged back. See CHANGELOG.md.
MCP server for parametric 3D modeling in Autodesk Inventor — drive Inventor with Claude (or any MCP client) in natural language.
Build real parametric parts — flanges, shafts, nuts, brackets, sheet-metal enclosures — by talking to an AI assistant. The server wraps Inventor's COM API with high-level, millimeter-based tools and ships with battle-tested knowledge of Inventor 2026 API quirks that aren't documented anywhere else.
Features
- 57 MCP tools: sketching, extrude/revolve, native hole features (drilled / tapped / counterbore), fillets, chamfers, circular patterns, sheet metal (named rules / Face / auto-mitered Flanges / Cut at world coordinates / Corner Round, with Flat Pattern support), parameters
- Assemblies with vendor parts:
import_step(keeps the files in your project folder), placement with full orientation,check_interference/measure_distance, andsweep_rotationto check a door or lock moves freely through its whole range - Assemblies (IAM): place components, ground them, constrain by origin geometry (mate / flush / angle) or drop a bolt into a hole with a single Insert constraint
execute_pythonpower tool — run arbitrary Python against the live COM connection with a persistent namespace (escape hatch for anything not covered by dedicated tools)- Auto-reporting — every feature operation returns a volume/topology delta (
Hole1 | V 23497 (-503 mm³) | F7 E14), so the AI can self-verify each step - One tool per job — 57 tools with verb_noun names:
find_faces/find_edgeswork in a part and at any depth of an assembly,constraintakes origin geometry, faces and edges, andmanage_*tools group what you do to documents, occurrences, features, parameters, constraints, materials and sheet metal rules - Protects your files —
save_documentsaves only the active document unless asked, never a library or Content Center file; add your own paths withINVENTOR_MCP_PROTECTEDor~/.inventor-mcp/protected.txt. Deleting a component says what depends on it first, and reports what moved - Never hangs on a dialog — calls run with
SilentOperationon a dedicated Inventor thread. A call stuck behind a modal dialog, or a long job, returns within 50 s with the dialog's title and text (read from the window list, no COM call);manage_call(wait_seconds=30)follows it — with the prints andprogress()line so far — and returns the result the moment it finishes;manage_call(action="cancel")stops it - Shop-floor outputs —
export_flat_patterngives the flat size and writes the DXF/DWG for the laser (contour, holes and bend lines on their own layers);create_drawingmakes a PDF drawing (base + projected + iso views, overall dimensions, or the flat pattern dimensioned);export_bomlists the assembly's parts with quantity, part number, description, material and mass (CSV for Excel / ERP);edit_propertiesreads and sets part number, description, stock number, material and custom properties - Real arcs in sketches —
draw_closed_profiletakes rounded corners ([x, y, r]) and arcs through a point, plusdraw_rectangle(corner_radius),draw_slot,draw_arcandproject_edges(exact edges of a body, for remodelling). Arcs go through three points, so a sketch with flipped axes can't mirror them;inspect_modelwarns when a curve was drawn as many short lines.draw_patterndraws grids and circles of holes / slots,offset_profileoffsets loops, andcheck_sketch(also built into extrude's error) points at the gap that keeps a profile open - Sees its own work —
capture_viewreturns pictures of the model (iso / front / top / … , several in one call, zoom to components, isolate them) as images the agent can look at, with sketches hidden and the user's camera put back. A flange on the wrong side or a part floating off the frame shows at a glance - Steel frames —
add_frame_memberslays Content Center profiles along skeleton lines (start → end, roll, centered or at the profile origin, shortened or extended at either end) and returns a saw cut list — what Frame Generator does, which has no API. A 13-member frame takes ~35 s - Surfaces to solids —
convert_surfaces_to_solidknits an imported surface model, patches the holes in the shell and closes it into a solid (or turns a closed shell into one directly), with the volume and any edges it couldn't close - Materials in bulk —
manage_materialsgives every matching part of an assembly a material (Content Center parts left alone), reports material and mass per part and flags Generic parts, surface-only vendor models and parts with no mass;edit_properties(mass_kg)overrides a mass - Nested assemblies —
find_facesfinds faces of components inside sub-assemblies (type, normal, position, diameter) in top coordinates;constrainconstrains them, corrects a wrong offset sign from where the face must land, and reports any other component the constraint dragged along - Content Center and big assemblies —
use_content_centerbrowses categories → families → sizes and makes members, custom length included (a 1500 mm DIN 1026-1 U 100 in one call);place_componentsplaces dozens of components with position, orientation, name and grounding in one call - Agent-friendly Python —
execute_pythonerrors show the traceback from the agent's own lines (also in helpers defined in earlier calls), stderr is captured, andundo_on_error=Truerolls back everything the call did.load_library(or~/.inventor-mcp/startup.py) keeps helper code loaded across namespace resets. COM errors come with their name and a hint (E_INVALIDARG, RPC_E_DISCONNECTED …) instead of a localized "Exception occurred".save_documentchecks the path first instead of failing with E_INVALIDARG and never rewrites library or Content Center files;manage_documentsclears the Part12s left by failed attempts - Several Inventors at once, across restarts — e.g. two agents on two projects (Claude Desktop runs one server for all its chats).
connect(project="…ipj")reuses the Inventor that has the project, or the running one if it is free, or starts a separate one; every tool takesinstance=to pick one, and each has its own call thread andexecute_pythonnamespace, so one agent's long call doesn't hold up the other.list_instancesshows them. An Inventor opened by hand can't be targeted — Windows always hands out the first one — so let the server start the second. A keeper process holds the Inventors the server started, so after a restart of the clientconnect(project=…)gets them back - Transactions — wrap multi-step builds, roll back everything with one call
- Hot reload — edit the API wrapper and reload without restarting the MCP client
- Topology helpers — find edges/faces by coordinates instead of guessing indices
- Parametric discipline — projected origin points, symmetry constraints, dimensioned sketches that survive parameter changes
Requirements
- Windows with Autodesk Inventor (developed on Inventor 2026, also verified on Inventor 2027; older versions may need enum adjustments — see docs/inventor-api-notes.md)
- Python 3.12+
pip install "mcp[cli]" pywin32— MCP Python SDK 1.x and 2.x are both supported (2.x renamedFastMCPtoMCPServer; the server detects which is installed)- An MCP client — used daily with Claude Code and Claude Desktop (several agents at once, see below)
Installation
-
Clone this repository:
-
Install dependencies:
-
Register the server with your MCP client. For Claude Code, add to
.mcp.jsonin your project root (see.mcp.json.example). Use the absolute path toinventor_mcp_server/server.py:Don't use
"cwd"with-m inventor_mcp_server. Claude Code ignorescwdand starts the server from your project root, where the package can't be found — the process exits immediately and the client only reportsConnection closed. Pointing at the script by absolute path works from any directory.Configs written for 0.2.x that point at
src/server.pystill work — that file now forwards to theinventor_mcp_serverpackage — but please update them; the shim will be removed in a later release.Alternatively, install it from PyPI — no clone needed, and the config gets a plain command:
(If your MCP client can't find the command, use the full path printed by
where inventor-mcp-server.) -
Restart the MCP client (MCP servers load at session start), start Inventor, then ask your AI assistant to build something.
Avoid
win32com.client.gencache.EnsureDispatchandCastToin your own scripts against the same Python install — they generate agen_pycache that breaks plainGetActiveObject(KeyError: '_dispobj_'). The server itself is immune since 0.5.0 (it never uses gen_py classes), but your scripts aren't: delete%LOCALAPPDATA%\Temp\gen_pyif it happens. See the API notes for the full story.
Claude Desktop
Claude Desktop reads the same mcpServers block from claude_desktop_config.json — use the full path
of the Python that has mcp and pywin32 installed (a bare python may be a different one):
Two things that cost us an afternoon:
- Where the file is. The Microsoft Store build of Claude Desktop does not use
%APPDATA%\Claude\claude_desktop_config.json. It keeps its data in%LOCALAPPDATA%\Claude-Data\claude_<id>\claude_desktop_config.json(the<id>is the package id, e.g.claude_pzs8sxrjxfjjc). If an edit seems ignored, look in%LOCALAPPDATA%\Claude\Logs\main.log— its paths show which folder the app really uses. - Edit it only while Claude Desktop is fully closed. The app writes its in-memory copy of the file
back when it quits, so an edit made while it runs is silently thrown away. Quit from the tray icon
(closing the window is not enough), edit, start it again.
Settings → Developershould then listinventoras running; its log is%LOCALAPPDATA%\Claude\Logs\mcp-server-inventor.log.
Several agents, several projects
Claude Desktop starts one server for all its chats, so several agents share it. Each agent gets its own Inventor:
- Tell each agent only its project: "Work in C:\…\Kiosk.ipj." It calls
connect(project=…)— the server reuses the Inventor that already has that project, takes the running one if it is free, or starts a separate Inventor named after the project. - With several connected, every call carries
instance=<name>(the agent learns the name fromconnect); a call without it is refused instead of guessing.list_instancesshows them all. - Each Inventor has its own call thread,
execute_pythonnamespace andmanage_call, so one agent's long job doesn't hold up the others.
Things to know:
- Let the server start the Inventors. Open at most one by hand. Windows hands every client the first
Inventor that started, so a second one opened by hand can't be reached (
list_instanceslists it as unreachable). - Restarting Claude Desktop (or the server) keeps the Inventors. Every Inventor the server starts is
handed to a small keeper process (
keeper.py) that outlives the server; after the restart each agent'sconnect(project=…)gets the same Inventor back, open documents and all (connect(pid=…)picks one explicitly;list_instancesshows them). The keeper lets go of an Inventor when its window closes and exits on its own when it holds none. Inventors opened by hand — and ones started by a server older than 0.7 — are not kept: save and close those before restarting. - Don't run tests in an agent's Inventor.
python tests/smoke_test.py --ownstarts its own Inventor and quits it. Exit your own scripts a few seconds afterapp.Quit(): a process that ends right away can leave a windowlessInventor.exebehind — which Windows may later hand to the next client that asks for a new Inventor. Tell an agent's Inventor from such a leftover by its open documents, not by its start time.
Smoke test
tests/smoke_test.py exercises every geometry-creating code path once against a live
Inventor and reports PASS/FAIL per step — the quickest way to qualify a new Inventor
release or verify your install:
It also checks every hard-coded enum constant against the live COM type library, so a renumbered enum in a future release shows up as a named failure instead of a cryptic COM error. Exit code = number of failed steps.
Current results: 137/137 pass on Inventor 2027.1 (Python 3.12, mcp 1.29 and 2.3).
tests/assembly_smoke_test.py does the same for the assembly tools — it builds a
plate and a pin on disk, places them, and exercises mate / flush / angle / insert
constraints (30/30 pass on Inventor 2027.1).
Skills (optional, recommended)
The skills/ directory contains two Agent Skills that teach Claude the workflow and the Inventor 2026 API quirks:
- inventor-modeling — core patterns: units, sketch discipline, hole placement, sheet metal, diagnostic verification, common failure modes
- inventor-din-parts — parametric recipes for DIN/ISO standard parts (hex nuts DIN 934 / 439, bolts DIN 933, socket head cap screws DIN 912, countersunk screws DIN 7991, washers DIN 125, flanges DIN 2573) with dimension tables
Install by copying into your skills directory:
Why this exists
Inventor's COM API documentation is wrong or silent about many things in recent versions. This project encodes empirically verified knowledge:
- Correct Inventor 2026 enum values (
kPartDocumentObject = 12290, dimension orientation19201/19202/19203, …) ChamferFeatures.AddUsingDistance(EdgeCollection, d)— the 2026 replacement for the removedCreateChamferDefinition- Sheet-metal
FlangeDefinition: the Distance argument is silently ignored; the real height is set viafeature.Definition.HeightExtent.Distance.Expression(and the angle is in radians — pass90and you get 5156°) CreateLinearPlacementDefinitionrequires aBiasPointargument that dynamic dispatch won't tell you about- Edge indices renumber after every feature; fillets shift adjacent edges
- …and more in docs/inventor-api-notes.md
Architecture
Contributing
Contributions welcome — see CONTRIBUTING.md for setup, the fast
edit → reload_api loop, and how to add a tool. Especially valuable:
- Testing on Inventor 2024/2025 — run
tests/smoke_test.pyand file an Inventor version test report (no code needed) - Drawing (IDW) support, and more modeling tools (shell, loft, sweep)
- More DIN/ISO part recipes
- Bug reports with the exact COM error and Inventor version
Start with a good first issue,
or ask and share what you built in Discussions.
License
MIT — see LICENSE.
Source: README.md at commit 18eda27
Tools
0Version history
5- v1.0.1LatestNov 1, 2026
- v1.0.0Oct 31, 2026
- v0.9.0Oct 29, 2026
- v0.4.0Oct 26, 2026
- v0.3.0Oct 25, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Other Autodesk integrations

Autodesk Product Help MCP
com.autodesk.aps.apiOfficial publisher
Remote, read-only MCP server that lets an assistant search official Autodesk Help and Support documentation across 110+ products.

Autodesk Revit MCP Server
Published by GitHub account Sam-AEC
Connects AI assistants to Autodesk Revit through a local bridge so they can review BIM model quality and fix Revit parameters.