Clio MCP server Let your AI agent keep your Clio matters moving.

ToolWhat it doesAccess

• search_matters Matters of your firm with status, client and responsible attorney. read

  Returns matters one page at a time, newest first. status is open, pending or closed, the three statuses Clio uses; with no status every matter comes back. query matches the matter number and the description. What you see follows your Clio role and permissions. Use id as matter_id in the other tools.

  MCP callclio_read → search_matters

  REST endpointGET https://cotlet.dev/api/v1/clio/matters/search

  Parameters

  Parameters: search_matters

  Name	Type	Description
  query string	string	Text to find in the matter number or description.
  status enum	enum	open, pending or closed. Default: all.
  client_name string	string	Only matters of the client with this name.
  cursor string	string	Next page cursor from the previous call.

  Example response

  {
    "matters": [
      {
        "id": 1042871,
        "display_number": "00112-Hartley",
        "description": "Lease dispute",
        "status": "open",
        "client": "Hartley Properties",
        "responsible_attorney": "Dana Cole"
      },
      {
        "id": 1042890,
        "display_number": "00115-Ortega",
        "description": "Estate planning",
        "status": "pending",
        "client": "Maria Ortega",
        "responsible_attorney": "Dana Cole"
      }
    ],
    "next_cursor": null
  }

• get_matter One matter with its status, dates, practice area and the people on it. read

  Returns the matter as Clio shows it: status, open date, practice area, responsible attorney, the client and the related contacts with their roles. A matter you have no permission to see returns APP_PERMISSION_DENIED.

  MCP callclio_read → get_matter

  REST endpointGET https://cotlet.dev/api/v1/clio/matters/{matter_id}

  Parameters

  Parameters: get_matter

  Name	Type	Description
  matter_id integer required	integer	Matter ID from search_matters.

  Example input

  {
    "matter_id": 1
  }

  Example response

  {
    "id": 1042871,
    "display_number": "00112-Hartley",
    "description": "Lease dispute",
    "status": "open",
    "open_date": "2026-09-02",
    "practice_area": "Real estate",
    "responsible_attorney": "Dana Cole",
    "client": "Hartley Properties",
    "related_contacts": [
      {
        "name": "Gordon Pike",
        "role": "Opposing counsel"
      }
    ]
  }

• search_contacts People and companies in your Clio contacts. read

  Returns contacts matching the text, one page at a time, with type (person or company), email and phone as stored in Clio. Use it to find a client before you look for their matters.

  MCP callclio_read → search_contacts

  REST endpointGET https://cotlet.dev/api/v1/clio/contacts/search

  Parameters

  Parameters: search_contacts

  Name	Type	Description
  query string required	string	Name, email or phone to look for.
  cursor string	string	Next page cursor from the previous call.

  Example input

  {
    "query": "query"
  }

  Example response

  {
    "contacts": [
      {
        "id": 558120,
        "name": "Maria Ortega",
        "type": "person",
        "email": "maria@example.com",
        "phone": "+1 555 0142"
      }
    ],
    "next_cursor": null
  }

• update_matter_status Sets a matter to open, pending or closed. writeasks first

  Changes the status of one matter. open means the matter is active, pending means it was created but not yet opened, closed means it is finished. Clio records the open, pending or close date when the status changes. Returns the matter. By default you confirm each call; you can switch that off for this tool.

  MCP callclio_write → update_matter_status

  REST endpointPATCH https://cotlet.dev/api/v1/clio/matters/{matter_id}/status

  Parameters

  Parameters: update_matter_status

  Name	Type	Description
  matter_id integer required	integer	Matter ID from search_matters.
  status enum required	enum	open, pending or closed.

  Example input

  {
    "matter_id": 1,
    "status": "open"
  }

  Example response

  {
    "id": 1042890,
    "display_number": "00115-Ortega",
    "status": "open",
    "open_date": "2026-11-05"
  }

ToolWhat it doesAccess

