List the ACC/BIM 360 hubs (accounts) visible to the current credentials, with their account ids and data region. The accountId (without 'b.') is what the project-administration tools need.

List projects of an ACC account (hub), newest API, with filters and pagination. Also use this with classification='template' to discover project templates for acc_create_project.

Get one project's details including per-product activation status (docs, designCollaboration, ...). Use after acc_create_project to check that product activation finished (statuses become 'active').

Create an ACC project (optionally cloned from a template) — the first step of setting up a CDE. The signed-in user (acc_login) must be an account admin of the hub. Product activation is ASYNCHRONOUS: poll acc_get_project until products show 'active', then add a project admin with acc_add_project_user (this also triggers member copy from the template).

Location (latitude/longitude, address) can ONLY be set here at creation — the ACC Admin API has no project-update endpoint, so an existing project's location must be changed in the ACC UI (Project Admin > Settings).

List members of a project with their company, roles, access levels and product access. The returned 'id' (ACC user GUID) and 'autodeskId' are the subject ids used by the folder-permission tools; 'roleIds'/'roles' reveal the project's role ids for ROLE-based permissions.

Add one member to a project with product access, company and roles. The signed-in user must be a project admin (or account admin). Rule: projectAdministration:administrator requires every other granted product to be administrator too.

Change a project member's company, roles or product access. Accepts an email and resolves it to the user id automatically.

Remove a member from a project (their data/history stays; access is revoked). Confirm with the user before calling.

Bulk-add up to 200 members to a project in one call (asynchronous server job). Good for mobilizing a full project team from a list.

List companies (partners) registered in the account — source of the companyId used when adding members and granting COMPANY folder permissions.

List custom attribute definitions (id, name, type, allowed values). With folder_id: the folder-level view (BIM 360 + ACC). Without: the ACC project-level registry, which also shows which definitions are bound to the file naming standard (namingStandardIds) — i.e. the ISO 19650 Status/Revision/Classification metadata fields.

Create a custom attribute definition on a folder — the way to add ISO 19650 metadata fields (Status/Suitability, Revision, Uniclass code...) when the ACC file-naming standard is not used or extra fields are needed.

Batch-read document metadata: title, revision number, process state, review/approval status (from ACC review workflows) and all custom attribute VALUES (e.g. Status S3, Revision P01). The daily status-checking tool for a CDE manager.

Set custom attribute values on a document version — e.g. move a container from S2 to S3, stamp the Revision, or fill the Uniclass classification. Attribute names are resolved against the folder's definitions; unknown names are reported with the available ones.

Read the ACC file-naming standard configured on the project (the ISO 19650 naming enforcement in ACC Docs): delimiter, fields with allowed codes, and metadata fields (Status/Revision/Classification). Read-only — the standard itself is configured in the ACC Docs UI (Settings > File naming standard). Useful for cross-checking against the project BEP convention.

Check the authentication state of the ACC connection.

Shows whether the APS app credentials are configured, whether a 3-legged user session exists (and for whom), 2-legged token cache state, the default region and the callback URL. Call this first in a session, and whenever an auth error occurs.

Sign in with an Autodesk account (3-legged OAuth with PKCE).

Opens the Autodesk login page in the default browser (non-blocking) and ALWAYS returns the authorization URL so the user can open it manually, then waits for the redirect on the local callback port, exchanges the code and stores the rotating refresh token. The wait is capped per call (~45 s) to stay under the MCP host's request timeout — if it returns "still waiting", the login page stays open and the callback keeps listening, so just call acc_login again with wait_only=true to keep polling until the user finishes. After ~15 days without use the session expires and this tool must be re-run.

Discard the stored 3-legged session (refresh token). Use before switching Autodesk accounts; sign in again with acc_login.

Show the signed-in Autodesk user (3-legged) and the ACC hubs the current credentials can see. Useful to verify access after login and to fetch hub (account) ids for the admin tools.

Get a file's info and its current (tip) version: version number, size, file type, last modified, process/review state and storage URN.

List the version history of a file (audit trail: who uploaded which version when) — supports the ISO 19650 traceability requirement.

Upload a local file to an ACC Docs folder. If a file with the same name already exists there, a NEW VERSION is added (correct CDE behaviour); otherwise a new document is created. Tip: validate the name against the project naming convention first (acc_validate_names). Uses chunked S3 upload, so large models are fine.

