Autodesk Product Help MCP

com.autodesk.aps.apiPublished by api.aps.autodesk.comOfficial publisherv1.0.12Updated Oct 29, 2026

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

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingKnowledge & Memory

Overview

AI-generated overview

Remote, read-only MCP server that lets an assistant search official Autodesk Help and Support documentation across 110+ products.

What you can do
  • Search Autodesk Help and Support articles and product documentation, with ranked results including titles, URLs and text
  • Narrow searches by product, release code, source type and result count, in many languages and locales
  • List the supported Autodesk product catalog with product codes and release codes to validate filters
When to use it
Useful when users ask how to do something in an Autodesk product such as AutoCAD, Revit, Fusion or Maya, report an Autodesk error code, or need official troubleshooting and onboarding material cited from Autodesk's own documentation.
Requirements
A remote Streamable HTTP endpoint; nothing to install locally. No credentials, API keys or accounts are needed. The client must support remote HTTP MCP servers, and network access to the Autodesk endpoint is required.
Before you install
Read-only: the tools only retrieve published documentation and cannot change data. The public endpoint needs no authentication and does not access Autodesk accounts or customer data. Do not put passwords, license keys, access tokens or other sensitive data into tool arguments such as the search query. Fair-use rate limits apply, so heavy use may be throttled.

Installation

In SourceWeft

  1. Open Autodesk Product Help MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.autodesk.aps.api%2Fproduct-help-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

README

Autodesk Product Help MCP

Give any MCP-compatible AI client read-only access to Autodesk's official Help and Support documentation.

[MCP compatible] [Streamable HTTP] [No authentication] [Read-only]

Getting started · Tools · Examples · Troubleshooting · Docs


Autodesk® Product Help is a Model Context Protocol (MCP) Server that connects AI agents directly to Autodesk’s official product documentation across 110+ products including Autodesk Fusion®, AutoCAD®, Revit®, Inventor®, Maya®, Civil 3D®, and more. 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.

Key Features:

  • Ask support questions using natural language.
  • Learn and onboard to Autodesk products faster.
  • Create a foundation for AI agents and automation.
  • Available in 10 languages and 40 locales.

Requirements:

  • No special requirements.

About Autodesk

The world's designers, engineers, builders, and creators trust Autodesk to help them design and make anything. From the buildings we live and work in, to the cars we drive and the bridges we drive over. From the products we use and rely on, to the movies and games that inspire us. Autodesk's Design and Make Platform unlocks the power of data to accelerate insights and automate processes, empowering our customers with the technology to create the world around us and deliver better outcomes for their business and the planet. For more information, visit autodesk.com.

[!IMPORTANT] Autodesk hosts and operates this service, so there is nothing to install or run locally. This folder of the ai-integrations repository contains the MCP Registry metadata (server.json) and setup documentation.

Example prompts

Once connected, try asking your assistant:

  • How-to: "In AutoCAD, how do I create and manage layers using Layer Properties Manager?" or "In AutoCAD or Civil 3D, how do I create and assign a custom property to piping components using the Spec Editor?"
  • Troubleshooting: "In Revit, why are my linked CAD files not visible in a view, and how can I troubleshoot the issue?" or "What does AutoCAD error 1603 mean?"
  • Getting started: "I'm new to Revit. Show me a beginner tutorial for placing walls." or "Which Autodesk products does this help cover?"
  • Account and billing: "How do I sign in to my Autodesk account?" or "How do I upgrade my trial to a paid subscription?"

Getting started

Endpoint: https://api.aps.autodesk.com/knowledge/public/v1/mcp

Any MCP client that supports remote servers over Streamable HTTP can connect to this URL. No credentials are needed. A health check is available at https://api.aps.autodesk.com/knowledge/public/health.

Use it in Claude or ChatGPT

Autodesk Product Help is listed in both apps, so you can connect it without any configuration:

Add the server to your client

Claude Code
bash
claude mcp add --transport http autodesk-product-help \  https://api.aps.autodesk.com/knowledge/public/v1/mcp
Cursor

[Add to Cursor]

Or add it manually to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):

json
{  "mcpServers": {    "autodesk-product-help": {      "url": "https://api.aps.autodesk.com/knowledge/public/v1/mcp"    }  }}
VS Code

[Install in VS Code]

Or add it manually to .vscode/mcp.json in your workspace:

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

You can also run MCP: Add Server from the Command Palette, choose HTTP, and paste the endpoint URL.