• list_time_entries Time entries of a matter or a person, newest first. read

  Returns time entries with date, hours, description and the person who logged them. Filter by matter, person and date range. Hours can be hidden for your role, and then they come back empty.

  MCP callclio_read → list_time_entries

  REST endpointGET https://cotlet.dev/api/v1/clio/time-entries

  Parameters

  Parameters: list_time_entries

  Name	Type	Description
  matter_id integer	integer	Only entries on this matter.
  since date	date	Only entries on or after this date.
  until date	date	Only entries on or before this date.
  cursor string	string	Next page cursor from the previous call.

  Example response

  {
    "time_entries": [
      {
        "id": 7730412,
        "matter_id": 1042871,
        "date": "2026-11-04",
        "hours": 1.5,
        "description": "Review lease and draft reply",
        "user": "Dana Cole"
      },
      {
        "id": 7730398,
        "matter_id": 1042871,
        "date": "2026-11-03",
        "hours": 0.5,
        "description": "",
        "user": "Sam Reyes"
      }
    ],
    "next_cursor": null
  }

• list_bills Bills of a matter or client with date and total. read

  Returns bills newest first with issue date, the matter, the client and the total as Clio shows it. Use it to find the date of the last bill before you list the time since then. It only reads: generating a bill stays in Clio.

  MCP callclio_read → list_bills

  REST endpointGET https://cotlet.dev/api/v1/clio/bills

  Parameters

  Parameters: list_bills

  Name	Type	Description
  matter_id integer	integer	Only bills of this matter.
  cursor string	string	Next page cursor from the previous call.

  Example response

  {
    "bills": [
      {
        "id": 4410,
        "matter_id": 1042871,
        "client": "Hartley Properties",
        "issued_at": "2026-10-31",
        "total": 2850,
        "currency": "USD"
      }
    ],
    "next_cursor": null
  }

• create_time_entry Logs time on a matter. writeasks first

  Creates a time entry on the matter with the date, the hours and a description, for the signed-in person. It shows up in the matter's Activities and can go on the next bill to the client. Returns the new entry. By default you confirm each call; you can switch that off for this tool.

  MCP callclio_write → create_time_entry

  REST endpointPOST https://cotlet.dev/api/v1/clio/matters/{matter_id}/time-entries

  Parameters

  Parameters: create_time_entry

  Name	Type	Description
  matter_id integer required	integer	Matter ID from search_matters.
  date date required	date	Day the work was done.
  hours number required	number	Time spent, in hours, for example 1.5.
  description string required	string	What was done, as it will read on the bill.

  Example input

  {
    "matter_id": 1042871,
    "date": "2026-11-05",
    "hours": 1.5,
    "description": "Call with opposing counsel"
  }

  Example response

  {
    "id": 7730455,
    "matter_id": 1042871,
    "date": "2026-11-05",
    "hours": 1.5,
    "description": "Call with opposing counsel",
    "user": "Dana Cole"
  }

ToolWhat it doesAccess

• list_tasks Tasks with due date, assignee and matter. read

  Returns tasks one page at a time, soonest due first. Filter by matter, assignee or due date to find what is overdue. A task shows on its matter and on the Calendar on its due date.

  MCP callclio_read → list_tasks

  REST endpointGET https://cotlet.dev/api/v1/clio/tasks

  Parameters

  Parameters: list_tasks

  Name	Type	Description
  matter_id integer	integer	Only tasks on this matter.
  assignee string	string	Name of the person the task is assigned to.
  due_before date	date	Only tasks due on or before this date.
  complete boolean	boolean	true for finished tasks, false for open ones. Default: all.
  cursor string	string	Next page cursor from the previous call.

  Example response

  {
    "tasks": [
      {
        "id": 330981,
        "name": "Send engagement letter",
        "matter_id": 1042890,
        "assignee": "Dana Cole",
        "due_date": "2026-11-02",
        "complete": false
      },
      {
        "id": 330990,
        "name": "Collect ID copies",
        "matter_id": 1042890,
        "assignee": "Sam Reyes",
        "due_date": "2026-11-09",
        "complete": false
      }
    ],
    "next_cursor": null
  }

