integrations.sh
← all integrations

Autodesk Product Help

MCP server claude productivitycreative

The Autodesk Product Help MCP Server connects AI agents directly to Autodesk's official product documentation, enabling accurate, real-time answers across 110+ products. As a secure, read-only interface, it allows AI tools to search, navigate, and retrieve trusted Autodesk help content. This enables support for natural language queries, accelerates onboarding, and provides a reliable foundation for intelligent agents built on authoritative Autodesk product documentation.

Homepage
https://help.autodesk.com/view/ADSKMCP/ENU/?guid=ADSKMCP_KnowledgeMcp_autodesk_product_help_mcp_server_html
Remote URL
https://developer.api.autodesk.com/knowledge/public/v1/mcp
Transport
streamable-http

Tools (2)

Extracted live via the executor SDK.

  • get_available_products

    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_help_content

    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).