Windsurf

Add the server to ~/.codeium/windsurf/mcp_config.json, then restart Windsurf:

json
{  "mcpServers": {    "autodesk-product-help": {      "serverUrl": "https://api.aps.autodesk.com/knowledge/public/v1/mcp"    }  }}
Other clients and SDKs

For other clients, add a remote HTTP server that points to the endpoint URL. The configuration key names vary, so check your client's MCP documentation.

To call the server from your own code, use an official MCP SDK.

Python (pip install "mcp>=2"):

python
import asyncio
from mcp import ClientSessionfrom mcp.client.streamable_http import streamable_http_client
MCP_URL = "https://api.aps.autodesk.com/knowledge/public/v1/mcp"
async def main() -> None:    async with streamable_http_client(MCP_URL) as (read, write):        async with ClientSession(read, write) as session:            await session.initialize()            result = await session.call_tool(                "search_help_content",                {"query": "AutoCAD error 1603", "locale": "en_US"},            )            structured = result.structured_content or {}            for doc in structured.get("results", []):                print(doc["title"], doc["url"])

if __name__ == "__main__":    asyncio.run(main())

TypeScript / Node.js (npm install @modelcontextprotocol/sdk):

ts
import { Client } from "@modelcontextprotocol/sdk/client/index.js";import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp.js";
const MCP_URL = "https://api.aps.autodesk.com/knowledge/public/v1/mcp";
const client = new Client({ name: "example", version: "1.0.0" });await client.connect(new StreamableHTTPClientTransport(new URL(MCP_URL)));
const { structuredContent } = await client.callTool({  name: "search_help_content",  arguments: { query: "AutoCAD error 1603", locale: "en_US" },});
for (const doc of structuredContent?.results ?? []) {  console.log(doc.title, doc.url);}
await client.close();

Let your agent set it up

Paste this into your AI coding agent:

text
Add the Autodesk Product Help MCP server to this environment.Use the setup documentation at https://github.com/Autodesk/ai-integrations/tree/main/product-help/remote-mcp-serverand the endpoint https://api.aps.autodesk.com/knowledge/public/v1/mcp(Streamable HTTP, no authentication). Verify the connection with initialize and tools/list.

Verify the connection

bash
curl -sS -X POST https://api.aps.autodesk.com/knowledge/public/v1/mcp \  -H 'Content-Type: application/json' \  -H 'Accept: application/json, text/event-stream' \  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{        "protocolVersion":"2025-06-18","capabilities":{},        "clientInfo":{"name":"curl","version":"1.0"}}}'

A successful response reports serverInfo.name as autodesk-knowledge-public-v1-mcp-server.

Tools

The server exposes two tools. Both are annotated as read-only, non-destructive, and idempotent.

ToolPurpose
get_available_productsList the supported Autodesk products, with their product codes and release codes
search_help_contentSearch Help and Support documentation and return ranked results with source URLs

get_available_products

Returns the product catalog as a list of { product_name, product_code, release_codes } objects. It takes no arguments.

Call it when you need a valid product_code or release_code to narrow a search. Release codes are identifiers such as 2025, not display names such as "AutoCAD 2025". The catalog can change over time, so treat this tool as the authoritative list rather than hardcoding values.

search_help_content

Searches Autodesk documentation and support articles and returns the most relevant documents.

ParameterRequiredDescription
queryYesKeyword-rich search text, 2 to 1500 characters. Include the product, the feature or task, and any exact error codes. Write it in the same language as locale.
localeYesLanguage and region for search and results, for example en_US, de_DE, ja_JP, or zh_CN. The tool accepts regional locale values, several of which can map to the same language (for example de_DE, de_AT, and de_CH are all German). The tool schema lists every accepted value.
product_codeNoLimits results to one product. Must be a value from get_available_products. Preferred over product_name.
product_nameNoAlternative to product_code. If both are set, they must refer to the same product.
release_codeNoLimits results to one release, for example 2025. Requires product_code or product_name, and must be a valid release for that product.
sourcesNosfdc_articles (support knowledge base articles), product_documentation (official product documentation), or both. Searches both if omitted.
max_resultsNoNumber of results to return, 1 to 50. Defaults to 5.

Each result includes title, url, locale, body (full text or an excerpt), media_type, and source. The response also includes total_results.

Example call:

json
{  "name": "search_help_content",  "arguments": {    "query": "AutoCAD Error 1603 install failed",    "locale": "en_US",    "product_code": "ACD",    "max_results": 3  }}

