Clio assistant

Let your team's Claude or ChatGPT read and work in your firm's Clio, with every change recorded under the person who asked.

Quick links

Settings > Integrations > Clio assistant

Connect your firm's Clio app, your own Clio login, and set what the assistant may do.

Settings > MCP Server

The Clio server URL, and whether team members can make changes.

What the Clio assistant does

The Clio assistant connects your firm's Clio Manage account to Claude or ChatGPT through Superpractice. Your team can ask things like:

"What's the status of the Harper probate matter, and what's been billed?"
"Run a conflict check for Jordan Reyes."
"Log 0.5 hours on the Emery matter today: reviewed the file."
"Add a note to the Emery matter: client called about the closing date."
"Create a task on the Emery matter due Friday: call the client back."
"Put a client call on my calendar tomorrow at 2pm for the Emery matter."

Three things make it safe for a law firm:

Every change in Clio shows the person who asked. Each person signs in to Clio with their own login once. When Noah asks Claude to add a note, Clio records Noah as the author, not a shared account. Clio's own history stays accurate.
Your firm decides what it may change. It starts read-only. Owners and admins turn on changes, deleting and billing separately, and decide whether team members (not just owners and admins) can make changes.
Every call is logged. Your firm's activity log records who asked, which tool ran and whether it worked. Superpractice never uses your Clio data to train AI models. What Claude or ChatGPT reads is handled under your own plan with that provider, so check its data and training settings.

Separate from the Clio integration

The Clio integration brings retained matters, billing and payments into Superpractice for attribution and is read-only. The Clio assistant is a different connection that lets your AI tool work in Clio. They use different Clio apps and don't share access. You can use either or both.

Before you start

You need:

