One section in, one section out — on Markdown/GEML files, bad writes refused.
- Passed: Handshake
- Passed: Tools listed
- Passed: Updated recently
Median latency 70 ms · Last checked
Explore
Evidence for your next connection.
Independent measurements of remote MCP servers. Every observation has a timestamp.
Read-only probesMCP server · File & docs
Read official Autodesk documentation for 110+ products. No key required.
1 failed · 7 not measured
Median of successful probes over 7 days
Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.
Tool definitions returned by this server
Independent monitoring
Responded
The server completed its last measured handshake. This is an observation, not a guarantee.
Last checked| Test area | Passed | Failed | Unmeasured |
|---|---|---|---|
ConnectionCan a client connect and discover tools? | 5 | 0 | 0 |
Reliability & speedDoes it respond consistently and quickly? | 1 | 0 | 3 |
Access & authenticationWhat is required to use this server? | 1 | 0 | 2 |
Tool qualityAre the tool definitions usable by an agent? | 4 | 0 | 0 |
Publisher identityCan the publisher be traced to its source? | 3 | 1 | 2 |
Unmeasured means there is not enough evidence to decide. How these checks work
Start using Autodesk Product Help MCP
Choose your client, copy the configuration, then enable the server in your client’s MCP settings.
Run this command in your terminal, then restart Claude Code.
Claude Code
claude mcp add --transport http autodesk-product-help-mcp https://api.aps.autodesk.com/knowledge/public/v1/mcpCapabilities
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').
DiscoveredSearch 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).
DiscoveredRecent measurements
| Checked | Result | Response | Tools |
|---|---|---|---|
| Connected | 1213 ms | 2 | |
| Connected | 1230 ms | 2 |