Troubleshooting

Note:

The Autodesk Fusion Compute MCP Server is in Public Beta — tools, supported operations, and behavior may change. Share feedback.

Use this table to diagnose the most common setup and session issues. Connection problems are listed first, followed by issues that appear while a session is running.

Symptom Likely cause Fix
No tools appear after adding the server Configuration not loaded Confirm the configuration is valid (double quotes, no trailing commas) and restart the client fully — a reload is not always enough. See Connecting to the Autodesk Fusion Compute MCP Server.
In ChatGPT, Plugins > Add does not show Create MCP App Developer mode is off, or your workspace does not allow it Turn on Developer mode, or ask your workspace admin to allow it. See OpenAI's ChatGPT Developer mode guide and Using ChatGPT on the web.
ChatGPT sign-in fails with invalid_scope ChatGPT's default OAuth settings request Autodesk scopes that this server does not grant In the plugin's Advanced OAuth settings, clear OIDC enabled and set OIDC scopes supported to only mcp:read, mcp:write, and offline_access. See Using ChatGPT on the web.
401 Unauthorized, or "Session not found" Your access token has expired Disconnect and reconnect the client to trigger a fresh sign-in, then retry.
Operations fail even though sign-in succeeded Missing entitlement Cloud operations are checked against your Autodesk account. Confirm you have an active Fusion license, then reconnect.
Starting a session fails with a cryptic "hub missing" message You do not have a Fusion Team hub linked to your Autodesk account Set up a free Fusion Team hub — see Set up a free Fusion Team hub below.
Starting a session is rejected with a "concurrency cap reached" message (per_user_running_cap) You already have two Fusion sessions running. Two concurrent sessions per user are allowed during the beta. Find your running sessions with fusion_sessions and close one with stop_fusion, then start again.
Starting a session is rejected or queued with an "at capacity" message (engine_running_cap) The service is at total capacity across all users Wait and try again shortly — capacity frees up as other sessions finish.
Starting a session returns a queued status Capacity is full — this is expected, not an error Wait for the server's queue updates, or check your position with fusion_status. When your request is admitted, start the session again and it launches immediately. To give up your place, call stop_fusion.
The session stays in a launching state The cloud worker is still starting A session normally becomes active in less than 10 seconds. If it still shows launching after 5 minutes, call stop_fusion and start a new session.
A tool call fails with "worker disconnected" The worker was ended by a timeout, a crash, or a capacity reclaim Call stop_fusion to clean up, then start a new session. Anything not already exported is lost.
invoke_fusion returns status: "working" and a callId instead of a result The call is taking longer than about 40 seconds — this is expected, not an error Collect the result with fusion_call_result and the callId. Do not send the call again, or it runs twice. See Long-running calls.
Your client gave up on a long call (timed out or was cancelled) The call keeps running in Fusion Call fusion_status. If it shows a pendingCall, collect the result with fusion_call_result and that callId. Do not send the call again.
A call is rejected because Fusion "is still running an earlier call" A session runs one call at a time Collect the earlier call with fusion_call_result (its callId is in the message), then send the next call. If it is stuck, call stop_fusion and start a new session.
A call fails because it "got no response within 300 seconds" The call ran past the 300-second limit Split the work into smaller calls. If the session no longer responds, call stop_fusion and start a new session.
fusion_call_result reports an unknown or expired callId The call was made more than 20 minutes ago, or on a different session Pass the engine_session_id the call was made on. A result older than 20 minutes cannot be recovered; run the call again.
A script is rejected for a top-level import or export, or fails with ReferenceError: exports is not defined Inline scripts run as bare scripts, not modules Remove the statement. adsk is already in scope as a value, and a type by name comes from a local alias — see "Writing scripts for MCP.ExecuteTypeScript" in Tools.
A script succeeds but returns no output adsk.log or adsk.result was reached through an alias or adsk["result"] Spell both literally. Output capture is a textual rewrite, so indirect access still runs but its output is not returned.
Your session is listed as closed after a break Idle sessions are stopped after 15 minutes of inactivity Start a new session. Call stop_fusion when you finish rather than leaving sessions open.
A download or viewer link returns an error Export links expire 15 minutes after the export Re-run the export to get a fresh link.

Set up a free Fusion Team hub

The Fusion Compute MCP Server requires a Fusion Team hub linked to your Autodesk account. If you do not have a Fusion subscription, or have never created or been invited to a team, you may not have one yet. You can create one quickly and for free:

  1. Sign up for the Fusion trial at autodesk.com/free-trials.
  2. Fill in the required information.
  3. The Fusion installer will download — you do not need to install it.
  4. Open your Autodesk Account settings and go to Products and Services.
  5. Find Fusion - Contributor in the list and press Access.
  6. Follow the instructions to create a hub.
  7. Once these steps are complete, your Autodesk account can use the Fusion Compute MCP Server.

What to include in a support request