Connecting Legatics to Claude lets your team ask questions about live matters, and update them, from Claude. A System admin sets it up once in Legatics and in Claude. Each user then signs in with their own Legatics account. Setup takes a few minutes if you have the right access on both platforms.
Before you start
You'll need:
System admin access to the Legatics Administration System
On Claude Team or Enterprise plans: Owner or Primary Owner access in Claude. On Enterprise, a custom role with Manage access to Libraries also works
On Claude Pro or Max plans: your own Claude account
Your firm's Legatics MCP URL
Region | MCP URL |
Europe |
|
United States |
|
Australia |
|
Note: If your firm uses a dedicated or private Instance, your MCP URL will be different. Contact your Legatics account team to confirm it.
Step 1: Create a connected app for Claude in Legatics
In the Legatics Administration System, go to Setup → Integrations and open the Connected apps tab.
Select Create connected app.
Under Application type, leave Confidential client selected.
Enter a Name, for example Claude, and an optional Description.
Under Redirect URLs, add
https://claude.ai/api/mcp/auth_callbackUnder Select at least one connection type, tick Legatics MCP.
Under Allowed scopes, choose the scopes your firm wants to allow.
Select Save.
Copy the Client ID and Client secret. You'll enter both in Claude in Step 2.
Note: The client secret is only shown in full once. If you lose it, select Regenerate secret and update the connector in Claude. The connection stops working until you do.
Step 2: Add the Legatics connector in Claude
If your firm uses Claude Team or Enterprise
The Owner adds the connector once for the whole organisation.
In Claude, go to Organization settings → Connectors.
Select Add, hover over Custom, then select Web.
Enter a name, for example Legatics, and your MCP URL. Select Continue.
Review the detected authentication settings and select Continue.
Under OAuth client, choose Use your own OAuth client. Enter the Client ID and Client secret from Step 1.
Select Add.
If you use Claude Pro or Max
In Claude, go to Customize → Connectors.
Select + Add, then Add custom connector.
Enter a name and your MCP URL. Select Continue.
Review the authentication settings and select Continue.
Under OAuth client, choose Use your own OAuth client. Enter the Client ID and Client secret you got from your System admin.
Select Add.
Step 3: Connect your Legatics account
Each user completes this step once.
In Claude, go to Customize → Connectors.
Find the Legatics connector. It usually has a Custom label.
Select Connect.
You're taken to Legatics. Log in and review the permissions on the consent screen.
Confirm. You're returned to Claude.
Note: Claude only sees the matters you can see in Legatics. Any change Claude makes is recorded in the audit log under your name.
Step 4: Use Legatics in a chat
In a chat, select + in the bottom left.
Select Connectors and turn on Legatics.
Ask a question that names the matter, for example "What's outstanding on the CP checklist for Project Atlas, and who owns each item?"
Once you've connected, the connector works in Claude on the web, in the desktop app, in the mobile apps and in Cowork. See Using AI assistants with Legatics for more example prompts.
Having trouble?
Claude says it couldn't reach the MCP server
Check that the MCP URL is right for your Instance. For example, the US URL is
mcp.us1.legatics.com, notmcp.usa.legatics.com.Check that the connected app is enabled in Legatics.
Authorisation fails, or you see a redirect error after logging in
Check that the redirect URL on the connected app is exactly
https://claude.ai/api/mcp/auth_callback.Check that the Client ID and Client secret in Claude match the connected app. If the secret was regenerated, update the connector in Claude.
Ask your IT team to allow
api.app.legatics.com. Legatics uses this address for authentication.
You use SSO and the login page asks for a password
You don't have a Legatics password if your firm enforces SSO. If the Legatics login page doesn't send you to your firm's SSO, contact support@legatics.com and include your Instance and the time you tried.
The connector is connected but Claude can't find any tools
Make sure Legatics is turned on for the chat (Step 4).
Disconnect and reconnect in Customize → Connectors.
Check that the connected app has at least one scope selected.
Claude can read but can't make changes
The connected app probably has the Read only scope. Ask your System admin to update the scopes if your firm wants write access.
If someone in your team can't connect
Check that they have an active Legatics account on the right Instance. If they do, share this article with them, or ask them to email support@legatics.com with their email address and the error they see.
FAQ
How do I turn the connection off?
To stop it for everyone, disable or delete the connected app in Legatics. To stop it for yourself, disconnect Legatics in Customize → Connectors in Claude.
Can Claude read the contents of documents in Legatics?
No. Claude can see document details and signing status, such as the name, version and who has signed. It can't open the files themselves or upload them.
Is this included in our Legatics licence?
Yes. The MCP server is included for all customers at no extra cost.
Still need help?
For SSO, firewall or network problems, contact your internal IT team first. For anything else, email support@legatics.com with your Instance, the step you got stuck on and any error message, and we'll help you get connected.