Best practices for agents

  • Call search_help_content directly when the product is already known. Call get_available_products only when you need to look up or validate a product or release code.
  • If you cannot map a product or release to an exact value from get_available_products, leave that filter out rather than guessing.
  • Make query keyword-rich: include the product and the feature or task, keep the user's wording where possible, and include exact error text or codes.
  • Write query in the same language as locale, and take locale from the user's context rather than guessing it.
  • Cite the url of each result you use, so users can read the original article.

Troubleshooting

MCP clients and SDKs handle the HTTP details for you. The HTTP errors below mostly affect custom integrations that call the endpoint directly.

HTTP errors

ResponseCause and fix
400 Invalid Content-Type headerSend Content-Type: application/json with every request.
404 The requested resource does not existThe URL is wrong. Use the endpoint exactly as shown in Getting started, without a trailing slash.
405 Method Not AllowedThe endpoint accepts JSON-RPC messages sent with POST. It does not offer a GET event stream.
406 Not AcceptableSend Accept: application/json, text/event-stream.
429 Too Many RequestsThe public endpoint applies fair-use rate limits. Slow down and retry with exponential backoff. The ratelimit-remaining response header shows how much of your allowance is left.
500 with PayloadParsingErrorThe request body is not valid JSON.

Tool errors

When a tool call fails, the HTTP request still succeeds. The tool result has isError: true, and its text starts with one of the codes below, followed by what went wrong and how to fix it. Most agents can read this message and correct their own request.

CodeCause and fix
INVALID_ARGUMENTSAn argument is missing or invalid, for example a missing locale, a query shorter than 2 characters, a max_results above 50, or a product_code or locale value that is not in the tool schema. Use the exact values from the tool schema and get_available_products.
INVALID_RELEASE_CODEThe release is not available for the chosen product. The error message lists the valid release codes.
RELEASE_CODE_REQUIRES_PRODUCTrelease_code was sent without product_code or product_name. Add a product, or remove the release filter.
INVALID_PRODUCT_SCOPEproduct_code and product_name refer to different products. Send only product_code.
INTERNAL_ERRORThe call could not be completed. First check that the tool name matches tools/list exactly, because an unknown tool name also returns this code. Otherwise it is a temporary server-side problem: retry later, and open an issue if it persists.

No results

If search_help_content returns total_results: 0, remove the release_code, product_code, and sources filters one at a time, or rephrase query using the product's own terms for the feature.

Reporting a problem

Send an x-request-id header with a new UUID on each request. The server returns the same value in its response. Include that value when you open an issue so the request can be traced.

Security and data handling

  • The service is read-only. The tools only retrieve published Help and Support content and cannot change any data.
  • The public endpoint does not require authentication and does not access Autodesk accounts or customer data.
  • Do not put passwords, license keys, access tokens, or other personal or sensitive data in query or in any other tool argument.
  • To report a security vulnerability, follow the Autodesk Vulnerability Disclosure Policy and submit your report through Autodesk on HackerOne. Do not open a public issue for security reports.

About this repository

The ai-integrations repository is the official distribution point for Autodesk AI integrations. This folder, product-help/remote-mcp-server, holds the Autodesk Product Help MCP files.

text
product-help/remote-mcp-server/├── server.json   # MCP Registry metadata├── README.md     # Setup and usage documentation└── LICENSE.md

server.json follows the MCP Registry schema and is used to publish the server to the Official MCP Registry.

See server.json for the current registry name, version, and remote endpoint.

server.json is maintained by Autodesk and changes only when a new version of the service is published.

Contributing

Contributions to the documentation and client setup examples are welcome.

  1. Fork the repository and create a branch for your change.
  2. Open a pull request that describes the change and how you tested it, for example with the curl check above.

The hosted service is not built from this repository. For feature requests or problems with the service itself, open an issue.

Support

License and terms

LICENSE.md covers the files in this repository only. It does not cover the hosted service or the Autodesk content that the service returns.

Use of the Autodesk Product Help MCP server is subject to the Autodesk Terms of Use and Privacy Statement.

Source: product-help/remote-mcp-server/README.md at commit b5c3654

Tools

2

get_available_products

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

Takes no parameters.

search_help_content

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

Parametersqueryrequiredlocalerequiredsourcesmax_resultsproduct_codeproduct_namerelease_code

Version history

1
  1. v1.0.12LatestOct 29, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Autodesk integrations