# Autodesk Product Help MCP

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

- name: com.autodesk.aps.api/product-help-mcp
- version: 1.0.12
- connection class: R0 (autonomous)
- trust: 100/100
- quality: 88/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/com.autodesk.aps.api%2Fproduct-help-mcp
- tools: https://api.protogrid.dev/v1/servers/com.autodesk.aps.api%2Fproduct-help-mcp/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "product-help-mcp": {
      "type": "http",
      "url": "https://api.aps.autodesk.com/knowledge/public/v1/mcp"
    }
  }
}
```


## Trust

- hygiene: 100
- liveness: 100
- freshness: 100
- provenance: 100
- drivers: +repository +namespace-matches-repo +dns-namespace +website +reachable +uptime-100% +updated-11d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 88/100 (good)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 93 (weight 30)

- pass `tools.descriptions`: every tool has a description
- warn `tools.description_length`: 1 tools have descriptions over 1,024 characters, which crowds the context
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 2 of 2 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- pass `tools.token_cost`: about 3,435 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: 1 tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 2, about 3,435 tokens to load them all
- tool set hash: 8613d07d554430b83420b778682ea431
- tools last changed: 2026-11-03T06:20:35.315Z
- badge: [![protogrid quality](https://protogrid.dev/badge/com.autodesk.aps.api/product-help-mcp.svg)](https://protogrid.dev/servers/com.autodesk.aps.api/product-help-mcp)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-11-03 `search_help_content` changed (inputSchema)

Full history: https://api.protogrid.dev/v1/servers/com.autodesk.aps.api%2Fproduct-help-mcp/changes

## Remotes

- https://api.aps.autodesk.com/knowledge/public/v1/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (2)

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