A paid Clio Manage plan. Clio doesn't allow apps on its EasyStart plan. Any plan above EasyStart works.
A Clio login for the firm owner or a Clio admin, to create the firm's Clio app. It takes about 10 minutes.
An owner or admin in Superpractice, to connect the app.
Claude or ChatGPT for each person who will use it, on a plan that allows custom connectors (Claude's paid plans; ChatGPT with developer mode).

You do not need to apply for a Clio developer account. A firm's own app (Clio calls it a private app) is created by signing in with the firm's normal Clio login, and Clio doesn't review it.

Step 1: Create your firm's Clio app

The assistant runs on an app your firm owns in Clio. Your firm chooses its permissions, can see and remove it any time in Clio, and no other firm shares it.

Go to developers.clio.com/apps/new and sign in with the firm's Clio login (the owner or a Clio admin). You'll see "New App".
Fill in the form:

Field	What to enter
Name	`Superpractice Assistant`. Your team sees this name on Clio's approval page.
Description	`Lets our AI assistant look up and update matters, contacts, tasks, time and documents in Clio.` Optional.
Icon	Optional. Leave it blank if you like.
Website URL	`https://superpractice.com`
Support URL	Optional. `https://superpractice.com/support` works.
Redirect URIs	Two lines, exactly: `https://app.superpractice.com/api/integrations/clio-assistant/callback` and `https://app.superpractice.com/api/integrations/clio/callback`. The second lets the same app also connect the Clio card.
Deauthorization callback URL	Leave blank.
Agreements	Tick Accept Developer Terms of Service.

Set Permissions. Tick only what's below. "Write" includes read.

Permission	Read	Write	What the assistant uses it for
Activities	✓	✓	Time entries, expenses and activity codes
Billing	✓	✓	Reading bills, creating trust requests, changing a bill's memo, due date or state
Calendars	✓	✓	Calendar entries and invitations
Communications	✓	✓	Logging calls and emails that already happened
Contacts	✓	✓	Finding, creating and updating contacts; conflict checks
Custom fields	✓		Reading your custom field definitions
Documents	✓	✓	Listing, uploading, generating from templates, download links
General	✓		Basic account information
Matters	✓	✓	Matters, stages, practice areas and matter notes
Payment distributions	✓		Not used by the assistant. Lets the Clio card read the payments applied to your bills when it uses this app, so Collected is right.
Tasks	✓	✓	Tasks and task types
Users	✓		Finding the right attorney or assignee
Webhooks	✓	✓	Not used by the assistant. Write only lets Superpractice set up its own change notifications, never change your data. Lets the Clio card get changes within seconds when it uses this app.

Leave everything else unticked: Accounting, Api, Court rules, Imports, Reporting, Settings, Custom actions, Client share permissions, Grants, Personal injury and Clio payments.

Further down, Clio Payments → Redirect URIs is a different field: it's where a client lands after paying. Leave it blank. Don't put the addresses from step 2 here.
Click Save. Your app opens with its App Key and App Secret. Keep this tab open for Step 2.

Your app's permissions are the ceiling

The assistant can never do more than the permissions ticked here, whatever you set in Superpractice. You can narrow them later in the Developer Portal; everyone then reconnects their Clio login once.

Step 2: Connect the app in Superpractice

An owner or admin does this once for the firm.

Already connected the Clio card with your firm's own app? Click Connect your app on the Clio assistant card and choose Your Clio card's app; there's nothing to paste. First, in Clio, add https://app.superpractice.com/api/integrations/clio-assistant/callback to that app's redirect URIs and give it the permissions from Step 1. Or choose A different Clio app to keep the assistant on its own app. Each app's keys are stored encrypted with its own connection.

Otherwise:

In Superpractice, open Settings > Integrations > Clio assistant.
Paste the App Key into Client ID and the App Secret into Client secret. They're stored encrypted and never shown again.
Click Connect your app. Clio asks you to approve the app. Sign in with your own Clio login and approve.
You're back in Superpractice with the Clio assistant Connected. Your own Clio login is connected at the same time.

The first person to connect sets which Clio account the firm uses. From then on, anyone who signs in with a login from a different Clio account is refused.

Every person who will use the assistant does this once, including team members.

Sign in to Superpractice with your own account.
Open Settings > Integrations > Clio assistant. Under Each person's Clio login, click Connect my Clio login.
Sign in on Clio's page with your own Clio login and approve.

Until someone connects their own login, the Clio tools don't work for them. Claude tells them to connect it. The assistant never borrows someone else's login, so nothing ever lands in Clio under the wrong name.

Owners and admins can see who has connected and how many changes each person made this week on the same card.

Each person needs a Clio license

Your team member needs an active Clio user in your firm's account. If Clio shows "User account not found" or "no active Clio Manage license", add them in Clio under Settings > Manage Users, have them accept Clio's invitation, then try again.

Step 4: Add the Clio connector to Claude or ChatGPT

Each person adds it to their own Claude or ChatGPT. It's a second connector, next to the main Superpractice one.

The Clio server URL is:

https://app.superpractice.com/api/mcp/clio

You'll also find it on the Clio assistant card and in Settings > MCP Server.

Claude (web and desktop)

In Claude, open Settings > Connectors > Add custom connector.
Name: Superpractice Clio. URL: the Clio server URL above.
Leave the options as Claude detects them: Authentication: Sign in now and OAuth client: Register automatically.
Click Add, then Connect. Sign in to Superpractice with your own account and approve.

On the approval screen, check that Organization shows your firm, then pick an access level:

Read only: look things up in Clio.
Read & write: also add and update records, when your firm allows it (see What the assistant may do).

Team members see Read & write only when your firm has turned on Team members can make changes in Clio on the Clio assistant card.

ChatGPT

In ChatGPT, open Settings > Apps & Connectors and turn on Developer mode.
Create a connector named Superpractice Clio with the Clio server URL, and choose OAuth.
Sign in to Superpractice with your own account, pick an access level and approve.

Access lasts 90 days, then your AI tool asks you to sign in again. You can disconnect any time in your AI tool, or revoke it in Settings > MCP Server.

What the assistant may do

Owners and admins set this on the Clio assistant card, under What the assistant may do in Clio. Changes apply on the next request and are recorded in your firm's consent log.

Switch	Default	On	Off
Read-only	On	The assistant can only read from Clio.	It can create and update matters, contacts, notes, tasks, calendar entries, documents, custom fields and time entries.
Allow deleting	Off	It may delete a record when asked. Needs Read-only off.	It can only create and update.
Allow billing changes	Off	It may change a bill's memo, due date or state (for example, approve a draft) and create trust requests. Needs Read-only off.	It never touches bills or trust.

When a switch blocks something, Claude says so in plain words, for example: "Nothing was sent to Clio: your firm's Clio assistant is set to Read-only in Superpractice."

Team members

Owners and admins can always connect with Read & write. Team members (not owners or admins) read only, unless an owner or admin turns on Team members can make changes in Clio on the Clio assistant card. It applies to the Clio connector only; the Superpractice connector has its own switch in Settings > MCP Server.

Off (the default): team members can look things up but not change anything.
On: team members can connect with Read & write. A team member who connected while it was off reconnects once and picks Read & write.
Turning it off takes effect on the next request. Their connection keeps working read-only.
Sending texts and emails always stays with owners and admins.

A team member only ever reaches what their own Clio login can reach in Clio.

Our recommended start

Read-only on for the first few days, then off once you're comfortable.
Allow deleting off.
Allow billing changes off until you need trust requests.
Team members can make changes in Clio off at first; turn it on when you're ready.

What your team can ask for

Look things up

Matters (status, dates, attorneys, balances, custom fields), contacts, documents and folders, tasks, calendar entries, notes, logged communications, time and expenses, and bills.
Conflict checks across contacts, matters and related parties.

Make changes (when allowed)

Create and update matters and contacts.
Add notes; create and update tasks, including marking them complete.
Create and move calendar entries, and invite colleagues by their calendar.
Create folders, upload text documents, and generate documents from your Clio templates.
Log time and expenses, set custom field values, and log calls or emails that already happened.

Billing (when allowed)

Change a bill's memo, due date or state, for example approving a draft.
Create a trust request. It's created unapproved, so someone at your firm approves it in Clio before the client sees it.

Clio doesn't let apps create bills or record payments, so the assistant can't.

How changes are recorded

In Clio: under the person who asked. For example, a matter's timeline reads "Noah Zazulia created Matter 00008", and a note's author is Noah.
In Superpractice: every call (reads and changes) writes a row to your firm's activity log with who asked, the tool and whether it worked. Only record ids and counts are logged, never client content.
Time entries go on the asker's own timesheet at their Clio rate.

Good to know

Time zones. Clio shows times in each person's Clio time zone. Set yours in Clio under Settings > Profile, or a 2pm meeting may show at 11am.
New matters are visible to everyone. Clio gives a new matter the "Everyone" permission by default. If your firm restricts some matters, adjust it in Clio after creating.
Claude doesn't delete records. Even with Allow deleting on, Claude may decline to permanently delete and ask you to do it in Clio. That's Claude's own safeguard for records that can't be restored.
New Clio matters flow into Superpractice. If you also use the Clio integration, a matter created through the assistant arrives in Superpractice within seconds, or waits in Matters > Needs review if its client already has a linked matter.
Hourly rates come from Clio. A time entry with no rate means the person or matter has no rate in Clio.
US Clio accounts (app.clio.com) only for now. Tell us if your firm is on Clio in Canada, the EU or Australia.

Troubleshooting

Nothing happens when you click Connect in Claude. Your browser blocked the sign-in window. In Chrome, open claude.ai's site settings (the icon at the left of the address bar), set Pop-ups and redirects to Allow, reload and click Connect again. In Safari: Safari > Settings for claude.ai > Pop-up Windows > Allow. Or connect from the Claude desktop app, which opens your browser instead.
Claude says "Account mismatch". Your browser is signed in to a different Claude account than the Claude desktop app. Sign in to claude.ai with the same account as the app, then connect again. This is Claude's check, not Superpractice's.
Clio says "User account not found" or "no active license". That Clio login has no active user in your firm's Clio account. Add the person in Clio under Settings > Manage Users and have them accept the invitation.
"That Clio login belongs to a different Clio account." You signed in to Clio with a login from another firm's account. Sign out of Clio and use your login at your firm.
"You haven't signed in to Clio with your own login yet." Do Step 3.
"Nothing was sent to Clio: your firm's Clio assistant is set to Read-only." An owner or admin turns off Read-only on the Clio assistant card.
"Your firm has turned off changes by team members." An owner or admin turns on Team members can make changes in Clio on the Clio assistant card. If you connected while it was off, reconnect and choose Read & write.
"This connection is read-only." You approved Read only when connecting. Disconnect the connector in your AI tool, connect again and pick Read & write.
Claude says a tool isn't found, or keeps asking to authenticate. Disconnect and reconnect the Superpractice Clio connector in your AI tool.
"Clio rejected the request: …" Clio refused the change and gives the reason after the colon, for example a missing field. Fix it in the request, or make the change in Clio.
"Clio has no record with that id." Looking up one matter or contact needs Clio's own numeric id, not the matter's display number or a Superpractice id. Ask the assistant to find the matter or search for the contact first, then open it from the result.
The approval screen shows the wrong organization. You're signed in to Superpractice as someone else. Sign out, sign in with your own account and connect again.

Disconnecting

One person: on the Clio assistant card, Disconnect my login. Their Clio sign-in is revoked; everyone else keeps working.
The whole firm: an owner or admin clicks Disconnect on the card. Everyone's Clio logins are revoked and the app's keys are removed from Superpractice. Nothing in Clio changes.
From Clio: remove the app in the Developer Portal, or a person revokes it in Clio under Settings > Apps.
Just the AI tool: remove the connector in Claude or ChatGPT, or revoke it in Settings > MCP Server.

Security

Your firm's App Key, App Secret and every person's Clio sign-in are encrypted (AES-256) before they're saved and never shown again; Settings shows only the last 4 characters of the App Key. Only Superpractice's servers can read them.
If the Clio assistant and the Clio card use separate Clio apps, each app's keys are stored separately. If they share one, the keys are copied between them on our servers, never through your browser.
Every request runs on the asker's own Clio login and is checked against your firm's switches before anything reaches Clio.
Superpractice staff can't connect or disconnect the Clio assistant, or turn on changes, deleting or billing, on your behalf, even when helping in your account.
Superpractice never uses your firm's Clio data to train AI models. Clio data your AI tool reads goes to that tool's provider under your plan with them; check its data and training settings.