Clio Manage Canada integration
Clio Manage is practice-management software for law firms; this integration targets accounts hosted in the Clio Canada region (ca.app.clio.com), which hold their own data and need their own developer app. An agent can list, read, create, update and delete matters, contacts, time entries and expenses (activities), tasks, calendar entries, notes, communications, reminders and webhooks, and read bills, documents, folders, custom fields, practice areas, users and billing balances. Trust accounting, payments, bill editing, document upload and download, reports, court rules and the other admin settings are not exposed. Authentication is OAuth 2.0 with a Clio Canada region developer app (its permissions are chosen on the app, not as scopes); the access token is sent as Authorization: Bearer.
Say what should happen.
The workflow builds itself.
What you can do with Clio Manage Canada
Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.
Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.
Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.
Calendar entry, 5 operations
create_calendar_entryCreate calendar entryPOSTAgents: ask firstCreate a calendar entry from the data object. Returns the new record with its id.delete_calendar_entryDelete calendar entryDELETEAgents: ask firstPermanently delete a calendar entry by id. Returns no content.get_calendar_entryGet calendar entryGETAgents: ask firstGet one calendar entry by id, with its main fields and linked records. Can return client personal data.list_calendar_entriesList calendar entriesGETAgents: ask firstList calendar entries, with filters and paging (limit up to 200, then pass meta.paging.next as page_token). Each row carries its main fields and linked records. Can return client personal data.update_calendar_entryUpdate calendar entryPATCHAgents: ask firstUpdate a calendar entry: send only the data fields to change; the others keep their value. Returns the updated record.
Communication, 5 operations
create_communicationCreate communicationPOSTAgents: ask firstCreate a communication (logged email or phone call) from the data object. Returns the new record with its id.delete_communicationDelete communicationDELETEAgents: ask firstPermanently delete a communication (logged email or phone call) by id. Returns no content.get_communicationGet communicationGETAgents: ask firstGet one communication (logged email or phone call) by id, with its main fields and linked records. Can return client personal data.list_communicationsList communicationsGETAgents: ask firstList communications, with filters and paging (limit up to 200, then pass meta.paging.next as page_token). Each row carries its main fields and linked records. Can return client personal data.update_communicationUpdate communicationPATCHAgents: ask firstUpdate a communication (logged email or phone call): send only the data fields to change; the others keep their value. Returns the updated record.
Contact, 5 operations
create_contactCreate contactPOSTAgents: ask firstCreate a contact (person or company) from the data object. Returns the new record with its id.delete_contactDelete contactDELETEAgents: ask firstPermanently delete a contact (person or company) by id. Returns no content.get_contactGet contactGETAgents: ask firstGet one contact (person or company) by id, with its main fields and linked records. Can return client personal data.list_contactsList contactsGETAgents: ask firstList contacts, with filters and paging (limit up to 200, then pass meta.paging.next as page_token). Each row carries its main fields and linked records. Can return client personal data.update_contactUpdate contactPATCHAgents: ask firstUpdate a contact (person or company): send only the data fields to change; the others keep their value. Returns the updated record.
Matter, 5 operations
create_matterCreate matterPOSTAgents: ask firstCreate a matter from the data object. Returns the new record with its id.delete_matterDelete matterDELETEAgents: ask firstPermanently delete a matter by id. Returns no content.get_matterGet matterGETAgents: ask firstGet one matter by id, with its main fields and linked records. Can return client personal data.list_mattersList mattersGETAgents: ask firstList matters, with filters and paging (limit up to 200, then pass meta.paging.next as page_token). Each row carries its main fields and linked records. Can return client personal data.update_matterUpdate matterPATCHAgents: ask firstUpdate a matter: send only the data fields to change; the others keep their value. Returns the updated record. Set reset_matter_number for a change to take effect on display_number.
Note, 5 operations
create_noteCreate notePOSTAgents: ask firstCreate a note from the data object. Returns the new record with its id.delete_noteDelete noteDELETEAgents: ask firstPermanently delete a note by id. Returns no content.get_noteGet noteGETAgents: ask firstGet one note by id, with its main fields and linked records. Can return client personal data.list_notesList notesGETAgents: ask firstList notes, with filters and paging (limit up to 200, then pass meta.paging.next as page_token). Each row carries its main fields and linked records. Can return client personal data.update_noteUpdate notePATCHAgents: ask firstUpdate a note: send only the data fields to change; the others keep their value. Returns the updated record.
Task, 5 operations
create_taskCreate taskPOSTAgents: ask firstCreate a task from the data object. Returns the new record with its id. Assign it to up to 10 firm users (assignees) or to one contact (assignee), never both.delete_taskDelete taskDELETEAgents: ask firstPermanently delete a task by id. Returns no content.get_taskGet taskGETAgents: ask firstGet one task by id, with its main fields and linked records. Can return client personal data.list_tasksList tasksGETAgents: ask firstList tasks, with filters and paging (limit up to 200, then pass meta.paging.next as page_token). Each row carries its main fields and linked records. Can return client personal data.update_taskUpdate taskPATCHAgents: ask firstUpdate a task: send only the data fields to change; the others keep their value. Returns the updated record. assignees replaces the whole set.
Time entry or expense, 5 operations
create_activityCreate activityPOSTAgents: ask firstCreate a time entry or expense (activity) from the data object. Returns the new record with its id. type and date drive billing; on a LEDES matter a billable entry needs UTBMS codes.delete_activityDelete activityDELETEAgents: ask firstPermanently delete a time entry or expense (activity) by id. Returns no content.get_activityGet activityGETAgents: ask firstGet one time entry or expense (activity) by id, with its main fields and linked records. Can return client personal data.list_activitiesList activitiesGETAgents: ask firstList activities, with filters and paging (limit up to 200, then pass meta.paging.next as page_token). Each row carries its main fields and linked records. Can return client personal data.update_activityUpdate activityPATCHAgents: ask firstUpdate a time entry or expense (activity): send only the data fields to change; the others keep their value. Returns the updated record. On a LEDES matter a billable entry needs UTBMS codes.
Webhook, 5 operations
create_webhookCreate webhookPOSTAgents: ask firstSubscribe an https url to created, updated or deleted events of one model. Starts pending: Clio sends the signing secret to the url in an X-Hook-Secret header, which the url must echo back. Returns the webhook id.delete_webhookDelete webhookDELETEAgents: ask firstPermanently delete a webhook by id. Returns no content.get_webhookGet webhookGETAgents: ask firstGet one webhook by id, with its main fields and linked records.list_webhooksList webhooksGETAgents: ask firstList webhooks, with filters and paging (limit up to 200, then pass meta.paging.next as page_token). Each row carries its main fields and linked records.update_webhookUpdate webhookPATCHAgents: ask firstUpdate a webhook: send only the data fields to change; the others keep their value. Returns the updated record.
Firm user, 3 operations
get_current_userGet current userGETAgents: ask firstGet the Clio user the connection acts as (id, name, email, roles). Use it to check the connection.get_userGet userGETAgents: ask firstGet one firm user by id, with its main fields and linked records.list_usersList usersGETAgents: ask firstList users, with filters and paging (limit up to 200, then pass meta.paging.next as page_token). Each row carries its main fields and linked records.
Folder, 3 operations
create_folderCreate folderPOSTAgents: ask firstCreate a folder from the data object. Returns the new record with its id.get_folderGet folderGETAgents: ask firstGet one folder by id, with its main fields and linked records.list_foldersList foldersGETAgents: ask firstList folders, with filters and paging (limit up to 200, then pass meta.paging.next as page_token). Each row carries its main fields and linked records.
Relationship, 3 operations
create_relationshipCreate relationshipPOSTAgents: ask firstCreate a relationship (a contact related to a matter) from the data object. Returns the new record with its id.delete_relationshipDelete relationshipDELETEAgents: ask firstPermanently delete a relationship (a contact related to a matter) by id. Returns no content.list_relationshipsList relationshipsGETAgents: ask firstList relationships, with filters and paging (limit up to 200, then pass meta.paging.next as page_token). Each row carries its main fields and linked records.
Reminder, 3 operations
create_reminderCreate reminderPOSTAgents: ask firstCreate a reminder from the data object. Returns the new record with its id.delete_reminderDelete reminderDELETEAgents: ask firstPermanently delete a reminder by id. Returns no content.list_remindersList remindersGETAgents: ask firstList reminders, with filters and paging (limit up to 200, then pass meta.paging.next as page_token). Each row carries its main fields and linked records.
Activity description, 2 operations
get_activity_descriptionGet activity descriptionGETAgents: ask firstGet one activity description (billing description and rate) by id, with its main fields and linked records.list_activity_descriptionsList activity descriptionsGETAgents: ask firstList activity descriptions, with filters and paging (limit up to 200, then pass meta.paging.next as page_token). Each row carries its main fields and linked records.
Bill, 2 operations
get_billGet billGETAgents: ask firstGet one bill (invoice) by id, with its main fields and linked records. Can return client personal data.list_billsList billsGETAgents: ask firstList bills, with filters and paging (limit up to 200, then pass meta.paging.next as page_token). Each row carries its main fields and linked records. Can return client personal data.
Calendar, 2 operations
get_calendarGet calendarGETAgents: ask firstGet one calendar by id, with its main fields and linked records.list_calendarsList calendarsGETAgents: ask firstList calendars, with filters and paging (limit up to 200, then pass meta.paging.next as page_token). Each row carries its main fields and linked records.
Custom field, 2 operations
get_custom_fieldGet custom fieldGETAgents: ask firstGet one custom field by id, with its main fields and linked records.list_custom_fieldsList custom fieldsGETAgents: ask firstList custom fields, with filters and paging (limit up to 200, then pass meta.paging.next as page_token). Each row carries its main fields and linked records.
Document, 2 operations
get_documentGet documentGETAgents: ask firstGet one document by id, with its main fields and linked records. Can return client personal data.list_documentsList documentsGETAgents: ask firstList documents, with filters and paging (limit up to 200, then pass meta.paging.next as page_token). Each row carries its main fields and linked records. Can return client personal data.
Practice area, 2 operations
get_practice_areaGet practice areaGETAgents: ask firstGet one practice area by id, with its main fields and linked records.list_practice_areasList practice areasGETAgents: ask firstList practice areas, with filters and paging (limit up to 200, then pass meta.paging.next as page_token). Each row carries its main fields and linked records.
Task template list, 2 operations
copy_task_template_listCopy task template listPOSTAgents: ask firstCopy a task template list: creates a new task template list from an existing one (id from list_task_template_lists). Returns the new list with its id.list_task_template_listsList task template listsGETAgents: ask firstList task template lists, with filters and paging (limit up to 200, then pass meta.paging.next as page_token). Each row carries its main fields and linked records.
Activity rate, 1 operation
list_activity_ratesList activity ratesGETAgents: ask firstList activity rates, with filters and paging (limit up to 200, then pass meta.paging.next as page_token). Each row carries its main fields and linked records.
Bill line item, 1 operation
list_line_itemsList line itemsGETAgents: ask firstList line items, with filters and paging (limit up to 200, then pass meta.paging.next as page_token). Each row carries its main fields and linked records.
Billable matter, 1 operation
list_billable_mattersList billable mattersGETAgents: ask firstList billable matters, with filters and paging (limit up to 200, then pass meta.paging.next as page_token). Each row carries its main fields and linked records.
Custom field set, 1 operation
list_custom_field_setsList custom field setsGETAgents: ask firstList custom field sets, with filters and paging (limit up to 200, then pass meta.paging.next as page_token). Each row carries its main fields and linked records.
Document category, 1 operation
list_document_categoriesList document categoriesGETAgents: ask firstList document categories, with filters and paging (limit up to 200, then pass meta.paging.next as page_token). Each row carries its main fields and linked records.
Email address, 1 operation
list_contact_email_addressesList contact email addressesGETAgents: ask firstList email addresses, with filters and paging (limit up to 200, then pass meta.paging.next as page_token). Each row carries its main fields and linked records. Can return client personal data.
Expense category, 1 operation
list_expense_categoriesList expense categoriesGETAgents: ask firstList expense categories, with filters and paging (limit up to 200, then pass meta.paging.next as page_token). Each row carries its main fields and linked records.
Folder item, 1 operation
list_folder_contentsList folder contentsGETAgents: ask firstList the contents (documents and sub-folders) of a folder (parent_id), or of the top level. Cursor pagination only: pass meta.paging.next as page_token.
Group, 1 operation
list_groupsList groupsGETAgents: ask firstList groups, with filters and paging (limit up to 200, then pass meta.paging.next as page_token). Each row carries its main fields and linked records.
Matter client, 1 operation
get_matter_clientGet matter clientGETAgents: ask firstGet the client contact of one matter (matter_id from list_matters). Can return client personal data.
Matter contact, 1 operation
list_matter_contactsList matter contactsGETAgents: ask firstList the contacts of one matter (matter_id): its client and related contacts, with their relationship. Can return client personal data.
Matter stage, 1 operation
list_matter_stagesList matter stagesGETAgents: ask firstList matter stages, with filters and paging (limit up to 200, then pass meta.paging.next as page_token). Each row carries its main fields and linked records.
Outstanding client balance, 1 operation
list_outstanding_client_balancesList outstanding client balancesGETAgents: ask firstList outstanding client balances, with filters and paging (limit up to 200, then pass meta.paging.next as page_token). Each row carries its main fields and linked records. Can return client personal data.
Phone number, 1 operation
list_contact_phone_numbersList contact phone numbersGETAgents: ask firstList phone numbers, with filters and paging (limit up to 200, then pass meta.paging.next as page_token). Each row carries its main fields and linked records. Can return client personal data.
Related contact, 1 operation
list_matter_related_contactsList matter related contactsGETAgents: ask firstList the contacts related to one matter (matter_id), with their relationship description. Can return client personal data.
Task type, 1 operation
list_task_typesList task typesGETAgents: ask firstList task types, with filters and paging (limit up to 200, then pass meta.paging.next as page_token). Each row carries its main fields and linked records.
Use Clio Manage Canada from Claude Code, Cursor or Codex
Connect Clio Manage Canada in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Clio Manage Canada operations become tools the client can call, next to every other integration you connected.
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"
[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"{
"mcpServers": {
"livecontext": {
"type": "http",
"url": "https://livecontext.ai/mcp",
"headers": {
"X-API-Key": "YOUR_API_KEY"
}
}
}
}How to connect Clio Manage Canada
- Create your workspace
Sign up free. Nothing to install.
- Connect Clio Manage Canada once
Add your Clio Manage Canada connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
- Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.
Clio Manage Canada integration FAQ
What can you do with the Clio Manage Canada integration?
LiveContext exposes 82 operations on Clio Manage Canada, covering calendar entry, communication, contact and matter.
