Integration

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.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Clio Manage Canada.Built from the 82 Clio Manage Canada tools below, on the connection you add once.

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.

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 entryPOSTCreate a calendar entry from the data object. Returns the new record with its id.
  • delete_calendar_entryDelete calendar entryDELETEPermanently delete a calendar entry by id. Returns no content.
  • get_calendar_entryGet calendar entryGETGet one calendar entry by id, with its main fields and linked records. Can return client personal data.
  • list_calendar_entriesList calendar entriesGETList 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 entryPATCHUpdate a calendar entry: send only the data fields to change; the others keep their value. Returns the updated record.

Communication, 5 operations

  • create_communicationCreate communicationPOSTCreate a communication (logged email or phone call) from the data object. Returns the new record with its id.
  • delete_communicationDelete communicationDELETEPermanently delete a communication (logged email or phone call) by id. Returns no content.
  • get_communicationGet communicationGETGet one communication (logged email or phone call) by id, with its main fields and linked records. Can return client personal data.
  • list_communicationsList communicationsGETList 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 communicationPATCHUpdate 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 contactPOSTCreate a contact (person or company) from the data object. Returns the new record with its id.
  • delete_contactDelete contactDELETEPermanently delete a contact (person or company) by id. Returns no content.
  • get_contactGet contactGETGet one contact (person or company) by id, with its main fields and linked records. Can return client personal data.
  • list_contactsList contactsGETList 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 contactPATCHUpdate 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 matterPOSTCreate a matter from the data object. Returns the new record with its id.
  • delete_matterDelete matterDELETEPermanently delete a matter by id. Returns no content.
  • get_matterGet matterGETGet one matter by id, with its main fields and linked records. Can return client personal data.
  • list_mattersList mattersGETList 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 matterPATCHUpdate 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 notePOSTCreate a note from the data object. Returns the new record with its id.
  • delete_noteDelete noteDELETEPermanently delete a note by id. Returns no content.
  • get_noteGet noteGETGet one note by id, with its main fields and linked records. Can return client personal data.
  • list_notesList notesGETList 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 notePATCHUpdate a note: send only the data fields to change; the others keep their value. Returns the updated record.

Task, 5 operations

  • create_taskCreate taskPOSTCreate 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 taskDELETEPermanently delete a task by id. Returns no content.
  • get_taskGet taskGETGet one task by id, with its main fields and linked records. Can return client personal data.
  • list_tasksList tasksGETList 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 taskPATCHUpdate 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 activityPOSTCreate 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 activityDELETEPermanently delete a time entry or expense (activity) by id. Returns no content.
  • get_activityGet activityGETGet one time entry or expense (activity) by id, with its main fields and linked records. Can return client personal data.
  • list_activitiesList activitiesGETList 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 activityPATCHUpdate 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 webhookPOSTSubscribe 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 webhookDELETEPermanently delete a webhook by id. Returns no content.
  • get_webhookGet webhookGETGet one webhook by id, with its main fields and linked records.
  • list_webhooksList webhooksGETList 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 webhookPATCHUpdate 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 userGETGet the Clio user the connection acts as (id, name, email, roles). Use it to check the connection.
  • get_userGet userGETGet one firm user by id, with its main fields and linked records.
  • list_usersList usersGETList 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 folderPOSTCreate a folder from the data object. Returns the new record with its id.
  • get_folderGet folderGETGet one folder by id, with its main fields and linked records.
  • list_foldersList foldersGETList 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 relationshipPOSTCreate a relationship (a contact related to a matter) from the data object. Returns the new record with its id.
  • delete_relationshipDelete relationshipDELETEPermanently delete a relationship (a contact related to a matter) by id. Returns no content.
  • list_relationshipsList relationshipsGETList 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 reminderPOSTCreate a reminder from the data object. Returns the new record with its id.
  • delete_reminderDelete reminderDELETEPermanently delete a reminder by id. Returns no content.
  • list_remindersList remindersGETList 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 descriptionGETGet one activity description (billing description and rate) by id, with its main fields and linked records.
  • list_activity_descriptionsList activity descriptionsGETList 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 billGETGet one bill (invoice) by id, with its main fields and linked records. Can return client personal data.
  • list_billsList billsGETList 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 calendarGETGet one calendar by id, with its main fields and linked records.
  • list_calendarsList calendarsGETList 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 fieldGETGet one custom field by id, with its main fields and linked records.
  • list_custom_fieldsList custom fieldsGETList 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 documentGETGet one document by id, with its main fields and linked records. Can return client personal data.
  • list_documentsList documentsGETList 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 areaGETGet one practice area by id, with its main fields and linked records.
  • list_practice_areasList practice areasGETList 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 listPOSTCopy 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 listsGETList 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 ratesGETList 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 itemsGETList 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 mattersGETList 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 setsGETList 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 categoriesGETList 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 addressesGETList 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 categoriesGETList 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 contentsGETList 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 groupsGETList 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 clientGETGet the client contact of one matter (matter_id from list_matters). Can return client personal data.

Matter contact, 1 operation

  • list_matter_contactsList matter contactsGETList 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 stagesGETList 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 balancesGETList 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 numbersGETList 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 contactsGETList 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 typesGETList 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 Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Clio Manage Canada

  1. Create your workspace

    Sign up free. Nothing to install.

  2. 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.

  3. 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.

Popular integrations

Browse the whole catalog