NavisCoord runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 7 Sep 2026.
Autodesk Navisworks coordination: clash triage, root causes, work plans and reports
We read the source, 20 h ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
var process = System.Diagnostics.Process.Start(new System.Diagnostics.ProcessStartInfo
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Navisworks coordination and clash detection via APS — reports, viewpoints, model objects.
Manage Kanera workspaces, boards, cards, checklists, comments, notes, automations, and reports.
Manage RD Station CRM contacts, deals, tasks and notes, with pipeline health reports
Read and triage bug reports captured by Session Replay for your verified domains.
Publish AI reports as managed native links with versions, access control, revocation, and audit.
Job orders for trades and field work: parts, labour, status, completion report, invoice payload.
Connect AI assistants to Itcons.app work orders, reports, projects, users, and resources.
No-code databases, forms, portals and AI sites. Manage records and automation via natural language.
Answers built from our own checks of this server.