Skip to main content
Glama

Autodesk Product Help MCP

Server Details

Read official Autodesk documentation for 110+ products. No key required.

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
Autodesk/ai-integrations
GitHub Stars
0
ChatGPT
–
Claude
–

TDQS

A4.6/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct roles: one returns a closed product catalog for validation, the other searches help documentation. The descriptions explicitly cross-reference each other, explaining when to call the catalog tool versus the search tool, so an agent cannot easily confuse them.

Naming Consistency5/5

Both names follow a consistent snake_case verb_noun pattern (get_available_products, search_help_content). The verbs ('get' for retrieval of a fixed set, 'search' for querying) accurately signal each tool's behavior.

Tool Count4/5

Two tools is on the thin side, but each earns its place: the catalog tool exists solely to validate/normalize inputs for the search tool, and the search tool is the core capability. There is no filler, though the surface is minimal compared with typical 3-15 tool servers.

Completeness4/5

The core lifecycle—discover valid product/release values, then search official documentation with those filters—is fully covered, and search returns document bodies so follow-up fetches are rarely needed. Minor gaps exist, such as no direct fetch-by-document-ID or browsing of documentation structure, but agents can work around these via search.

Available Tools

2 tools
get_available_productsGet Available ProductsA
Read-onlyIdempotent
Inspect

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

Inputs: no named parameters. Returns: result

search_help_contentSearch Help ContentA
Read-onlyIdempotent
Inspect

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

Inputs: query (required), locale (required), sources, max_results, +3 more. Returns: results, total_results

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to inspect and control running 3ds Max scenes across versions 2016–2025, including object queries, property edits, object creation and deletion, screenshots, file import/export, and MAXScript execution. It also provides API discovery and local documentation search to help verify available classes and properties before scripting.
      15
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to drive CAD workflows through 87 tools for documents, part studios, sketching, solid features, assemblies, drawings, measurement, rendering, and export. It supports zero-config browser sign-in and secure credential storage.
      87
      156 npm
      MIT
    • F
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to draw, edit, inspect, and manage CAD drawings through a consistent API, either headlessly without a CAD installation or by driving a live Windows session. It supports documents, layers, entities, transforms, hatching, dimensions, blocks, architectural workflow tools, and optional previews.
      43
      -
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.