Clio MCP
Clio MCP: connect Claude or ChatGPT to Clio, and pick the right connector
There are four ways to put Clio inside Claude or ChatGPT: Clio's own connector, Zapier, an open-source server, or a firm brain. They differ on who signs in, what they can change, and whether they can see anything outside Clio.
Third-party details checked November 19, 2026 from Clio's Claude connector listing, Clio's help article, OpenAI's Clio plugin page, Zapier's Clio MCP page and the oktopeak/clio-mcp README. Vendors change these often; their pages win.
Written by FirmOps, a Vertana brand. We build law firms a firm brain that sits on the case system they already run, and Clio is the one we see most. The first one was built inside Conduit Law, a personal injury firm that runs on Clio, where staff use it every day. We do not sell Clio and Clio does not pay us. One of the four options below is ours, so read the table with that in mind.
What a Clio MCP does
MCP, the Model Context Protocol, is how Claude, ChatGPT and other AI apps call outside tools. A Clio MCP server turns Clio into a short list of tools: find a matter, read its notes and tasks, check a balance, add a task. Staff ask a question in plain English, the AI calls the tools, and the answer comes from the live record instead of something pasted into a chat. The longer explainer is what MCP means for a law firm.
Clio MCP options compared
| Option | Who runs it | What it reads and does | What it can change | What it sees |
|---|---|---|---|---|
| Clio connector for Claude | Clio (Themis Solutions Inc.), listed in Claude's connector directory as Anthropic verified | Requires a Clio Work license and the Claude desktop app; included with Clio Work at no extra cost. Legal research, analysis, first drafts, US court filings, and Clio Manage and Clio Grow records when the firm subscribes to those products. | Read and write. In Claude each tool starts at "Needs approval", so Claude asks before it calls the tool. That is a per-tool default the user can change, and Clio advises keeping approval on for anything that creates, updates or deletes records. | Clio only. |
| Zapier MCP for Clio | Zapier, hosted at mcp.zapier.com | Find matters, bills, contacts and users. | Create matters, tasks, time and expense entries, notes, folders, calendar entries, contacts and documents from templates. Update matters, tasks and contacts. | Clio plus whatever other Zapier apps you connect. |
| Open-source servers (example: oktopeak/clio-mcp) | The maintainer on GitHub. You run it yourself | 37 tools across matters, contacts, documents, tasks, calendar, time, billing, notes and users. | Twelve write tools. A READ_ONLY setting removes them. The README says the approval prompt belongs to the AI client, not the connector. | Clio only. You register your own Clio developer app. |
| A firm brain MCP (FirmOps) | FirmOps, hosted, per firm | Matters, contacts, notes, tasks, calendar, communications, the matter timeline, documents, bills, balances and trust balance, plus the firm's email, files and read-only call history. | Notes, tasks, calendar entries, expenses, custom fields, stage and practice area. Every write returns a preview first and runs only when a person confirms it. | Clio plus Gmail or Microsoft 365, documents, billing and phones. |
These are not really rivals. Clio's connector is the way to use Clio Work's research and drafting inside Claude. Zapier is quick if your firm already lives in Zapier. An open-source server is free if you are willing to run it. A firm brain is for the operations side: the follow-ups, status checks and handoffs that need Clio, email and the file together.
Six questions to ask before you connect Clio to an AI
Who signs in?
Each person should sign in as themselves, through OAuth, so the AI sees only what that person could see in Clio. A shared API key or one admin login means every question runs with the admin's access, and your log cannot tell who asked.
What can it change?
Reading a matter and changing one are different risks. Ask for the list of write tools by name. Then ask whether writes can be turned off for some staff, or off entirely while you trial it.
Who presses go?
An AI client that asks "allow this tool?" is not the same as a server that refuses to write until a person confirms the exact change. Look for a preview of the change and a second call that actually applies it.
Is there an audit log you can read?
You want one row per tool call: who, which tool, which matter, when, and whether it succeeded. When something looks wrong in Clio, the log is how you find out whether a person or the AI did it.
Can it see past Clio?
Most of a matter is not in Clio. The dec page is in Dropbox, the adjuster's last email is in Gmail, the client's voicemail is in the phone system. An MCP that only reads Clio answers half the question and sounds sure about it.
Who keeps it running?
Clio changes its API, tokens expire, and rate limits bite when several people ask at once. Someone has to watch for that. With a self-run server, that someone is you.
See it on a real matter
Watch Claude read a Clio matter, the email and the file at once
On a 15-minute demo we show the firm brain working on a sample firm, map your stack, and check that your systems have the APIs to build yours.
Book a 15-minute demoWhy Clio alone is half the file
A typical question at a PI firm: which open cases are ready for a demand? The matter and its stage are in Clio. The policy limits are on a dec page in the matter's Dropbox folder. The last word from the adjuster is in someone's Gmail. The medical bills are split between Clio and the folder.
A Clio-only connector can list the matters. It cannot tell you that the dec page in one folder is for the wrong policy, or that the adjuster asked for records last week and nobody answered. That is the work a firm brain is for: read across the systems, notice when they disagree, and draft the next step for a person to send. Our Clio guide covers where Clio's own AI stops, and Clio integrations covers which other systems are worth connecting.
How the FirmOps MCP handles Clio
The FirmOps MCP is a hosted server at https://mcp.firmops.io/mcp. A firm adds it once to Claude, ChatGPT or Cursor, and each person signs in as themselves. The sign-in decides which firm they reach.
- Reads. Find a matter, its details, custom fields, stage and practice area; contacts; notes, tasks, calendar entries, communications and the matter timeline; the documents folder; bills, outstanding balances and trust balance.
- Writes, after onboarding. Add a note, create or update a task, add a calendar entry, record an expense, update a custom field, the stage or the practice area. Writes are off during a trial.
- Preview, then confirm. Every write returns a preview of the change first. Nothing changes in Clio until the person confirms that preview, and each applied write is recorded once in the firm's audit log.
- No unsupervised sends. It drafts email; a person sends it. Call history is read-only. Live client calls stay with people.
Setup steps for each AI app, and the full tool list, are on the FirmOps MCP page.
What running a Clio MCP in production taught us
- Clio's rate limits are shared. Background jobs and staff questions draw on the same Clio allowance. When a sync job is busy, a question that normally takes seconds can wait. Staff questions should go to the front of the line.
- A timeout in the chat is not a failed tool. AI apps give up on a slow tool call after about a minute, while the server can still finish the work. Check the audit log before you retry, or you run the same job twice.
- Clio's API has its own habits. Some filters are ignored without an error, some fields cannot be expanded in one call, and a new document upload is not finished until a final step marks it uploaded. A connector has to handle that, not the person asking. More on the Clio API page.
- A short tool menu beats a long one. The AI picks the right tool more often when there are fewer, clearly named ones, and the firm can read the whole list in a minute.
See it on a real matter
Watch Claude read a Clio matter, the email and the file at once
On a 15-minute demo we show the firm brain working on a sample firm, map your stack, and check that your systems have the APIs to build yours.
Book a 15-minute demoRunning a firm on Clio
More on Clio from a firm that runs on it
Clio AI
Clio Work, Clio Manage AI and Vincent, and where a firm brain picks up.
Clio integrations
Which integrations matter by job, and the catch with each one.
Clio API in production
What the Clio API docs leave out, from a firm that writes to Clio every day.
Clio pricing
Clio plans, the published per-user price, and the costs around Clio.
Clio intake workflow
From signed and paid to a clean Clio matter, without retyping.
Clio consultant
When you need a Clio Certified Consultant, when you need a connected layer, and what to ask either.
Clio alternatives
Check whether the gap is Clio or the stack around it, then a fair short list.
Clio Grow vs Clio Manage
What each does, which plan includes Grow, and the handoff between them.
Clio vs MyCase
Plans, pricing, AI and what each lets you connect, side by side.
Clio vs PracticePanther
Plans, pricing, AI and API access, side by side.
Clio vs Smokeball
Plans, pricing, AI and API access, side by side.
Filevine vs Clio
Pricing, implementation, AI and API for personal injury firms.
Clio MCP questions
What is a Clio MCP server?
MCP (Model Context Protocol) is the standard way AI apps like Claude and ChatGPT call outside tools. A Clio MCP server is a connector that exposes Clio as a set of tools, such as find a matter, read its notes, or create a task, so the AI reads the live record instead of text someone pasted in.
Does Clio have an official MCP connector for Claude?
Yes. Clio announced its Claude connector on October 30, 2026, included with Clio Work at no additional cost. It needs a Clio Work license and the Claude desktop app, asks for read and write access, and reads Clio Manage and Clio Grow records when the firm subscribes to them. Each tool starts at "Needs approval" in Claude, a default each user can change. Accounts that sign in only through vLex single sign-on are not supported yet, and Clio says Vincent customers get support later. Checked November 19, 2026 on clio.com and help.clio.com.
Can I connect ChatGPT to Clio?
Yes. OpenAI lists an official Clio plugin for ChatGPT, built by Clio (Themis Solutions Inc.) with read and write access, for ChatGPT Work and Codex, and Clio publishes Clio for Codex. Clio's own help says regular ChatGPT chat has no Clio connection, so check which ChatGPT product your firm uses. Zapier MCP and a hosted firm brain also work as ChatGPT connectors; the FirmOps MCP uses the same server address in Claude, ChatGPT and Cursor. Checked November 19, 2026.
Is a free open-source Clio MCP good enough?
For one lawyer who is comfortable running software, it can be. You register a Clio developer app, keep the server running, and update it when Clio changes. For a firm with staff, the harder parts are per-person sign-in, a confirm step on writes, a log you can read, and someone who answers when it breaks.
Can an AI write back to Clio safely?
Yes, if the server stages the change and a person confirms it. On the FirmOps MCP every write returns a preview first, nothing changes in Clio until the person confirms that preview, and each applied write is recorded once in the firm's audit log.
What is the difference between Clio Work and a Clio MCP?
Clio Work is Clio's AI product for legal work: research, drafting and case strategy. Clio's Claude connector brings Clio Work into Claude. A firm brain MCP is about running the firm: it reads Clio alongside email, documents, billing and phones, and stages the follow-up work for a person to approve.
Do I need my own Clio API app?
Only for a server you run yourself. Open-source servers ask you to register a Clio developer app and keep its keys. A hosted connector, such as Clio's, Zapier's or FirmOps', handles the app, and you sign in with your Clio account. What we learned building on Clio's API is on our Clio API page.