---
name: aps-construction-data
description: Read project data from Autodesk Construction Cloud / Autodesk Forma (Autodesk Docs is now Forma Data Management) through Autodesk Platform Services APIs or an APS MCP server - issues, RFIs, submittals, files and model properties - read-only, and turn it into digests, overdue lists and dashboards. Use when the user works in ACC, Autodesk Build, Autodesk Docs/Forma and asks about open issues, overdue RFIs, "incidencias abiertas", project status, or to connect an agent to ACC/Forma.
---

# Autodesk Construction Cloud / Forma data through APS

## Know the landscape (October 2026)
- Autodesk folded its construction cloud into **Autodesk Forma**; Autodesk Docs became **Forma Data Management**. The APS APIs (Data Management, ACC Issues/RFIs/Submittals, Model Derivative, AEC Data Model GraphQL) remain the developer entry point; check names in aps.autodesk.com because product labels changed faster than endpoints.
- Official Autodesk MCP servers today cover Revit (desktop), Fusion, Fusion Data and Product Help. For ACC/Forma data, the options are: Autodesk's samples (`aps-mcp-server-nodejs`, archived in May 2026 but still a useful reference; `aps-aecdm-mcp-dotnet` for the AEC Data Model), community MCP servers (review the code first), or direct API calls like `scripts/acc_issues.py`.

## Access (ask the user; never ask for their password)
1. An APS app (aps.autodesk.com > My Apps) provisioned in the ACC/Forma account by an account admin (Custom Integrations).
2. A token with `data:read`:
   - 3-legged (acts as the user, sees what they see), or
   - a Secure Service Account (SSA) invited to the project (acts as a dedicated account; good for scheduled digests).
3. Project ids: Data Management uses `b.<guid>`; the Construction APIs (Issues, RFIs...) use the bare `<guid>`. Strip `b.`.

## Procedure
1. Confirm which data the user needs (issues, RFIs, submittals, files) and the project.
2. Issues digest: `APS_TOKEN=... python scripts/acc_issues.py --project <id> --status open --md digest.md --out issues.csv`. Offline or for testing: `--from-json response.json`.
3. For RFIs or submittals, look up the current endpoint in aps.autodesk.com/en/docs/acc/v1/ before writing code; follow the same pattern (paging, read-only, CSV + digest).
4. Resolve assignee ids to names with the Admin API or ask the user for a mapping; never guess names.
5. Present: totals by status, overdue list sorted by due date, owners with most overdue items, and 3 suggested follow-ups (drafted, not sent).

## Output
- Digest (markdown) + CSV. For a recurring version, use the routine `acc-issues-digest`.

## Never
- Never create, edit or close issues/RFIs from this skill. Writes need a separate, explicit request and the user's approval per item.
- Never store tokens in files, prompts or logs; use environment variables and short-lived tokens.
- Never send project data to third-party services the user has not approved.