Navisworks MCP
by navisworks-mcp.itmartin24.workers.dev in AI models & inference
Navisworks coordination and clash detection via APS — reports, viewpoints, model objects.
https://navisworks-mcp.itmartin24.workers.dev/mcp
Last 30 days
- Uptime
- 100%
- Response time
- 127 ms typical, 129 ms slowest 5%
- Last check
- 7 h ago
- Next check
- any minute now
How to call it
Add it to any MCP client that supports remote servers.
{
"mcpServers": {
"navisworks-mcp": {
"type": "http",
"url": "https://navisworks-mcp.itmartin24.workers.dev/mcp"
}
}
}5 tools
- nwd_upload
Upload a Navisworks file (.nwd/.nwf/.nwc) to Autodesk Platform Services (APS) Object Storage and start an SVF2 translation job so the model becomes queryable by the other nwd_* tools. When to use: at the start of a coordination workflow — e.g. the GC hands off a federated NWD co
- nwd_get_clashes
Detect geometric/logical clashes between two element sets in an already-translated Navisworks model. Uses APS Model Derivative property extraction + same-level proximity heuristics, optionally augmented by VDC rules stored in D1 (table vdc_rules). When to use: when coordinating
- nwd_export_report
Build a coordination report for a translated Navisworks model: translation status/progress, derivative outputs, available views (2D sheets / 3D viewables), total element count, and a per-category element breakdown. Doubles as the canonical way to poll translation status after nwd
- nwd_get_viewpoints
List saved viewpoints / camera positions and top-level view containers for a translated Navisworks model. Pulls the metadata view list and enriches each 3D view with its first two levels of the object tree (viewpoint folders typically live there in NWD files). When to use: when
- nwd_list_objects
List elements (objects) in the translated Navisworks model with their objectid, name, externalId, and full property bag, optionally filtered by a case-insensitive keyword matched against name and Category. When to use: when answering "how many VAV boxes are on Level 3?", "list e
Security scan
- No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 7 h ago | Passed | 200 | 112 ms |
| 16 h ago | Passed | 200 | 143 ms |
| 26 h ago | Passed | 200 | 129 ms |
| 36 h ago | Passed | 200 | 127 ms |