MCP troubleshooting

Common issues when connecting or using Clment with Claude Desktop, and how to resolve each.

Updated 2 Jun 2026

The MCP connector is mostly invisible when it’s working. When it isn’t, the symptoms are often vague. Here’s a triage guide.

”Couldn’t connect to MCP server”

What you see when first adding the custom connector in Claude Desktop.

Check the URL. It should be https://api.clment.com/v1/mcp (not /mcp alone, not http://). For region-specific routing use https://us.clment.com/v1/mcp, https://eu.clment.com/v1/mcp, or https://au.clment.com/v1/mcp.

Confirm the host is reachable. Open the URL’s /health endpoint in your browser (e.g. https://api.clment.com/health). It should return a small JSON payload. If you get a connection error or a 503, the host itself is down — check status.

Real TLS certificates required. Claude Desktop only accepts MCP servers behind a publicly-trusted TLS certificate. The production Clment hosts (api.clment.com, us.clment.com, eu.clment.com, au.clment.com) all qualify; self-signed or locally-trusted certificates won’t be accepted.

”Authorize button does nothing”

You clicked Connect in Claude Desktop, expected a browser window to open for the Clment consent screen, and nothing happened.

  • Pop-up blocker. Some pop-up blockers stop the auth handoff. Whitelist clment.com (or your region’s host) and retry.
  • Default browser misconfigured. Claude Desktop hands off to whatever browser is set as system default. If your default browser is one you don’t use, the consent page opens in the wrong window. Set the right default and retry.
  • Already authenticated, different account. If you’re signed into a Clment org you don’t want this connector to grant access to, sign out first (or use a private/incognito window) before retrying.

”Token shows as expired” or constant 401s

The MCP token Clment issues is long-lived but can be revoked any of these ways:

  • You explicitly revoked it under Settings → Connect AI Agent.
  • Your account was removed from the org the connector was scoped to.
  • An Admin rotated MCP signing keys (rare; happens after a security event).

To fix: revoke the connector cleanly from the Clment side first (Settings → Connect AI Agent → Revoke), then in Claude Desktop remove the connector, then re-add and re-authorise from scratch. This rotates the underlying credential.

Skill calls succeed but the agent ignores results

Sometimes Claude reports having called a skill but seems unaware of the result. Common causes:

  • Truncated response. A get_contract_text on a 100-page contract returns a lot of text. Claude has internal context limits; very long responses may be summarised aggressively. Ask the agent to focus: “Use get_contract_text on CLM-42 and look specifically at the indemnity clause.”
  • Stale conversation context. Long conversations with many tool calls can lose earlier results. Start a fresh conversation if the agent seems confused by its own history.

”Org has no MCP connectors” on a Free org

Free-tier orgs can’t be linked to MCP custom connectors — this is intentional. The MCP surface is a paid feature.

To use Clment with Claude Desktop:

  • Upgrade to Pro — billing-on-credits, no per-seat charge. See Billing and credits.
  • OR use a different organisation. If you’re a member of both a Free org and a Pro org, the consent screen shows both — pick the Pro one for the connector.

Sometimes you have multiple Clment accounts (work + personal, or multi-region) and the consent page picks the wrong one.

  • Sign out of Clment in your default browser first.
  • Then click Connect in Claude Desktop.
  • The browser opens to the Clment sign-in page; sign in with the right account.

If you frequently switch between accounts, an incognito window for each authorise step keeps them clean.

”Skill not found” on a write action

If the agent tries a write skill (e.g. start_review) and gets “skill not found”:

  • You authorised the connector for read scope only. Revoke it (Settings → Connect AI Agent), re-add in Claude Desktop, and at the consent step grant read,write.

Audit log shows actions attributed to “A reviewer” or “Unknown”

This was a known issue resolved in May 2026. If you’re still seeing it on actions taken after that date, please contact support — the fix should be deployed everywhere.

For historic rows, we ran a one-time backfill to attribute actions to the right user where we could. A small number of pre-fix rows may still show as “A reviewer” — that’s a permanent record of the limitation at the time, intentionally not retroactively rewritten.

When all else fails

Send [email protected]:

  • Your Clment org id or sign-in email.
  • A description of what you were trying to do.
  • A screenshot of the error or the relevant Claude Desktop output.
  • Approximate time (so we can find the corresponding log entries).

We respond within one business day.

See also

Still have questions?

Instant article search