Troubleshooting

Find the problem you see, then apply the solution. The first rows come from a user's real attempts to connect Claude Code in October 2026.

Before you begin

Connection

ProblemCauseSolution
Claude Code: invalid_request, redirect_uri does not match the client's registered redirect URLsA Client ID registered for Claude Desktop was used. Claude Desktop calls back to claude.ai; Claude Code listens on localhostDo not set a Client ID in Claude Code. It registers its own
Removing the Client ID changed nothingClaude Code keeps the old sign-in outside its configuration fileIn /mcp choose the server, then Clear authentication. On Claude Code 2.1.186 or later you can run claude mcp logout lawatlas instead. Then authenticate again
The server is not listed in /mcpThe server was added at a scope this project does not read, for example from a symlinked pathAdd it with --scope user
The server is still not listedThe session started before the server was addedRestart Claude Code
OpenAI Codex cannot connect to the SSE addressCodex uses streamable HTTPUse https://advisor.lawatlas.ai/api/mcp-http/mcp

Credentials

ProblemCauseSolution
HTTP 401No credential, or the key is unknown, revoked, suspended or expired, or issued in another environmentCheck LAWATLAS_API_KEY; check the key on the partner page
FORBIDDEN: keys are pausedThe owning organisation's AI Pro subscription is not activeRenew the subscription
A paid tool returns a sentence with a renewal linkA subscriber's AI Pro subscription has lapsedRenew, or call renew_subscription for the link
FORBIDDEN: not permitted from this network addressThe key's client has an IP allowlist that excludes your addressAdd your address on the partner page

Calls

ProblemCauseSolution
INSUFFICIENT_SCOPEThe partner client does not hold the tool's scopeAdd the scope to the client
TERMS_REQUIRED on a Hansard toolThe organisation has not accepted the current Hansard conditionsAccept them on the partner page
RATE_LIMITEDThe client used its calls for the minute or dayWait retry_after_seconds
TITLE_NOT_IN_FORCEThe title is not in forceShow the user the frl_link; Advisor does not serve its text
A response is cut shortIt hit the response size limitPage with the cursor, next_offset or next_from_paragraph the response gives

Check it worked

Call health. A good response has "status": "ok".

What to do if it did not

Contact support with the tool, the time and any reference in the error (Support).

Next steps