If your firm uses an AI assistant that supports MCP (Model Context Protocol), you can connect it to Legatics so it can work with your live matter data. This means the AI can answer questions about your transactions accurately, using real data rather than general knowledge.
This article is for members who want to use an AI assistant with Legatics, and for the IT/developer, AI tool admin, or system admin setting up the connection.
How the connection works
When your AI assistant is connected to Legatics, it can query your matters, lists, and transaction data in real time. It can read your data and, where the connected app allows it, create and update records on your behalf — for example updating a status, adding a row, or marking a document for signing. It reads and writes only what's needed to answer your question or complete your request, and doesn't store it.
The connection is set up once by your system admin and IT/developer or AI tool admin. After that, each member signs in through the AI tool to grant it access to their data.
Note: Your system admin needs to create a connected app before you can connect your AI assistant. If the connection isn't set up yet, ask your system admin to read Create and manage connected apps.
For IT/developers and AI tool admins: set up the AI tool
These steps are done once for your firm. Members don't need to do them. For the full sequence, including allowlisting and redirect URLs, read the setup section of Legatics MCP explained.
Step 1: Get the connection details from your system admin
Ask your system admin for:
The MCP URL for your Legatics environment (see Finding your Legatics API and MCP URLs)
The client ID for the connected app
The client secret, if the connected app has one. Apps set up as a public client don't have a client secret, so you'll only need the client ID
Important: Treat the client secret like a password. Only the person configuring the AI tool needs it. Don't share it with members.
Step 2: Add the Legatics MCP server to your AI tool
The exact steps depend on the AI tool you're using. In most cases, you'll need to add the Legatics MCP server as a connector or integration within the tool's admin settings, then enter the MCP URL, client ID and, if issued, client secret.
Tip: For tool-specific steps, read Connecting Legatics to Claude, Connecting Legatics to Harvey or Connecting Legatics to Legora. For other tools, your AI provider's documentation will show you where to enter these details.
For members: connect your account
Step 3: Authenticate
Once your firm has added Legatics to your AI tool, connect to it from within the tool. When prompted, log in with your Legatics credentials to authorise the AI assistant to access your data. You don't need a client ID or client secret. This follows the standard OAuth flow: you'll be redirected to Legatics to confirm access, then returned to your AI tool.
The consent screen lists the permissions (scopes) the connected app is requesting. You can untick any you don't want to grant, but you can't grant more than the app was set up with — your system admin sets the ceiling when they create the connected app.
What you can ask
Once connected, your AI assistant can answer questions about your live Legatics data. Some examples:
"What's outstanding on the conditions list for [matter name]?"
"What's the recent activity on [matter name]?"
"Summarise the current status of [matter name]."
"Which tasks are assigned to me across my matters?"
"What documents are still waiting to be signed?"
"Mark the share purchase agreement as signed on [matter name]"
"Add a row for the board minutes under Corporate approvals"
"Assign the tax clearance CP to [person]"
"Send the disclosure letter for signing"
The more specific your question, the better. Include the matter name or relevant context where you can.
FAQ
Can the AI assistant change data in Legatics?
Yes, if your system admin has enabled it. Write access is controlled by scopes on the connected app. If the app carries the read_only scope, the AI assistant can only read and summarise your Legatics data. Otherwise, and where the app's scopes allow it, it can also create and update records — for example statuses, owners, rows, and parties.
Does the AI remember what it sees in Legatics?
No. The AI queries Legatics to answer a specific question. It does not retain or store your Legatics data between conversations. Each session queries fresh data.
Can the AI access all my matters?
The AI can access the matters you have permission to see in Legatics. It cannot access matters you don't have access to, regardless of the connected app's configuration.
My AI assistant says it can't connect to Legatics. What should I do?
Check the following:
You've completed the authentication step (Step 3 above)
The connected app is enabled - ask your system admin to confirm
The MCP URL entered in the AI tool is correct - ask your AI tool admin to check
Your Legatics session is active - try logging into Legatics directly first
api.app.legatics.comis allowlisted. This is the address Legatics uses for authentication, so the connection can't complete if your firm's network or your AI provider blocks it. Ask your IT/developer or AI tool admin to allow itThe connected app uses the right authentication type. If your AI tool doesn't ask for a client secret, or authentication fails after you're returned from Legatics, ask your system admin to check that the connected app is set to Public client
If you're still having trouble, contact Legatics support.
Will changes made by the AI show up in the audit log?
Yes. Any change the AI assistant makes is attributed to you, the authenticating member, in the Legatics audit log — just as if you'd made the change yourself.
How do I disconnect the AI assistant from my Legatics account?
Connected apps don't have a per-user access list: anyone at your firm with a valid Legatics login can authenticate through a connected app once it's set up. There's no way to disconnect just yourself.
To stop an AI assistant from accessing Legatics, ask your system admin to disable or delete the connected app. This stops the integration for everyone using it, not just you.
What can't the AI assistant do?
It can create and update records — statuses, owners, rows, parties, lists, and marking documents for signing — where the connected app's scopes and your own permissions allow it. It can't upload or attach the actual file content for a document; that step still has to be done manually in Legatics. It also can't grant itself more access than the connected app and your own Legatics permissions allow.