Clio MCP by usefulapi

Each tool pairs a distinct resource with an action, and descriptions actively clarify overlaps (e.g. time entries are activities, notes vs. communications, get vs. list). Minor residual friction: an agent wanting to list time entries must know to use clio_list_activities, and clio_create_time_entry lives outside that family, which could cause occasional misselection.

All tools use a uniform clio_ verb_noun snake_case pattern (create/get/list/update), which is highly predictable. Small deviations: clio_log_communication uses 'log' where 'create' is used elsewhere, and clio_who_am_i is an idiom rather than verb_noun.

23 tools is on the heavy side of the 16-25 band, but the Clio domain legitimately spans many resources (matters, contacts, bills, tasks, calendar, documents, notes, activities, communications, users, custom fields). The surface is mostly read+create, so the count is arguably lean rather than bloated for what it covers.

Coverage is broad on reads and creates, but there is no update/delete for matters, contacts, calendar entries, notes, time entries or communications, no document upload, and no bill creation or payment — only tasks support update. An agent can handle core intake and reporting workflows but will hit dead ends on common lifecycle operations like closing a matter or correcting a time entry.