While using an Autodesk MCP server, you may occasionally encounter situations where a request does not produce the expected result. This does not necessarily indicate a problem with the server; instead, it may reflect how the MCP server was designed to operate, or it may point to a configuration or connectivity issue.

Connectivity and authentication issues

Before you can send a request, your AI application must establish a connection to the MCP server and, if required, authenticate successfully. Common causes of failure at this stage include:

• You cannot reach the MCP server due to network issues or server unavailability
• You are sending too many requests and the server is rate-limiting you

For servers that require authentication, you may also encounter failures if:

• Your authentication credentials are missing, invalid, or expired
• You have not granted the required consent or permissions

For remote MCP servers, check your network connection. If the server requires authentication, verify that your credentials are valid and up to date. For local MCP servers, verify that the server process is running and has not crashed or become unresponsive.

Validation failures

Your request may fail during validation, before the server executes the requested tool or returns the requested resource. This happens when the server determines that it cannot safely or correctly process your request. Common causes include:

• You omitted required inputs or provided incomplete information
• You provided input values that do not match the expected format or schema
• You requested a tool or resource that does not exist on the server

When this happens, review your request and ensure that it aligns with the server's documented tool schemas and input requirements.

Authorization and policy rejections

Even if you submit a well-formed request, the server may reject it based on policy rules. Common causes include:

• You are attempting an operation that the server restricts or disables by policy
• You are connected to a server that operates in a limited or read-only mode

For servers that require authentication, the server may also reject your request if you do not have permission to perform the requested action.

If the server rejects your request, consult the server's documentation to understand any access requirements or limitations.

Unexpected or incomplete results

In some cases, your request may succeed but the result may not be what you expected. Common causes include:

• You accessed a server that exposes only a subset of available data
• You received exactly what you requested, but not what you intended
• You received results shaped by domain-specific rules, filters, or defaults
• You requested a large result set that the server truncated or paginated

When this happens, refine your request or try a different approach, such as using a prompt provided by the server to guide the interaction.

Understanding error responses

When your request fails, you typically receive a structured error response that includes an error code and a descriptive message. Use these details to diagnose the issue and determine the appropriate next step.

Check the error response in your AI application's output or logs to understand why your request failed. Note that some failures, such as network timeouts or server crashes, may not return a structured error response at all.

Autodesk MCP servers execute only what you explicitly request and only within their defined boundaries. When something does not work, start by checking error messages. Then verify your inputs and, if applicable, your authentication. If the issue persists, consult server-specific documentation to resolve it.