The following table lists common issues you may encounter when using the Autodesk Inventor MCP Server and possible solutions.
| Symptom | Likely cause | Fix |
|---|---|---|
| The AI client cannot connect, and reports "No running Inventor instance was found." | Inventor is not running. The proxy never starts Inventor itself. | Start Inventor, wait for it to finish loading, sign in to your Autodesk account, then reconnect the AI client. |
| The AI client cannot connect, and reports "Not signed in to Autodesk (A360)." | The Inventor session is not signed in. | Sign in from within Inventor, then reconnect the AI client. |
| The AI client cannot connect, and reports "Another agent is already connected to this Inventor instance." | Only one external AI client can be connected to an Inventor instance at a time. | Disconnect the other AI client first, then reconnect. |
| The AI client connects to a different Inventor session than expected. | More than one Inventor instance is running. The server connects to the first supported instance that is ready. | Close the other Inventor instances, then reconnect. |
| The AI client cannot connect, and reports "The Autodesk Assistant add-in is not ready yet." | Inventor is still loading and the add-in has not created its pipes yet. | Wait for Inventor to finish loading, then try again shortly. |
| The AI client cannot connect, and reports "This Inventor version does not support the public MCP server." | The running Inventor predates the release the public MCP add-in shipped in. | Use Inventor 2027.2 or later. |
| The AI client cannot connect, and reports "The Autodesk Assistant add-in was unloaded from Inventor." | The add-in was unloaded while Inventor kept running. | In Inventor, go to Tools > Add-Ins, select Autodesk Assistant, and turn on Loaded/Unloaded, then reconnect. |
| The connection drops mid-session with "The Inventor instance is no longer available." | The Inventor instance exited while the AI client was connected. | Restart Inventor and reconnect the AI client. |
| The AI client cannot connect, and reports "Invalid arguments. Expected one argument: /Inventor or /InvRO." | The args value in the configuration is missing, misspelled, or has extra entries. |
Set args to exactly ["/Inventor"], then restart the AI client. |
| The AI client cannot connect, and reports "Inventor RO is not supported." | The configuration uses /InvRO. Inventor Read-Only does not include the Autodesk Assistant add-in. |
Use /Inventor with a full Inventor installation. |
| In Cursor, the Autodesk Inventor MCP Server does not start. | Cursor may not support executable paths that contain spaces, such as C:\Program Files\.... |
Use the Windows short path for InvMcpStdio.exe in the Cursor configuration. See the Cursor section of Connect Your AI Client to the Autodesk Inventor MCP Server. |
| No tools appear in the AI client. | The MCP Server configuration is incomplete or the AI client has not reloaded the configuration. | Verify the MCP configuration file and restart the AI client. Check that the configuration file contains valid JSON. In JSON, each backslash in a Windows file path must be written as a double backslash. |
| In Claude Desktop, the Inventor tools are not available. | <> Code is not active. | Select <> Code at the top of the window, then start a new conversation. |
| Tools stop working mid-session with "Sign in to Autodesk (A360) from within Inventor before using the public MCP endpoint." | You signed out of your Autodesk account in Inventor after the AI client connected. | Sign in from within Inventor, then reconnect the AI client. |
| The server does not respond to prompts. | Inventor is currently in an editor mode, has a blocking dialog open, or an iLogic rule is waiting for input in a dialog box. | Finish or cancel the current editing operation and close any open dialog boxes before sending another prompt. |
| Queries return no results. | The query criteria are too restrictive or the requested objects do not exist in the current document. | Broaden the query criteria or verify that the specified document, Model State, or object names are correct. |
| The AI response is incorrect or unexpected. | Large language models (LLMs) can generate inaccurate or incomplete responses. | Verify AI-generated results before making changes to your Inventor documents. |
| Configuration changes do not take effect. | The AI client is still using the previous configuration, or the configuration was added to a different file than the one the AI client reads. | Restart your AI client after updating the MCP configuration. In Claude Desktop, turn on Developer mode if needed, then go to Settings > Developer > Edit Config to confirm which configuration file the application is using. For more information, see the Model Context Protocol documentation. |
| Expected tools are not available. | The running Inventor session has not yet loaded the tool source, or the tool belongs to a different environment. | Refresh the tool list (reconnect the client). Some tools are only available in specific environments — for example, assembly tools work only with an active assembly document. |
| A Python script is rejected before it runs. | The script imports a blocked module (for example os, subprocess, pathlib, or io) or calls exec/eval. |
Rewrite the script to use the Inventor API, or use the dedicated MCP tools for file operations. |
| A Python script fails because Python cannot be found. | Python 3.13 or later is not installed, the Python Executable path in Application Options is out of date, or python.exe is not on PATH. |
Install Python 3.13 or later, then set Application Options > File > Python Executable or add Python to PATH. |
| A Python script stops with "Script timed out after Ns (process killed)." | The script ran longer than its time limit (30 seconds by default). | Ask the AI client to run it with a longer timeout (up to 300 seconds), or make sure the script ends on its own instead of leaving windows or loops open. |
| An iLogic rule is blocked by the security scanner. | The rule uses APIs that iLogic security inspection flags. | Review the flagged items listed in the error. Ask the AI client to run a security check first and confirm before running the rule. |
| A request seems stuck while running an iLogic rule. | The rule opened a dialog box in Inventor and is waiting for input. | Switch to Inventor and respond to the dialog. |
The Autodesk Inventor MCP Server includes the following limitations:
execute_ilogic_code or run_ilogic_rule are not rolled back if they fail partway, and changes to external rule files, global event triggers, and external rule directories cannot be undone.Include your Inventor version, AI client name and version, the exact error message, and the time the issue occurred.
For help from the Inventor community and Autodesk support staff, post your question in the Inventor forum.