Three deliberate steps
An organization admin turns on MCP access — it stays off until your organization chooses to enable it. Admins then grant each member the capabilities they need; reading clash data and editing clashes are separate permissions. Finally, add the server URL to your MCP client, sign in to ClashWise, and approve the requested access for that connected app.
Changes do not happen silently
For high-impact clash edits, your client first receives the exact before-and-after preview. It must explicitly confirm that preview before ClashWise applies the change.
Review, revoke, audit
Review and revoke the AI clients connected to your account whenever you need to. Tool calls are recorded for the user and organization, alongside activity from Wise and Navisworks.
Frequently asked questions
Which AI clients can connect to ClashWise?
Any MCP-compatible AI client or IDE that supports remote MCP servers with OAuth 2.1 sign-in. Add the ClashWise server URL, sign in when prompted, and approve the requested access.
Who controls what a connection can do?
Organization admins. MCP access is off until an admin enables it for the organization, and each member only gets the capabilities an admin grants them — viewing clash data and editing clashes are separate permissions.
Can an AI client change my clash data without asking?
No. High-impact edits return an exact before-and-after preview that the client must explicitly confirm before ClashWise applies the change, and every tool call is recorded in your organization activity.