Troubleshoot the MCP connection
| Symptom | Check |
|---|---|
| AI (MCP) panel is missing | Confirm that the running application includes the Module and that AI (MCP) is licensed and enabled under System > License. |
| “Unable to start MCP” | The port may already be in use. Choose an unused port, copy the new address, and reconnect. |
| Client cannot connect | Keep Model Vista running, enable AI connection enabled, and use the displayed /mcp URL with Streamable HTTP on the same computer. |
| Web Remote works but MCP does not | Check the independent AI (MCP) toggle and port. The Control Page URL is not the MCP URL. |
| No loaded models are returned | Use list_library_models to discover assets, then load a chosen result. |
| Model or State name is ambiguous | Discover again and use the returned ID instead of a shared name. |
| A tool or field is missing | Reconnect to refresh tools, then inspect application tools, fields, functions, and instances. Some controls require a loaded model or another entitlement. |
| Desktop camera command fails in XR | Keep XR and use available model/State controls, or intentionally exit XR and wait for readback before using camera tools. |
Change is rejected or applied is false |
Check busy state, transform locks, visibility rules, graphics availability, and license status. Read the actual state before retrying. |
| Turntable assignment is accepted but not confirmed | Read get_turntable; network acceptance can precede the actual assignment. |
| State is selected but no animation is visible | Inspect get_model_animation and the rendered view. Selected-option readback and advancing clocks do not prove visible motion. |
| Screenshot times out | Make the application or Game view visible and allow a rendered frame, then retry. |
| Job ID is no longer found | The listener may have restarted or the completed job may have expired. Inspect application state before repeating the operation. |
After a restart or license change
Section titled “After a restart or license change”Reconnect your AI client after changing the port, restarting Model Vista, or restoring the MCP entitlement. Refresh discovery before using previously returned instance IDs.
If a long operation times out in the client, check whether it is still running or has completed in Model Vista. A client timeout is not evidence that the operation was cancelled.
Report an issue
Section titled “Report an issue”Include the Model Vista version, AI client and version, selected MCP port, desktop/XR mode, exact tool name and arguments, returned error or status, and expected result. Describe whether the issue followed a model load, listener restart, license change, or XR transition. Remove credentials and private model information from shared logs and screenshots.
