Integration

Autodesk Platform Services integration

Autodesk Platform Services (APS, formerly Forge) gives access to the design files a user keeps in Autodesk Docs, BIM 360, Fusion and other Autodesk hubs. An agent can browse hubs, projects, folders, items and versions, create, rename, move and hide folders, rename items and versions, manage custom relationships, run Data Management commands, convert a version to another download format, translate a design with the Model Derivative API and read its manifest, model views, object tree, properties and thumbnail, and manage webhooks and their secret token. Not exposed: file upload and new item or version creation (they need the OSS signed S3 upload flow, which this reference serves only to app tokens), the signed-cookie derivative download, OSS bucket routes and the app-wide webhook list (app tokens only). Authentication is OAuth 2.0 (3-legged) as the signed-in Autodesk user, with the data:read, data:write, data:create and data:search scopes.

Connect Autodesk Platform Services How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Autodesk Platform Services.Built from the 59 Autodesk Platform Services tools below, on the connection you add once.

What you can do with Autodesk Platform Services

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Webhook, 8 operations

create_event_webhookCreate event webhookPOSTCreates a webhook calling callbackUrl when one event (for example dm.version.added) occurs in the scope. No body comes back: find it with list_event_webhooks. Deliveries are signed only once a secret token is set.
create_system_webhookCreate system webhookPOSTCreates webhooks calling callbackUrl for every event of a system (for example data) in the scope. No body comes back: find it with list_system_webhooks. Deliveries are signed only once a secret token is set.
delete_webhookDelete webhookDELETEDeletes the webhook specified by its ID.
get_webhookGet webhookGETRetrieves the details of the webhook for the specified event within the specified system.
list_event_webhooksList event webhooksGETRetrieves a paginated list of webhooks for the specified event. The returned list contains a subset of webhooks accessible to the provided access token within the specified region.
list_system_webhooksList system webhooksGETRetrieves a paginated list of webhooks for the specified system.
list_webhooksList webhooksGETRetrieves a paginated list of webhooks available to the provided access token within the specified region. Each page includes up to 200 webhooks.
update_webhookUpdate webhookPATCHUpdates a webhook: status (active or inactive), filter, hookAttribute, token, expiry or auto-reactivation. Leave out a field to keep its value.

Folder, 6 operations

create_folderCreate folderPOSTCreates a folder in a project, under the parent folder named in data.relationships.parent. Returns the new folder (data.id).
get_folderGet folderGETReturns the folder specified by the ``folder_id`` parameter from within the project identified by the ``project_id`` parameter.
get_folder_parentGet folder parentGETReturns the parent folder of the specified folder. In a project, folders are organized in a hierarchy. Each folder except for the root folder has a parent folder.
get_item_parent_folderGet item parent folderGETReturns the parent folder of the specified item. **Note:** This operation works with both BIM 360 Projects and Forma Projects.
list_top_foldersList top foldersGETReturns the details of the highest level folders within a project that the user calling this operation has access to. The user must have at least read access to the folders.
update_folderUpdate folderPATCHRenames, moves, hides or unhides a folder. For BIM 360 Docs and Forma folders, hiding a folder effectively deletes it.

Item, 4 operations

get_itemGet itemGETRetrieves an item. Items represent Word documents, Fusion 360 design files, drawings, spreadsheets.
get_version_itemGet version itemGETReturns the item corresponding to the specified version. **Note:** This operation works with both BIM 360 Projects and Forma Projects.
search_folderSearch folderGETSearches the specified folder and its subfolders and returns a list of the latest versions of the items you can access.
update_itemUpdate itemPATCHRenames an item (its displayName). Not supported for BIM 360 Docs and Forma items.

Version, 4 operations

get_item_tipGet item tipGETReturns the latest version of the specified item. A project can contain multiple versions of a resource item.
get_versionGet versionGETReturns the specified version of an item. **Note:** This operation works with both BIM 360 Projects and Forma Projects.
list_item_versionsList item versionsGETLists all versions of the specified item. A project can contain multiple versions of a resource item. **Note:** This operation works with both BIM 360 Projects and Forma Projects.
update_versionUpdate versionPATCHRenames a version of an item (the only property this route can change). Not supported for BIM 360 and Forma projects, where a rename needs a new version.

Download, 3 operations

create_downloadCreate downloadPOSTStarts a job converting a version to another download format (from list_version_download_formats). Check it with get_download_job; the format then appears in list_version_downloads.
get_downloadGet downloadGETReturns the details of a downloadable format of a version of an item.
list_version_downloadsList version downloadsGETReturns the list of file formats of the specified version of an item currently available for download. **Note:** This operation is not fully implemented as yet.

Hub, 3 operations

get_hubGet hubGETReturns the hub specified by the ``hub_id`` parameter. For BIM 360 Docs, a hub ID corresponds to a BIM 360 account ID.
get_project_hubGet project hubGETReturns the hub that contains the project specified by the ``project_id`` parameter. **Note:** This operation works with both BIM 360 Projects and Forma Projects.
list_hubsList hubsGETLists the hubs (BIM 360 or Forma accounts, Fusion teams, A360 hubs) the signed-in user can access. A hub id is the starting point for list_projects.