• create_task Adds a task, with an assignee and a due date, to a matter. writeasks first

  Creates a task with a name and the person it is assigned to, the two things Clio requires. A due date and a matter are optional. The assignee sees the task in Clio. Returns the new task. By default you confirm each call; you can switch that off for this tool.

  MCP callclio_write → create_task

  REST endpointPOST https://cotlet.dev/api/v1/clio/tasks

  Parameters

  Parameters: create_task

  Name	Type	Description
  name string required	string	Task name.
  assignee string required	string	Name of the person the task is assigned to.
  matter_id integer	integer	Matter the task belongs to.
  due_date date	date	Day the task is due.

  Example input

  {
    "name": "Jane Doe",
    "assignee": "assignee"
  }

  Example response

  {
    "id": 331004,
    "name": "Collect ID copies",
    "matter_id": 1042890,
    "assignee": "Sam Reyes",
    "due_date": "2026-11-09",
    "complete": false
  }

• complete_task Marks a task as complete. writeasks first

  Marks one task complete, as the person signed in. Returns the task with its new state. A task is reopened in Clio, not with this tool. By default you confirm each call; you can switch that off for this tool.

  MCP callclio_write → complete_task

  REST endpointPOST https://cotlet.dev/api/v1/clio/tasks/{task_id}/complete

  Parameters

  Parameters: complete_task

  Name	Type	Description
  task_id integer required	integer	Task ID from list_tasks.

  Example input

  {
    "task_id": 1
  }

  Example response

  {
    "id": 330981,
    "name": "Send engagement letter",
    "matter_id": 1042890,
    "assignee": "Dana Cole",
    "due_date": "2026-11-02",
    "complete": true
  }

• create_matter_note Adds a note to a matter. writeasks first

  Adds a note with a subject and text to the matter, written by the person signed in. It shows on the matter for everyone with access to it. Returns the new note. By default you confirm each call; you can switch that off for this tool.

  MCP callclio_write → create_matter_note

  REST endpointPOST https://cotlet.dev/api/v1/clio/matters/{matter_id}/note

  Parameters

  Parameters: create_matter_note

  Name	Type	Description
  matter_id integer required	integer	Matter ID from search_matters.
  subject string required	string	Short title of the note.
  body string required	string	Text of the note.

  Example input

  {
    "matter_id": 1,
    "subject": "subject",
    "body": "body"
  }

  Example response

  {
    "id": 66120,
    "matter_id": 1042890,
    "subject": "First meeting",
    "created_at": "2026-11-05T10:12:00Z"
  }

• list_calendar_entries Calendar entries in a date range, with matter and location. read

  Returns calendar entries starting inside the range, earliest first, with summary, start, end, location and the matter they belong to.

  MCP callclio_read → list_calendar_entries

  REST endpointGET https://cotlet.dev/api/v1/clio/calendar-entries

  Parameters

  Parameters: list_calendar_entries

  Name	Type	Description
  from date required	date	First day of the range.
  to date required	date	Last day of the range.
  matter_id integer	integer	Only entries on this matter.
  cursor string	string	Next page cursor from the previous call.

  Example input

  {
    "from": "2026-10-01",
    "to": "2026-10-01"
  }

  Example response

  {
    "calendar_entries": [
      {
        "id": 90412,
        "summary": "Filing deadline",
        "start_at": "2026-12-12T09:00:00",
        "end_at": "2026-12-12T09:30:00",
        "matter_id": 1042871,
        "location": ""
      }
    ],
    "next_cursor": null
  }

• create_calendar_entry Adds a calendar entry, optionally on a matter. writeasks first

  Creates a calendar entry with a summary, a start and an end, and links it to a matter when you pass one. Attendees you add see it in their Clio calendar. Returns the new entry. By default you confirm each call; you can switch that off for this tool.

  MCP callclio_write → create_calendar_entry

  REST endpointPOST https://cotlet.dev/api/v1/clio/calendar-entries

  Parameters

  Parameters: create_calendar_entry

  Name	Type	Description
  summary string required	string	Title of the entry.
  start_at datetime required	datetime	Start, for example 2026-12-12T09:00:00.
  end_at datetime required	datetime	End, same format as start_at.
  matter_id integer	integer	Matter the entry belongs to.
  location string	string	Where it takes place.

  Example input

  {
    "summary": "summary",
    "start_at": "2026-10-01T09:00:00Z",
    "end_at": "2026-10-01T09:00:00Z"
  }

  Example response

  {
    "id": 90431,
    "summary": "Filing deadline",
    "start_at": "2026-12-12T09:00:00",
    "end_at": "2026-12-12T09:30:00",
    "matter_id": 1042871
  }