Download a document from ACC Docs to the local disk (or get a temporary signed URL with link_only=true, valid for a few minutes).

Copy a file version into another folder of the same project as a NEW document — the typical WIP → Shared / Published hand-off when not using an ACC review workflow. (ACC cannot move items via API; copy then delete the original in the UI if a move is required.)

Get the root-level folders of a project (e.g. 'Project Files' / 'Plans' in ACC Docs). Start here to obtain folder URNs before listing or creating subfolders. Also reveals namingStandardIds when a file-naming standard is active.

List the contents of a folder: subfolders and files with tip-version info (version number, size, last modified, process/review state, naming conformingStatus where available).

Create a single subfolder under a parent folder. For whole CDE trees use acc_create_folder_structure instead.

Create a whole (nested) folder tree in one call — the core of CDE setup per ISO 19650 (WIP / Shared / Published / Archived containers). Existing folders with the same name are reused, so the tool is safe to re-run (idempotent). Returns the created/existing folder URNs level by level.

Rename a folder (contents and permissions unaffected).

Delete a folder in ACC Docs (soft delete — the folder is hidden and can be restored with acc_restore_folder). Confirm with the user first.

Restore a previously deleted (hidden) folder.

Move a folder (with its contents) under another parent folder. Folder permissions defined directly on the folder move with it; inherited ones re-derive from the new parent — re-check with acc_get_folder_permissions.

Search recursively under a folder for files by exact name and/or type. Returns matching tip versions with their item (lineage) URNs.

List the available container-ID naming conventions and the current default. Bundled presets: 'iso19650-uk' (generic UK BIM Framework, the default). Each project adds its own convention by dropping a JSON file named after the project (e.g. '.json') in ~/.acc-mcp/naming, then selecting it via config_id or ACC_MCP_NAMING_CONFIG. With config_id, returns the full convention: field code tables, status & revision codes, classification system and the default CDE folder structure.

Validate file / information-container names against the project's ISO 19650 naming convention: field-by-field decoding with meanings, precise errors and closest-code suggestions. Accepts the optional -Status-Revision suffix (e.g. ...-0001-S3-P01). Use before uploading or when checking a delivery list.

Build a correct container ID from field values (validated against the code tables), optionally with the -Status-Revision suffix. Use when creating a new deliverable name — check the next free sequence number with acc_search_folder first.

Audit an ACC folder (tree) for naming compliance: every file name is validated against the ISO 19650 convention; ACC's own conformingStatus is reported when a naming standard is active. Returns compliance stats plus the list of non-conforming files with reasons — a standards/metadata QA check for routine (daily/weekly) CDE review.

Generate a generic ISO 19650 CDE folder structure (WIP / Shared / Published / Archived) from simple lists — project-agnostic, so any project can build its own tree. Returns a JSON structure ready to pass to acc_create_folder_structure (review it first, then create). Give the WIP disciplines, the Published milestones and the Shared subfolders for the project; or use from_config to pull a convention's predefined cdeStructure.

List who can access a folder (users / roles / companies), their permission level (named when it matches a standard ACC level) and whether it is direct or inherited from parent folders.

Grant or change folder permissions for users, roles or companies — the ISO 19650 access-control step of CDE setup (e.g. give the design team 'upload' on WIP, the client 'view_download' on Published). Automatically uses batch-create for new subjects and batch-update for subjects that already hold direct permissions on the folder. Requires CONTROL ('manage') permission on the folder.

Remove all DIRECT permissions of the given subjects on a folder. Inherited permissions from parent folders remain — remove them at the parent too if full revocation is needed. Project admins cannot be removed. Confirm with the user before calling.

List the document approval workflows configured in ACC (steps, reviewers/approvers, approval status labels, copy-files destination). These are the controlled WIP→Shared→Published transitions of the ISO 19650 CDE. Workflows are created in the ACC UI (or acc_create tools may not cover every option) — this shows what exists and the workflowId needed to start a review.

List document reviews (approval processes) in a project — e.g. all OPEN reviews awaiting action, for the daily CDE follow-up.

Get one review's detail: status, current step and due date, per-step progress (who acted, decisions) and optionally the files in the review. Note: step decisions (approve/reject) can only be made in the ACC UI, not via API — use this to monitor and chase.

Start (initiate) a document review on an existing approval workflow — submitting containers for the checking/approval transition (e.g. S3 review or S4 stage approval). The subsequent approve/reject decisions happen in the ACC UI; monitor with acc_get_review.