Webhook secret, 3 operations

create_webhook_secretCreate webhook secretPOSTSets the secret token used to sign webhook deliveries, for every webhook the signed-in user owns. Fails if a token already exists: use update_webhook_secret then.
delete_webhook_secretDelete webhook secretDELETERemoves the webhook secret token from the signed-in user's webhooks; deliveries are then no longer signed.
update_webhook_secretUpdate webhook secretPUTReplaces the webhook secret token of the signed-in user's webhooks. The change can take up to 10 minutes: accept both tokens for a while.

Folder relationship, 2 operations

create_folder_relationshipCreate folder relationshipPOSTCreates a custom relationship between a folder and another folder, item or version of the same project.
list_folder_relationshipsList folder relationshipsGETReturns the custom relationships associated with the specified folder.

Item relationship, 2 operations

create_item_relationshipCreate item relationshipPOSTCreates a custom relationship between an item and another folder, item or version of the same project.
list_item_relationshipsList item relationshipsGETReturns the custom relationships that are associated with the specified item.

Manifest, 2 operations

delete_manifestDelete manifestDELETEDeletes the manifest of the specified source design. It also deletes all derivatives (translated output files) generated from the source design.
get_manifestGet manifestGETRetrieves the manifest of the specified source design.

Object property, 2 operations

get_all_propertiesGet all propertiesGETRetrieves a list of properties of all objects in the Model View specified by the ``modelGuid`` URI parameter. This operation returns properties of all objects by default.
query_propertiesQuery propertiesPOSTQueries the objects in the Model View (Viewable) specified by the ``modelGuid`` URI parameter and returns the specified properties in a paginated list.

Project, 2 operations

get_projectGet projectGETReturns the specified project from within the specified hub. For BIM 360 Docs, a hub ID corresponds to a BIM 360 account ID.
list_projectsList projectsGETReturns a collection of active projects within the specified hub. The returned projects can be Forma, BIM 360, BIM 360 Team, Fusion Team, and A360 Personal projects.

Version relationship, 2 operations

create_version_relationshipCreate version relationshipPOSTCreates a custom relationship between a version and another folder, item or version of the same project.
list_version_relationshipsList version relationshipsGETReturns the custom relationships for the specified version.

Command, 1 operation

execute_commandExecute commandPOSTRuns a Data Management command on several resources at once, chosen by data.attributes.extension.type: CheckPermission, ListRefs, ListItems, GetPublishModelJob, PublishModel and others.

Design reference, 1 operation

specify_referencesSpecify referencesPOSTSpecifies the location of the files referenced by the specified source design.

Download format, 1 operation

list_version_download_formatsList version download formatsGETReturns a list of file formats the specified version of an item can be downloaded as. **Note:** This operation works with both BIM 360 Projects and Forma Projects.

Download job, 1 operation

get_download_jobGet download jobGETChecks the status of a job that generates a downloadable format of a version of an item.

Folder content, 1 operation

list_folder_contentsList folder contentsGETReturns a list of items and folders within the specified folder.

Folder link, 1 operation

list_folder_linksList folder linksGETReturns a list of links for the specified folder. Custom relationships can be established between a folder and other external resources residing outside the data domain service.

Folder ref, 1 operation

list_folder_refsList folder refsGETReturns the resources (items, folders, and versions) that have a custom relationship with the specified folder.

Item link, 1 operation

list_item_linksList item linksGETReturns a list of links for the specified item. Custom relationships can be established between an item and other external resources residing outside the data domain service.

Item ref, 1 operation

list_item_refsList item refsGETReturns the resources (items, folders, and versions) that have a custom relationship with the specified item.

Model view, 1 operation

list_model_viewsList model viewsGETRetrieves a list of Model Views (Viewables) in the source design specified by the ``urn`` URI parameter. The response also returns an ID that uniquely identifies each Model View.

Object tree, 1 operation

get_object_treeGet object treeGETRetrieves the structured hierarchy of objects, known as an object tree, from the specified Model View (Viewable) within the specified source design.

Thumbnail, 1 operation

get_thumbnailGet thumbnailGETRetrieves a thumbnail of the specified source design.

Translation format, 1 operation

list_translation_formatsList translation formatsGETRetrieves an up-to-date list of supported translations, including information on the types of derivatives that can be generated for each source design file type.

Translation job, 1 operation

create_translation_jobCreate translation jobPOSTStarts translating a design (input.urn) to svf, svf2, thumbnail, stl, step, iges, obj, ifc, dwg or fbx; returns at once. Poll get_manifest until status is success, failed or timeout.

Version link, 1 operation

list_version_linksList version linksGETReturns a collection of links for the specified version of an item.

Version ref, 1 operation

list_version_refsList version refsGETReturns the resources (items, folders, and versions) that have a custom relationship with the specified version.

Use Autodesk Platform Services from Claude Code, Cursor or Codex

Connect Autodesk Platform Services in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Autodesk Platform Services operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Autodesk Platform Services

Create your workspace
Sign up free. Nothing to install.
Connect Autodesk Platform Services once
Add your Autodesk Platform Services connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.