Fusion - the Fusion 360 Bridge

@@ -21,7 +21,49 @@ over MCP. This bridge proxies it, so an Adom AI running in the cloud can use it. | **Fusion Data MCP** | CLOUD-hosted | navigate hubs/projects/folders, manage items, file permissions, team access | not this; a separate Autodesk service |  Everything below is the **local Fusion MCP**. If someone mentions folder management or permissions-over MCP, that is the Data MCP, a different thing.+over MCP, that is the Data MCP, a different thing, covered next.++## The Fusion Data MCP (the cloud one), and why we mostly do not need it++The **Fusion Data MCP** is a separate, **cloud-hosted** MCP server Autodesk runs. It is the data+side, not the modeling side, and it is worth understanding because it **overlaps heavily with our+own APS verbs**.++**What it is:** a remote MCP endpoint that authenticates with your **Autodesk account** and talks to+`developer.api.autodesk.com`. Its capabilities:++- **Hubs and projects**, navigate and query your organization's Fusion projects.+- **Folders and items**, create and organize folder structure within projects.+- **Permissions and access**, add team members, assign roles, manage who can access what.++**Does it need auth like APS?** Yes, and for the same reason: **it is APS underneath.** The Fusion+Data MCP is a thin MCP wrapper around the exact **APS Data Management API** that our `fusion_aps_*`+verbs already call. Same account, same `developer.api.autodesk.com`, same OAuth model.++**So do we need it? Mostly no.** This bridge already does the data-management work directly against+APS, and does it with a **never-charge cap** and auth **folded into the Fusion sign-in**:++| Fusion Data MCP capability | our equivalent |+|---|---|+| navigate hubs / projects | `fusion_aps_browse` |+| list / search files | `fusion_aps_search`, `fusion_aps_recent` |+| create folders, manage items | `fusion_aps_create_folder`, `fusion_aps_upload`, `fusion_aps_download`, `fusion_cleanup_cloud_files` |+| version history | `fusion_aps_versions`, `fusion_aps_file_info` |+| **permissions / team access / roles** | **not covered here** |++The one thing it does that we do **not**: **permissions and role management** (adding teammates,+assigning access). If a user specifically wants AI-driven team/permission management, the Fusion Data+MCP is the tool for it (or a future `fusion_aps_permissions` verb here).++**Reaching it is different from the local MCP.** The local Fusion MCP binds loopback, so a cloud AI+needs this bridge to proxy it. The Fusion Data MCP is **cloud/remote**, so a cloud AI can add it as a+**connector directly**, no bridge, no local Fusion, no subscription-gated toggle. That is also why+this bridge does **not** proxy it: there is nothing loopback to bridge, and its file-management+surface is already served, tested and free, by `fusion_aps_*`.++**Bottom line:** for finding and managing files, prefer our `fusion_aps_*` verbs (tested,+never-charge, one-login auth). Reach for the Fusion Data MCP only for permission/role management, and+connect the AI to it directly rather than through this bridge.  ## Why the bridge has to proxy it