Clio Manage MCP connector
The Clio Manage connector lets Claude, ChatGPT, Cursor and the Elaichi Agent read and update time entries, activity rates, bank accounts and bank transactions in Clio Manage, with each person signed in as themselves and every call logged.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Clio Manage to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Clio Manage once
-
Open Connections, choose Add connection, and pick Clio Manage.
-
Optionally set Share with to give a team access, then press Connect.
-
Supply your own Clio Manage app, then approve. Clio Manage needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Clio Manage MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Clio Manage MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Clio Manage MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Clio Manage to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Clio Manage through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Attorneys
Log the time right after the call
Tell the agent what you just did and for which matter, and a time entry with the right rate lands in Clio Manage before you open the next file.
-
Paralegals
Tidy time entries before the billing run
Pull up every entry for a matter, fix the descriptions and durations that are off, and remove the duplicates without clicking through each one.
-
Billing
Check rates before invoices go out
Ask which activity rates apply to a client or a timekeeper and update the ones that changed with the new engagement letter.
-
Accounting
Review bank transactions without leaving your chat
List yesterday's transactions on the trust and operating accounts, record the ones that are missing, and spot anything that does not match the bank statement.
-
Office management
Keep activity descriptions consistent across the firm
See every activity description in use, rename the ones people keep typing differently, and add the standard ones a new practice group needs.
-
Partners
See where payments were allocated
Ask how a payment was allocated across bills and matters and get the answer from live Clio Manage records rather than a forwarded screenshot.
Try asking
- “Log 0.5 hours on the Henderson matter for today's client call”
- “Show my time entries from this week that are still unbilled”
- “Which bank transactions posted to the trust account yesterday?”
Compare
Elaichi vs Zapier MCP vs Composio for Clio Manage
All three can connect Clio Manage to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Clio Manage tools | Allow or restrict single Clio Manage tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Clio Manage call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
AI tools
Clio Manage tools for your AI agents
304 tools are ready to call through Elaichi's MCP endpoint the moment you connect Clio Manage, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Showing 264 of 304 Clio Manage tools here. Connect Clio Manage and call search_tools or tools/list over the MCP endpoint for the complete set.
See it in Elaichi
What connecting Clio Manage gets you
6 screens from the product, each doing one job for your Clio Manage account.
The agent
Ask about your time entries in plain language.
Get answers from live Clio Manage activities, rates and bank transactions, no reports to run.
- activities
- activity rates
- bank accounts
- bank transactions
Ask Elaichi to work across your apps.
Log 0.5 hours on the Henderson matter for today's client call
Show my time entries from this week that are still unbilled
Which bank transactions posted to the trust account yesterday?
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint connects Clio Manage to every client.
Claude, ChatGPT and Cursor reach Clio Manage through one org endpoint, no SDK, no shared API key.
Copy the endpoint
Tool catalog
304 Clio Manage tools, no code to write.
Activities, activity rates, allocations, bank accounts and bank transactions, covered out of the box.
- List all Clio Manage activities
- Create a Clio Manage activity
- Get single Clio Manage activity by ID
- Update a Clio Manage activity by ID
Toolboxes
Every team gets its own Clio Manage toolbox.
Attorneys get time entries, accounting gets bank transactions, each team sees only its toolbox.
- Attorneys
- Paralegals
- Billing
- Accounting
Shared connections
Share Clio Manage without sharing a password.
One person connects Clio Manage, teams work through it, nobody else sees a credential.
- Litigation
- Family law
- Billing
- Accounting
Audit log
Every Clio Manage call is on the record.
Who changed which time entry or bank transaction, and when, in an append-only log.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
Unbilled time gets chased on a schedule.
Activities are fetched, grouped by matter, drafted into a digest, approved, then posted to Clio Manage.
Clio Manage digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch activities
Clio Manage
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Clio Manage
Queued
Collections and dashboards
Clio Manage health, computed without a model.
Activities logged, rates in use and transactions by team, refreshed on a schedule, nobody has to ask.
Clio Manage health
Refreshed 4 minutes ago · every 15 minutes · from the activities collection
Activities
1,284 ↓ 12%
Activity rates
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Activities created
Last 14 days
By team
Share of activity
Litigation 34%
Family law 27%
Billing 21%
Accounting 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Clio Manage to Claude?
Connect Clio Manage in Elaichi first. Clio Manage asks your firm to register an OAuth application inside Clio Manage, so one administrator brings that client ID and secret once, and after that everyone else simply signs in with their own Clio Manage login. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude signs in through Elaichi and Clio Manage is ready to use.
Does Clio Manage work with ChatGPT and Cursor as well as Claude?
Yes. Once Clio Manage is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Clio Manage once and every client picks it up.
What can an AI agent actually do with my Clio Manage data?
It can log, look up, correct and remove time entries and expenses in Clio Manage, check and change activity rates, keep activity descriptions tidy, and review allocations. It can also list your bank accounts and record or review bank transactions. Short, concrete asks such as "log 0.3 hours on the Patel matter for today's call" work better than long paragraphs.
Does connecting Clio Manage give the AI access to every matter?
No. The AI works inside the Clio Manage access of the person who signed in, so a paralegal who cannot see a matter in Clio Manage cannot see it through the agent either. Elaichi can narrow that access further for a team or a role, and it never widens it beyond what Clio Manage already allows.
Can I stop an agent from deleting or changing things in Clio Manage?
Yes. Restrictions in Elaichi work per action, so you can allow reading time entries and bank transactions while blocking deletes or updates. A restricted action is left out of the tool list the AI client sees, so it cannot be called no matter how the prompt is worded.
What happens to a Clio Manage connection when someone leaves?
Offboarding that person in Elaichi ends their access to Clio Manage through every AI client at once. A connection they shared with the team keeps working for everyone else. If you want Clio Manage gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client.
Does the Clio Manage MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Clio Manage is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Clio Manage?
Yes. Both let Claude, ChatGPT or Cursor use Clio Manage. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Clio Manage call.
How is Elaichi different from Composio for Clio Manage?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Clio Manage: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Clio Manage in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.