Connect AI Clients with MCP

ClashWise ships a Model Context Protocol (MCP) server, so an MCP-compatible AI client or IDE — for example Claude Desktop, or a coding assistant that supports remote MCP servers — can work with the coordinated clash data already in ClashWise. You can ask questions about clashes, sessions, and matrices in natural language and, when your organization allows it, prepare controlled clash edits.

Access is governed end to end: an organization admin has to enable MCP, each member only gets the capabilities an admin grants them, high-impact edits must be explicitly confirmed, and every tool call is recorded.

Before you connect

• Your organization must enable MCP access. It is off by default and stays off until an organization admin turns it on.
• You need granted capabilities. Admins grant capabilities per member — a connection can never do more than what your admin granted to you.
• Plan availability. MCP connections are part of the Clash Management cloud platform — see the pricing page for which plans include it.

Step 1 — Enable MCP for your organization (admins)

1. Sign in at https://clashwise.ai and open Organization from the navigation drawer.
2. In the CONNECTED AI card, select Manage to open the MCP access page.
3. Turn on Enable MCP connections.
4. Select Save MCP access.

While MCP is disabled, existing connections cannot call any ClashWise tools.

Step 2 — Grant member capabilities (admins)

On the same MCP access page, each active member has a capability grid:

• View clashes — browse and inspect coordinated clashes, including full details, comments, and viewpoint images (image links are time-limited).
• View sessions — read coordination session records and minutes.
• View matrices — inspect matrices and their applied rules.
• Edit clashes — prepare and confirm controlled clash edits.
• Manage sessions — create and update coordination sessions.
• Manage matrices — update rules on matrices you created (tolerance, defaults, responsible contact, active state), with the same confirm-before-change preview as clash edits. Matrices with AI edits disabled cannot be changed this way.

Viewing and editing are deliberately separate permissions — grant read access widely if you like, and keep Edit clashes for the members who own the data. Select Save MCP access after making changes; the save bar appears whenever there are unsaved changes.

Step 3 — Connect from your AI client

1. In your MCP client, add a remote MCP server with the URL:

   https://api.clashwise.ai/mcp
   

2. The client opens a browser window for sign-in. Sign in with your ClashWise account.

3. ClashWise shows an approval page listing the capabilities the client requested. Review them and select Approve.

4. The client completes the connection and the tools become available in its tool list.

If the approval page says your organization has not granted the requested access, ask an organization admin to enable MCP and grant you the needed capabilities (Steps 1 and 2).

Managing your connections

Open Connected apps from the navigation drawer to see every AI client connected to your account: the client name, its granted capabilities, and when it connected. Select Revoke to disconnect a client — revocation blocks its next token refresh immediately.

Controlled edits — nothing changes silently

For high-impact clash edits, the ClashWise MCP server does not apply changes directly. Your client first receives an exact before-and-after preview and must explicitly confirm it before ClashWise applies the change. If the client never confirms, nothing changes.

Auditing tool activity

Every tool call is recorded:

• Members see their own calls under Organization → Tool activity, alongside activity from Wise and the Navisworks plugin.
• Organization admins can filter the same page by any member.

Troubleshooting

• "Your organization has not granted the requested MCP access." — MCP is disabled for your organization, or you're missing one of the requested capabilities. An admin can fix both on the MCP access page.
• A tool call is denied after connecting. — Your admin may have removed a capability after you approved the connection. The connection only ever gets what is currently granted; ask your admin to re-grant it.
• A revoked client keeps appearing in Connected apps. — Revoked connections stay listed (marked revoked) for your records, but they can no longer refresh tokens or call tools. Approving the client again creates a fresh connection.