Autodesk Construction Cloud via APS — projects, issues, RFIs, documents, submittals.
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read from a real MCP initialize → tools/list handshake against the declared endpoint. No tool was ever invoked — tools/list is the read-only introspection call the protocol defines for this. It reflects what the server advertised at that moment; a hosted endpoint is not pinned to any version and can change without notice.
https://acc-mcp.itmartin24.workers.dev/mcp9 tools · 483msacc_list_projectsEnumerate every ACC and BIM 360 project the authenticated APS app can see by walking all accessible hubs and their project lists.
When to use: The agent needs to discover project IDs before calling any other tool (e.g. the user says 'show me my projects' or 'find issues in the Tower project' and n…Enumerate every ACC and BIM 360 project the authenticated APS app can see by walking all accessible hubs and their project lists. When to use: The agent needs to discover project IDs before calling any other tool (e.g. the user says 'show me my projects' or 'find issues in the Tower project' and n…
No input schema was published for this tool.
acc_create_issueCreate a new ACC issue (field observation, coordination clash, safety, quality, etc.) in the target project via the APS Construction Issues API.
When to use: The user wants to log a new issue — e.g. 'open a high-priority issue about the leaking valve on level 3' or a downstream agent detected a de…Create a new ACC issue (field observation, coordination clash, safety, quality, etc.) in the target project via the APS Construction Issues API. When to use: The user wants to log a new issue — e.g. 'open a high-priority issue about the leaking valve on level 3' or a downstream agent detected a de…
| Parameter | Type | Description |
|---|---|---|
| project_id* | string | ACC project ID. MUST use the 'b.' prefix literal (e.g. 'b.a1b2c3d4-...'). The worker strips the prefix internally for the Issues endpoint. Obtain via acc_list_… |
| title* | string | Short issue title, 1–255 chars. Required. |
| description* | string | Detailed issue description / body. Plain text, up to ~10,000 chars. Required. |
| priority | string | Issue priority. Defaults to 'medium' if omitted. |
| assigned_to | string | Optional APS user ID (oxygen ID / ACC user UUID) of the assignee. Leave null for unassigned. |
| due_date | string | Optional due date in ISO 8601 date format (YYYY-MM-DD). |
acc_update_issuePatch an existing ACC issue — change status, priority, assignee, or description via the APS Construction Issues API.
When to use: The user asks to close/reopen/escalate an issue, reassign it, or edit its body. Typical agent flow: acc_list_issues → pick an id → acc_update_issue.
When NOT to use: D…Patch an existing ACC issue — change status, priority, assignee, or description via the APS Construction Issues API. When to use: The user asks to close/reopen/escalate an issue, reassign it, or edit its body. Typical agent flow: acc_list_issues → pick an id → acc_update_issue. When NOT to use: D…
| Parameter | Type | Description |
|---|---|---|
| project_id* | string | ACC project ID. MUST use the 'b.' prefix literal. Obtain via acc_list_projects. |
| issue_id* | string | UUID of the issue to update, as returned by acc_list_issues or acc_create_issue. |
| status | string | New status. Project workflow may forbid certain transitions (e.g. draft → closed). |
| priority | string | New priority. |
| assigned_to | string | APS user ID of the new assignee. Omit to leave unchanged. |
| description | string | Replacement description body. Plain text. |
acc_list_issuesList and filter issues from a single ACC project (limit 50 per call) via the APS Construction Issues API.
When to use: The user or upstream agent needs to review open issues, count issues by status/priority, or look up an issue_id before calling acc_update_issue. E.g. 'show me all critical open is…List and filter issues from a single ACC project (limit 50 per call) via the APS Construction Issues API. When to use: The user or upstream agent needs to review open issues, count issues by status/priority, or look up an issue_id before calling acc_update_issue. E.g. 'show me all critical open is…
| Parameter | Type | Description |
|---|---|---|
| project_id* | string | ACC project ID. MUST use 'b.' prefix literal. Obtain via acc_list_projects. |
| status | string | Optional status filter. Typical values: open, in_review, closed, draft. |
| priority | string | Optional priority filter. Typical values: critical, high, medium, low. |
| assigned_to | string | Optional assignee APS user ID filter. Accepted but not currently forwarded as a URL filter by this server — filter client-side if needed. |
acc_create_rfiCreate a new Request For Information (RFI) in an ACC project via the APS Construction RFIs API. RFI is created in 'draft' status — the project workflow owner typically transitions it to 'submitted'.
When to use: The user needs a formal question-of-record to the design or GC team — e.g. 'raise an R…Create a new Request For Information (RFI) in an ACC project via the APS Construction RFIs API. RFI is created in 'draft' status — the project workflow owner typically transitions it to 'submitted'. When to use: The user needs a formal question-of-record to the design or GC team — e.g. 'raise an R…
| Parameter | Type | Description |
|---|---|---|
| project_id* | string | ACC project ID. MUST use 'b.' prefix literal. Obtain via acc_list_projects. |
| subject* | string | Short RFI subject/title, 1–255 chars. Required. |
| question* | string | Full RFI question body. Plain text, up to ~10,000 chars. Required. |
| assigned_to | string | Optional APS user ID of the person the RFI is directed to. |
| priority | string | RFI priority. Defaults to 'medium' if omitted. |
acc_list_rfisList and filter RFIs from a single ACC project (limit 50 per call) via the APS Construction RFIs API.
When to use: The user wants to review open RFIs, count outstanding ones, or look up an RFI ID. E.g. 'how many RFIs are still open on the Tower project?'
When NOT to use: Do not use for issues (us…List and filter RFIs from a single ACC project (limit 50 per call) via the APS Construction RFIs API. When to use: The user wants to review open RFIs, count outstanding ones, or look up an RFI ID. E.g. 'how many RFIs are still open on the Tower project?' When NOT to use: Do not use for issues (us…
| Parameter | Type | Description |
|---|---|---|
| project_id* | string | ACC project ID. MUST use 'b.' prefix literal. Obtain via acc_list_projects. |
| status | string | Optional RFI status filter. Typical values: draft, submitted, open, answered, closed, void. |
acc_search_documentsFull-text search the ACC Docs repository of a project for drawings, specs, submittals, and other files via the APS Data Management search endpoint.
When to use: The user wants to find a document by keyword (filename, sheet number, or metadata match). E.g. 'find the latest A-201 sheet' or 'search f…Full-text search the ACC Docs repository of a project for drawings, specs, submittals, and other files via the APS Data Management search endpoint. When to use: The user wants to find a document by keyword (filename, sheet number, or metadata match). E.g. 'find the latest A-201 sheet' or 'search f…
| Parameter | Type | Description |
|---|---|---|
| project_id* | string | ACC project ID. MUST use 'b.' prefix literal. The worker re-adds the prefix for Data Management URL formatting. Obtain via acc_list_projects. |
| query* | string | Free-text search string matched against filenames, titles, and indexed metadata. 1–500 chars. |
| document_type | string | Optional APS document type filter (e.g. 'items:autodesk.bim360:File', 'items:autodesk.bim360:Document'). |
acc_upload_fileprivilegedUpload a file from a public source URL into an ACC project folder. Runs the full four-step APS Data Management flow: top-folder discovery → storage object creation → OSS PUT of bytes → first-version item creation.
When to use: The user wants to push a document/photo/model into ACC Docs — e.g. 'upl…Upload a file from a public source URL into an ACC project folder. Runs the full four-step APS Data Management flow: top-folder discovery → storage object creation → OSS PUT of bytes → first-version item creation. When to use: The user wants to push a document/photo/model into ACC Docs — e.g. 'upl…
| Parameter | Type | Description |
|---|---|---|
| project_id* | string | ACC project ID. MUST use 'b.' prefix literal. Obtain via acc_list_projects. |
| file_url* | string | Publicly fetchable HTTPS URL of the source file. Must return 2xx to an unauthenticated GET. Max practical size ~100MB for this single-PUT implementation. |
| file_name* | string | Destination filename in ACC, including extension. 1–255 chars. Avoid path separators. |
| folder_path | string | Case-insensitive substring of the target top-level folder's display name. Defaults to 'Project Files'. Common values: 'Project Files', 'Plans', 'Photos', 'Subm… |
acc_project_summaryFetch the full ACC project metadata record (name, type, status, dates, extension attributes) for a single project via APS Data Management. If hub_id is omitted the tool picks the first accessible hub, which may be wrong on multi-hub tenants.
When to use: The user asks 'tell me about project X' or…Fetch the full ACC project metadata record (name, type, status, dates, extension attributes) for a single project via APS Data Management. If hub_id is omitted the tool picks the first accessible hub, which may be wrong on multi-hub tenants. When to use: The user asks 'tell me about project X' or…
| Parameter | Type | Description |
|---|---|---|
| project_id* | string | ACC project ID. MUST use 'b.' prefix literal (this endpoint — unlike Issues/RFIs — wants the prefixed form). Obtain via acc_list_projects. |
| hub_id | string | Optional ACC/BIM 360 hub ID. Also uses the 'b.' prefix literal. If omitted, the first hub returned by APS is used — prefer supplying this explicitly on multi-h… |
9 of 9 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Autodesk Construction Cloud via APS — projects, issues, RFIs, documents, submittals.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.