Autodesk Product Help
Search Autodesk's official help and support documentation from your AI agent. Two read-only tools, 110+ products, 40 locales, no sign-in. Verified anonymous on 2026-08-18.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Autodesk Product Help via MCP
https://developer.api.autodesk.com/knowledge/public/v1/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Autodesk Product Help Tools & Capabilities (2)
Returns the canonical Autodesk product catalog (closed set). Each item has: product_name, product_code, and release_codes. Use this to discover or validate product values for other product-scoped tools. Not required if valid product context is already available. Terminology: release_codes = the code only (e.g. 2025), not the human-readable release name (release_name, e.g. 'AutoCAD 2025').
Search Autodesk Help/Support documentation and return the most relevant documents for a user question. Use when: - The user asks how to do something in an Autodesk product. - The user reports an error (include the exact error text/code in the query). - The user needs official troubleshooting steps or reference documentation. Call shape (recommended): - Always pass: `query`, `locale`. - If your agent has a default product context, pass it directly via `product_code` (preferred) or `product_name`. - Pass `release_code` only when you can validate it for that product. Behavior: 1) Locale: - Read `locale` from your current context. Do not guess locale. - Pass that locale as the `locale` parameter. 2) Product and release filters (best-effort): - If your agent already has a default `product_code` or `product_name`, pass it directly. - Only call `get_available_products` to validate/normalize when: a) product is missing/unknown in context, OR b) the user explicitly specifies a product that may differ from your default, OR c) you have a `release_code` that may not be valid for the product, OR d) the product/release value appears malformed or not an allowed enum/value. - If you cannot confidently map to an exact allowed value from `get_available_products`, omit that field rather than guessing. - If both `product_name` and `product_code` are present, they must refer to the same product; `product_code` takes precedence. 3) Query construction: - Make the query keyword-rich: include product + feature/task nouns. - Include exact error text/codes when relevant. - Use the user's wording where possible. - Do not include secrets, credentials, or personal data. Returns: - Up to `max_results` documents sorted by relevance. Each item includes title, url, locale, body, media_type, source (and may include internal IDs for debugging/deduplication).
Read from the server on 2026-08-18, including each tool's own safety annotations.
Limits
- Prompts and resources are declared and empty.
initializeadvertisespromptsandresources, each withlistChanged: true. On 2026-08-18prompts/listreturned an empty array,resources/listreturned an empty array, andresources/templates/listreturned an empty array. None returned error-32601, which is what an undeclared capability returns — so these are surfaces the server claims and does not populate, not surfaces it never offered. A prompt picker or resource browser pointed at this server will be blank. Autodesk's own concept documentation acknowledges the general case, stating that while all its MCP servers provide tools, not all provide resources and prompts. - It declares a UI extension with no UI behind it. The capabilities block includes
extensions: {"io.modelcontextprotocol/ui": {}}— an empty declaration of the MCP UI extension. There is nothing to render it:resources/listis empty, so no widget resource exists; neither tool carries UI metadata in its_metablock; and Anthropic's directory entry does not set thehas_mcp_appflag it sets for connectors that ship an interactive app. We found no evidence this server renders a widget anywhere, and we do not claim it does. - The server publishes an OAuth descriptor it does not enforce. An RFC 9728
oauth-protected-resourcedocument for this endpoint returns HTTP 200 and names an authorization server plus scopesmcp:read,mcp:writeandoffline_access. The endpoint nonetheless answers anonymously with noWWW-Authenticatechallenge. Two things follow: a strict client that treats the descriptor as a gate may demand a sign-in the server does not want, andmcp:writeis declared on a server whose only two tools are annotated read-only. - A rate limit exists but is not documented. Every response carries
ratelimit-value: 14000and aratelimit-remainingcounter, observed across repeated probes on 2026-08-18. The remaining count moved between probes without tracking our own call count, so the quota appears to be shared rather than per-client. Neither header is mentioned in Autodesk's documentation, and we make no claim about the window it applies over. - The documentation's product codes are not the tool's product codes. The Appendix: Product Coverage page lists what it calls UPI codes, and many are not valid values for the
product_codeparameter. Of 34 we checked against the live enum on 2026-08-18, 15 were absent — includingNAVfor Navisworks,BUILD,TAKEOFF,FLAMEandfusion360for Fusion. Since the tool treats product values as a closed set and its own description says to omit a field rather than guess, copying a code from that appendix can produce a validation error. Resolve products throughget_available_productsinstead, which is what Autodesk's tips page advises. - The docs list a locale the server does not accept. Autodesk's language-mapping table includes
ru_RUfor Russian. That value is not in the livelocaleenum of 40, read on 2026-08-18. The table is presented as a mapping aid for older three-letter Autodesk language codes rather than as the authoritative list, and the tools page correctly says the schema validates the locale. - Coverage is documentation, not your data. The connector reaches Autodesk's published help and support corpus. It cannot see your drawings, models, projects, hubs, licences or entitlements, and there is no tool that could. For those, Autodesk operates separate MCP servers with account sign-in or host-managed authentication.
- Product coverage is broad but bounded. Autodesk states 110+ products with active documentation, spanning releases 2018–2026 plus cloud products, and says locales vary by content source and tool configuration. The live catalogue enum carries 243 product codes and 244 product names, which is a superset of the appendix's curated list — some entries in it are visibly retired or internal, with names ending "DO NOT USE".
- We did not call either tool. Our check was a read-only
initialize,tools/list,prompts/list,resources/listandresources/templates/listhandshake. Every behavioural claim above comes from the server's own schemas and descriptions, or from Autodesk's published documentation.
Frequently asked questions
Does the Autodesk Product Help MCP server require an Autodesk account?
No. Autodesk's own connection documentation states this is a public server that requires no sign-in, so no API key or headers are needed. Our anonymous handshake against the published endpoint on 2026-08-18 returned both tool definitions with no credential attached. The endpoint sits on Autodesk's developer API host, but the public path is deliberately open.
Why does the connector return no results or irrelevant results?
The query is usually too conversational. Autodesk's troubleshooting page advises short, specific keywords or exact error text rather than long questions, and says to always include a locale. If you scope by product, it requires an exact product code from the catalogue tool. Guessed product values are the second most common cause of empty results.
How do I get Autodesk help results in a language other than English?
Ask for the language in your request, or pass the matching locale. Autodesk's documentation says to state it conversationally, for example asking for results in German. The search tool requires a locale parameter, and its live schema accepts 40 values including de_DE, fr_FR, ja_JP and zh_CN. Autodesk warns clients not to guess the locale.
Why does nothing happen when I ask Claude about Autodesk documentation?
The client almost certainly has not loaded the server. Autodesk's troubleshooting page says to confirm the server is configured and then fully restart the client, quitting Claude Desktop completely rather than closing the window. It offers a one-line test: ask for a list of all available Autodesk products. If that works, the connection is fine.
Can the Autodesk Product Help connector change anything in my Autodesk files?
No. Both tools are annotated read-only and non-destructive by the server itself, verified on 2026-08-18, and Autodesk's own client documentation describes the server as public, unauthenticated and read-only. Neither tool accepts a file, a project, a hub or a credential. It searches published help documentation and returns links and text.
Why is the Autodesk connector available in one Claude Code project but not another?
Claude Code added it at local scope, which is per-project and private to you. Autodesk's troubleshooting page says to re-add the server with a user scope to make it available across all your projects, or a project scope to share it with your team through a checked-in configuration file. Flags must precede the server name.
Is the Autodesk Product Help MCP server the same as the Autodesk Fusion connector?
No, they are different servers with different architectures. Product Help is a remote server on Autodesk's public API host that searches documentation. Autodesk Fusion is a local extension that talks to a running Fusion session on your own machine to create and modify CAD geometry. Anthropic's directory lists both separately, at partner tier.
Sources
- Autodesk, "Autodesk Product Help MCP Server" (retrieved 2026-08-18, HTTP 200). This is the exact
documentationvalue in Anthropic's directory entry. It is a JavaScript viewer shell; the underlying content file is (HTTP 200), located by observing the viewer's own network requests rather than by guessing a path. Source for the endpoint table with its public audience and no-auth row, the common workflows, and the example prompts. · retrieved 2026-08-18 - Autodesk, "Autodesk Product Help MCP Server" (in-contents copy) (retrieved 2026-08-18, HTTP 200). The maintained version of the page above, reached from the help product's own table of contents at (HTTP 200). Source for the ChatGPT and Claude Code client support. · retrieved 2026-08-18
- Autodesk, "Tools and Language Support" (retrieved 2026-08-18, HTTP 200). The per-tool reference table, the required and optional parameter tables, the tips for successful tool calls including the closed-set and casing rules, and the locale-to-language-code mapping table containing
ru_RU. · retrieved 2026-08-18 - Autodesk, "Supported clients and IDEs" (retrieved 2026-08-18, HTTP 200). The Cursor JSON, the Claude Desktop
mcp-remoteconfiguration and log paths, the Claude Codeclaude mcp addcommand with its flag-ordering and scope rules, the ChatGPT app-directory route, and the statement that this is a public server requiring no sign-in so no API key or headers are needed. · retrieved 2026-08-18 - Autodesk, "Troubleshooting" (retrieved 2026-08-18, HTTP 200). The sole source for four of the seven FAQ questions on this page: the nothing-happens symptom and its restart fix, the no-results and irrelevant-results guidance, the wrong-language row, and the Claude Code scope row. · retrieved 2026-08-18
- Autodesk, "Appendix: Product Coverage" (retrieved 2026-08-18, HTTP 200). The 110+ product claim, the 2018–2026 plus cloud version range, the real-time sync statement, and the UPI code table cross-checked against the live enum in Limits. · retrieved 2026-08-18
- Autodesk, "Authentication and Access" (retrieved 2026-08-18, HTTP 200). The three authentication models across Autodesk MCP servers, and the statement that public remote servers expose non-sensitive information and are typically read-only while not being required to be. · retrieved 2026-08-18
- Autodesk, "About Autodesk MCP Servers" (retrieved 2026-08-18, HTTP 200). The statement that all Autodesk MCP servers provide tools while not all provide resources and prompts, cited in Limits against the empty-listing finding. · retrieved 2026-08-18
- Autodesk, "Handling Unexpected Results" — and "Governance overview and server types" (both retrieved 2026-08-18, HTTP 200). Rate-limiting and validation-failure guidance, and the local-versus-remote server taxonomy that separates this connector from the Fusion one. · retrieved 2026-08-18
- Live handshake against
https://developer.api.autodesk.com/knowledge/public/v1/mcp— anonymousinitializereturned HTTP 200, protocol2025-06-18, serverautodesk-knowledge-public-v1-mcp-server3.2.0, capabilitieslogging,promptsandresourcesandtoolswithlistChanged: true, an emptyexperimentalblock, anextensions: {"io.modelcontextprotocol/ui": {}}block, and an instructions string describing it as a public server for external consumers providing product catalogue access and help content search.tools/listreturned two tools with full input and output schemas and four-hint annotations;prompts/list,resources/listandresources/templates/listeach returned an · retrieved 2025-06-18 - Auth probe —
https://developer.api.autodesk.com/.well-known/oauth-protected-resource/knowledge/public/v1/mcpreturned HTTP 200 (2026-08-18) naming authorization serverhttps://developer.api.autodesk.com/mcpauthand scopesmcp:read,mcp:writeandoffline_access. The nested form under the endpoint path returned HTTP 404. The endpoint itself answered the anonymousinitializewith HTTP 200 and noWWW-Authenticateheader, which is what establishes the unauthorized posture on this page. · retrieved 2026-08-18 - Autodesk privacy statement — , the
privacy_policyvalue in Anthropic's directory entry. Recorded as the vendor's stated policy; it returned HTTP 403 to our client on 2026-08-18, so it was not read and we make no claim about its contents. · retrieved 2026-08-18 - Anthropic Connectors Directory entry — . Tier, categories, endpoint, transport, auth posture, permissions "Read",
prompt_names: []and both tool names, read from our committed directory snapshot dated 2026-08-16. It records the connector as added 2026-04-28, with aworks_withlist of Claude, the Claude API and Claude Code. A separate entry,ant.dir.gh.autodesk.fusion-mcp("Autodesk Fusion"), is a local partner-tier extension for a running Fusion desktop session and is a different server; the two are not conflated on this page. · retrieved 2026-08-16
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Productivity
- Developer
- Autodesk Product Help
- Tools
- 2
- Domain
- developer.api.autodesk.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.