Connecting Claude Desktop

Use Clment as an MCP custom connector inside Claude Desktop in three steps.

Updated 26 Jun 2026

Clment exposes its full review surface as an MCP (Model Context Protocol) server, so you can drive Clment from inside Claude Desktop. Three steps: add the connector, authorize it once, then chat.

Before you start

You’ll need:

Claude Desktop — the standalone desktop app from claude.ai/download. The browser version doesn’t support custom connectors.
A Clment account with at least one organization. The MCP token is scoped to whichever org you authorize against, so make sure you’re signed in to the right one first.

1. Add the custom connector

In Claude Desktop:

Open Settings → Connectors.
Click Add custom connector.
Paste the MCP server URL: https://api.clment.com/v1/mcp (use your home region’s URL — us.clment.com, eu.clment.com, or au.clment.com if you know it).
Give the connector a name like Clment and click Add.

Claude Desktop discovers the OAuth metadata automatically and prompts you to connect.

2. Authorize once

Click Connect and Claude Desktop opens a browser window to Clment’s consent page. The page shows you exactly which Clment skills the connector is requesting — read, write, or both. Approve, and the connector is linked.

The token Clment issues:

Is scoped to one organization. To use Clment in another org from Claude Desktop, add a second connector and authorize against that org.
Carries your name and email, so any review actions taken via Claude Desktop are attributed to you in audit logs (e.g. “Simon Aspden signed off REV-12 via Clment AI”).
Doesn’t expire on a fixed schedule, but you can revoke it any time under Settings → Connect AI Agent in the Clment web app.

3. Chat

You can now ask Claude to do anything in the Clment catalog. Some examples:

“List my 5 most recent contracts.”
“Upload this URL and start a review with our standard vendor playbook.”
“For REV-12, accept all the AI’s recommendations and generate the redline.”
“Which contracts in my portfolio have unlimited liability exposure?”
“What does the limitation of liability say in CLM-42, and how does it compare to our standard?”

Claude routes each request through the matching MCP skill, calls back with citations to specific clauses where relevant, and lets you continue the conversation.

Uploading files

Ask Claude to “upload this contract” — a file attached to the chat, or a link — and it calls Clment’s upload skills. One thing to set up first:

Claude pushes file bytes from a network sandbox that keeps its own allowed-domains list, separate from the connector you just added. So the first local-file upload can fail with “host not in allowlist: …clment.com” even though the connector itself works. Fix it once: add the host shown in that error — the same host as your connector URL (e.g. au.clment.com) — to Claude’s allowed domains / network setting. Every upload after that just works.

Prefer not to touch the allowlist? Two routes skip the sandbox entirely:

Give Claude a link instead of a local file — a Google Drive, SharePoint, or any HTTPS URL Clment can reach. Clment fetches it server-side.
Drag the file into the Clment web app — the browser upload doesn’t go through Claude at all.

See Uploading contracts for the full picture.

Troubleshooting

“Couldn’t connect to MCP server” — check the URL has /v1/mcp (not /mcp alone). Confirm your region’s API is reachable in a browser — https://api.clment.com/health should return JSON.

“Authorize button does nothing” — check pop-up blockers in your default browser. Claude Desktop hands off to whatever browser is set as system default.

Token shows as expired or 401 — revoke the connector in Clment (Settings → Connect AI Agent), then re-add it in Claude Desktop. This rotates the underlying credential.

Still have questions?

Instant article search