ACC.MCP

Start a 3‑legged OAuth login for APS (user context). Opens the user's browser to the Autodesk sign‑in page. After the user logs in and grants consent, the token is cached to disk and auto‑refreshed. All subsequent API calls use the 3LO token (with the user's own permissions) until aps_logout is called. The OAuth scope is determined by the APS_SCOPE setting configured by the user.

Clear the cached 3‑legged OAuth token. After this, API calls fall back to the 2‑legged (app‑context) token.

Get a 2‑legged access token for Autodesk Platform Services (APS). Use this to verify that credentials are configured correctly. The token is cached and auto‑refreshed by all other tools, so you rarely need to call this explicitly.

Call any APS Data Management API endpoint (project/v1, data/v1). This is the raw / power‑user tool – it returns the full JSON:API response which can be very large (100 K+ tokens for folder listings). Prefer the simplified tools (aps_list_hubs, aps_list_projects, aps_get_folder_contents, etc.) for everyday browsing. Use this tool when you need full control: pagination, POST/PATCH/DELETE, or endpoints not covered by simplified tools.

Response guidance – when summarising large responses focus on: • Folders: name, id, item count • Files: name, type/extension, size, last modified, version info • Ignore: relationship links, JSON:API meta, and extended attributes unless specifically needed.

List all ACC / BIM 360 hubs (accounts) accessible to this app. Returns a compact summary: hub name, id, type, and region. Use the returned hub id (e.g. 'b.abc123…') in subsequent calls to aps_list_projects.

List projects in an ACC / BIM 360 hub. Returns a compact summary: project name, id, platform (ACC / BIM 360), and last modified date. Use the returned project id with aps_get_top_folders or aps_get_folder_contents.

Get the root / top‑level folders for an ACC / BIM 360 project. Common root folders: 'Project Files', 'Plans', 'Shared', 'Recycle Bin'. Returns folder name, id, and item count. Use the folder id with aps_get_folder_contents.

Get a summarised listing of a folder's contents. Returns a compact JSON with: summary (item counts, file type breakdown, total size), folders (name, id, item count), and files (name, id, type, size, version, dates). This is ~95 % smaller than the raw API response.

Supports optional filtering by file extension and hiding hidden items. For the full raw response, use aps_dm_request instead.

Get summarised metadata for a single file / item: name, type, size, version number, dates. Much smaller than the raw JSON:API response. Use for quick file lookups when you already have the item_id from a folder listing.

Build a recursive folder‑tree structure showing subfolder hierarchy and file counts per folder. Useful for understanding a project's organisation at a glance. ⚠️ Each level makes an API call, so keep max_depth low (default 3) to avoid rate limits.

Return APS Data Management quick‑reference documentation: common ID formats, typical browsing workflow, raw API paths, query parameters, BIM file extensions, and error troubleshooting. Call this before your first APS interaction or when unsure about ID formats or API paths.

Call any ACC Issues API endpoint (construction/issues/v1). This is the raw / power‑user tool – it returns the full API response. Prefer the simplified tools (aps_issues_list, aps_issues_get, etc.) for everyday use. Use this when you need full control: custom filters, attribute definitions, attribute mappings, or endpoints not covered by simplified tools.

⚠️ Project IDs for the Issues API must NOT have the 'b.' prefix. If you have a Data Management project ID like 'b.abc123', use 'abc123'.

Get issue categories (types) and their types (subtypes) for a project. Returns a compact summary: category id, title, active status, and subtypes with code. Use the returned subtype id when creating issues (issueSubtypeId).

List and search issues in a project with optional filtering. Returns a compact summary per issue: id, displayId, title, status, assignee, dates, comment count. Supports filtering by status, assignee, type, date, search text, and more. This is much smaller than the raw API response.

Get detailed information about a single issue. Returns a compact summary with: id, title, description, status, assignee, dates, location, custom attributes, linked document count, permitted statuses, and more.

Create a new issue in a project. Requires: title, issueSubtypeId (get from aps_issues_get_types), and status. Optional: description, assignee, dates, location, root cause, custom attributes, watchers. ⚠️ Requires 'data:write' in APS_SCOPE.

Update an existing issue. Only include the fields you want to change. ⚠️ Requires 'data:write' in APS_SCOPE. To see which fields the current user can update, check permittedAttributes in the issue detail.

Get all comments for a specific issue. Returns a compact list: comment id, body, author, date.

Add a comment to an issue. ⚠️ Requires 'data:write' in APS_SCOPE.

Return ACC Issues API quick‑reference documentation: project ID format, statuses, typical workflow, raw API paths, common filters, sort options, and error troubleshooting. Call this before your first Issues interaction.

Call any ACC Submittals API endpoint. This is the raw / power‑user tool – it returns the full JSON response. Prefer the simplified tools (aps_list_submittal_items, aps_list_submittal_packages, etc.) for everyday use. Use this tool when you need full control: pagination, POST/PATCH, or endpoints not covered by simplified tools (e.g. metadata, settings/mappings, users/me, item-types, responses).

The base path is: construction/submittals/v2/projects/{projectId}/ You only need to provide the sub‑path after 'projects/{projectId}/' (e.g. 'items', 'packages', 'specs').

List submittal items in an ACC project. Returns a compact summary: title, number, spec section, type, status, priority, revision, dates. Supports filtering by status, package, spec section, and review response.

Get full details for a single submittal item by ID. Returns the complete item object from the API.

List submittal packages in an ACC project. Returns a compact summary: title, identifier, spec section, description, dates.

List spec sections for submittals in an ACC project. Returns a compact summary: identifier (e.g. '033100'), title, dates. Spec sections are the specification divisions that submittal items are organised under.

Get attachments for a specific submittal item. Returns file names, URNs, revision numbers, and categories. Use the URN to download the attachment via the Data Management API.

Return ACC Submittals API quick‑reference documentation: endpoints, query parameters, statuses, custom numbering, typical workflow, and key concepts. Call this before your first Submittals interaction or when unsure about Submittals API usage.