Use this table to diagnose the most common client setup and usage issues. Issues are grouped by client: general issues first, then a labeled block per client (Claude Desktop, Claude Code, ChatGPT, and Microsoft Copilot). The bold label rows are separators only.
| Symptom | Quick check | Likely cause | Fix / Steps |
|---|---|---|---|
| General issues | |||
| Nothing happens when I ask for documentation | Try: "List all available Autodesk products." | MCP server not configured, or client not restarted after config edit | Confirm the MCP server is configured in your client (Cursor: Cursor Settings: Tools & MCP; Claude Desktop: claude_desktop_config.json). Restart your IDE/client (Claude Desktop: fully quit and relaunch).Note: If "List all available Autodesk products." works, the connection is fine—move on to search/usage issues. |
| Search returns an error | Use a minimal valid JSON example | Malformed JSON (single quotes / invalid JSON) or missing required fields | Ensure inputs are valid JSON with double quotes and include required fields. Minimal example: {"name":"search_help_content","arguments":{"query":"tutorial","locale":"en_US"}} |
| Search returns no results (or irrelevant results) | Use short, specific keywords | Query is too long / too conversational; locale or product filter missing/wrong | Prefer keywords (for example "create wall" or exact error text) over long questions. Always include locale (for example en_US). If you need product scoping, provide exact product_code (preferred) or product_name from get_available_products, and optionally an exact release_code. Do not guess allowed values. |
| Wrong language | Confirm your request specifies the intended language | Default locale used, or locale not specified | Ask for the language explicitly (for example "…in German"). If a tool requires a locale input, provide the locale value it expects (for example de_DE)—do not guess. |
| Claude Desktop | |||
| MCP server not loading or errors | Validate config file JSON and endpoint URL | Config path/syntax issue; wrong npx path; wrong URL; proxy/TLS issues |
Check the config file path and JSON syntax (no trailing commas; use double quotes). Ensure the configured command points to your npx binary and the endpoint URL is correct.Note: Logs: macOS ~/Library/Logs/Claude/mcp*.log (for example tail -f ~/Library/Logs/Claude/mcp*.log). Windows: check under %APPDATA%\Claude\logs. |
| Claude Code | |||
| Server not added, or a flag seems ignored | Check the order of the command | Flags placed after the server name | Put all flags (--transport http, --scope) before the server name. See Supported clients and IDEs. |
| Server not connecting or tools missing | Run claude mcp list, or /mcp in a session |
Missing --transport http, wrong URL, or the session needs a refresh |
Confirm you added the server with --transport http and the correct endpoint URL. Use claude mcp list (or /mcp inside a session) to check its status, then start a new session. |
| Server available in one project but not another | Check the configuration scope | Added at the default local (per-project) scope | Re-add with --scope user to make it available across all your projects, or --scope project to share it with your team through a .mcp.json file. |
| ChatGPT | |||
| App added but its tools aren’t used | In the chat, confirm the app is turned on | The app isn’t enabled for that conversation | In the chat, select + > More and choose Autodesk Product Help MCP Server, then ask again. Unlike other clients, ChatGPT enables an app per conversation. |
| Can’t find "Autodesk Product Help MCP Server" in the directory | Confirm your plan and workspace allow apps | Plan doesn’t support apps, or a workspace admin hasn’t enabled or approved it | Use ChatGPT Plus, Pro, Business, Enterprise, or Education on the web. On Business, Enterprise, and Education workspaces, ask your administrator to enable or approve the app. |
| Microsoft Copilot | |||
| Answers read like general web results, and the connector’s tools aren’t used | Check whether web search is on | While web search is on, Copilot draws on public Autodesk support content and enterprise sources before it reaches the dedicated Autodesk connector | Turn web search off in Copilot, then ask again. Naming the connector in your request also helps (for example, "Using Autodesk Product Help, …"). See Microsoft Copilot. |
| Answers still don't use the connector, even with web search off | Ask your Copilot administrator whether your tenant prioritizes enterprise sources | Source selection is set by your organization's Copilot configuration, not by this server | Expected in some configurations, not a defect. Ask your Copilot administrator about source-priority settings if consistent connector use is required. |
| Not sure whether the answer came from this server | Look for the source of the answer in the response | Copilot synthesizes answers from multiple sources, so the source isn’t always obvious | Look for a citation, source reference, or other indication that identifies Autodesk Product Help. If none appears, turn off web search, refer to the connector by name, and try again. |