Menu
Mattering Automations connector

A Clio Manage MCP that takes privileged data seriously

60 nodes across matters, contacts, time entries and timers, bills and receivables, Clio Payments, tasks, calendar, notes, communications, documents and firm reference data. Every read node ships with a well chosen fields value, because Clio returns only an id and an etag when you leave it out. Defaults on the most sensitive reads are deliberately narrow: a communication body, a calendar attendee list and a user billing rate are all reachable and none is returned unless you ask.

60 ready-made nodes One credential to connect Works with Claude, ChatGPT, and Matter

What the Clio Manage MCP connector does

The Clio Manage connector for Mattering Automations is 60 nodes on Clio Manage API v4, pinned to version 4.0.13. Matters, contacts and matter contacts cover the firm's files and address book. Activities, timers, activity descriptions and expense categories cover recorded time and expenses. Bills, bill line items, payment allocations, outstanding client balances, billable matters and Clio Payments cover the money. Tasks, calendar entries and calendars cover the diary. Notes, communications and documents cover the file itself. Practice areas, matter stages, custom field definitions and users cover the reference data everything else hangs off. Thirty five nodes read and twenty five act.

Every capability is a node on the Automations canvas, and every node speaks MCP, the open protocol for connecting AI assistants to tools. Claude, ChatGPT, and any MCP-capable assistant can use them, alongside Matter, the AI assistant built into the platform. So an agent can read a month of recorded time with Clio Manage: List Activities, draft the pre-billing narrative, and stop there while a person decides whether anything is invoiced.

The first thing to understand about this API is the fields parameter, and it is the reason most people conclude a Clio integration is broken when it is working perfectly. Clio returns a minimal representation by default: leave fields out of a request and, for most endpoints, the only attributes that come back are id and etag. HTTP 200, no error message, and nothing usable. Every one of the 50 nodes here that returns a Clio record carries fields as a configured value with an authored default, so a node you drop on the canvas and run without touching returns a sensible record rather than a bare id. That default also feeds every picker in the connector, which is why a matter picker shows display numbers rather than raw integers. You can widen it whenever you want more, and requesting a field name Clio does not recognise fails loudly with a 400 rather than quietly omitting it.

This connector reads material protected by attorney-client privilege, and the defaults are shaped around that rather than around convenience. A communication's body is the privileged communication itself, so the communications lister asks for the subject and not the body. A calendar entry's attendee list names clients and opposing parties, so the calendar lister leaves it out. A firm user's billing rate is a commercially sensitive number, so the users lister leaves that out too. Each of those is documented and each is one edit away from being returned. The habit worth building on top of that is to select the fields a workflow actually needs rather than forwarding a whole Clio object into a chat window, a spreadsheet or an AI step, because privilege can be waived by disclosure and nothing undoes that afterwards.

One region is connectable today, and it is worth reading before you plan anything. Clio runs four independent deployments, in the United States, the European Union, Canada and Australia, and a token issued against one is not valid against another. Region therefore lives on the credential rather than on a node. Clio goes further than that: it requires a separate Clio account and a separate Developer Application per region, with a different application id in each, so serving a European, Canadian or Australian firm means sibling OAuth providers that do not exist yet. The connect flow on this page produces a United States credential. We are not going to imply the connector is region-agnostic or promise a date it will not be.

Deletes are not one thing here and the connector does not pretend they are. Clio Manage: Delete Document moves a file to the trash, where it stays readable and is purged only after 30 days, which is a genuine undo. Clio Manage: Delete Or Void Bill is not a delete at all: Clio moves a Draft bill to Deleted and an Unpaid bill to Void, only when no payments have been recorded against it, and documents no way back out of either state. Deleting a matter, contact, activity, task, calendar entry or note is permanent, with no trash state and no restore endpoint documented anywhere in Clio's own API description. Every one of those six names its reversible alternative in the node itself, because closing a matter or completing a task usually does what somebody actually wanted.

Fetch wide rather than looping. Clio allows 50 requests per minute per access token at peak hours, raises it by a region-dependent amount off peak, and does not grant custom increases. That single number is why fields being first class matters operationally: one list call asking for the columns you need beats a list call followed by one read per row, and a naive walk over a mid-sized firm's matters exhausts the budget in under a minute. Index calls return up to 200 records and the connector does not auto-paginate, so an unbounded number of requests never hides behind one canvas step.

Two honest notes about getting started. Clio's review process is a distribution gate, not an access gate: any firm on a paid Clio plan can create a private application at the Clio developer portal and call its own data immediately, and Clio states plainly that private Clio Manage apps are not reviewed. The security questionnaire, the recorded demo and the listing form apply to publishing in Clio's App Directory, which is a different thing. Separately, this connector signs in with Clio rather than taking an API key, so it needs a Clio OAuth client provisioned on the Mattering side before the sign-in step can complete. That provisioning is ours to do, not yours. The node catalog on this page is the shipped catalog and does not change when it lands.

One connection, three surfaces

  • Visual automations. Drag Clio Manage nodes onto the canvas and wire them to triggers, conditions, and other apps.
  • AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
  • The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.

Every Clio Manage node, ready to drop on the canvas

60 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.

Read and query nodes 35

Clio Manage: Download Document

Get a download URL for a document's file. Clio answers this endpoint with a 303 See Other pointing at a short-lived signed URL rather than streaming the bytes, so this node deliberately does NOT follow the redirect: it returns the URL at data.download_url for a following HTTP node, a worker, or a file-handling step to fetch. Two things that follow from that: the URL grants access to a privileged document to anyone holding it, so do not persist it or send it anywhere the document itself should not go; and it expires, so fetch it promptly rather than storing it for later.

Clio Manage: Get Activity

Fetch one time entry or expense in full, including which bill it landed on and which billing code it used. Money and hours on time entries are subject to two firm settings. With Billing Rate Visibility set to Own or None, price and total are removed and redacted is set to true. With Activity Hours Visibility restricted, quantity, rounded_quantity, quantity_in_hours, rounded_quantity_in_hours, total and non_billable_total come back NULL and quantity_redacted is set to true. Summing a page that contains redacted rows produces a number that is wrong and looks right, so filter on those flags before aggregating.

Clio Manage: Get Bill

Fetch one invoice in full, including its totals, tax, the matters it covers, and available_state_transitions - the list of states Clio will actually accept next, which is what you should read before trying to approve or void a bill rather than guessing.

Clio Manage: Get Calendar Entry

Fetch one calendar entry in full, including attendees, recurrence rule and any linked video meeting. Field visibility on calendar entries is restricted to the event's owners, editors and viewers (API version 4.0.12), so a user outside that set sees a reduced record rather than an error.

Clio Manage: Get Contact

Fetch one contact in full, including every email address, phone number and postal address rather than only the primary of each, plus custom field values. The default fields value here is deliberately wide because a single-record read costs one request against a 50-per-minute budget either way.

Clio Manage: Get Document

Fetch one document's metadata in full, including its latest version, who created it and which matter it is filed on. Metadata only - the file itself comes from Clio Manage: Download Document.

Clio Manage: Get Matter

Fetch one matter in full: client, practice area, stage, the three attorney roles, billing configuration and custom field values. Use this when the fields value you want would be too wide to run across the whole firm. Clio strips rather than refuses: a record the caller may not fully see comes back with the forbidden fields removed and redacted set to true, at HTTP 200. Check for redacted before trusting a field is absent.

Clio Manage: Get Note

Fetch one note in full, including its body and whether it is plain text or rich text. Privileged content: see the notes list node.

Clio Manage: Get Running Timer

Read the timer currently running for the authorising user, with its start time, elapsed seconds and the activity it is attached to. Clio runs at most ONE timer per user, so this is a singleton endpoint with no id. Returns 404 when no timer is running, which is a normal answer rather than an error.

Clio Manage: Get Task

Fetch one task in full, including its description body, its assignee, and the time entries recorded against it.

Clio Manage: List Activities

List time entries and expenses. This is the firm's revenue record: filter by matter, by timekeeper, by date range, and by billing status to answer questions like what is unbilled on this matter or how much did this attorney record last month. quantity is in SECONDS for time entries (changed in API version 4.0.4 - it used to be hours), and in units for expense entries. quantity_in_hours carries the hours form. Money and hours on time entries are subject to two firm settings. With Billing Rate Visibility set to Own or None, price and total are removed and redacted is set to true. With Activity Hours Visibility restricted, quantity, rounded_quantity, quantity_in_hours, rounded_quantity_in_hours, total and non_billable_total come back NULL and quantity_redacted is set to true. Summing a page that contains redacted rows produces a number that is wrong and looks right, so filter on those flags before aggregating.

Clio Manage: List Activity Descriptions

List the firm's billing codes: the reusable activity descriptions that pre-fill a time entry's narrative and rate, including UTBMS task and activity codes for firms that bill insurers. This is the source for the billing-code picker on the activity nodes.

Clio Manage: List Bill Line Items

List the individual lines that make up an invoice, with each line's description, quantity, price, tax and total. This is how a workflow reconstructs a bill in detail - for a client-facing statement, a spreadsheet export, or a reconciliation against the activities that produced it.

Clio Manage: List Billable Matters

Work in progress: matters with unbilled hours and unbilled value, plus how much of the client's money is sitting in trust against each. This is the pre-billing worklist - run it at month end to find the matters that are ready to invoice. Clio computes the figures, so this is one request rather than a walk over every activity.

Clio Manage: List Bills

List invoices with their totals, what has been paid, and what is still outstanding. balance is the amount still owed, which makes state plus balance the pair an accounts-receivable workflow runs on: state=awaiting_payment with overdue_only is the collections list. This is the source for every bill picker in this connector.

Clio Manage: List Calendar Entries

List calendar events in a time range: hearings, meetings, deadlines. The from and to filters are the pair to use - from matches events ENDING on or after it and to matches events BEGINNING on or before it, so together they catch anything overlapping the window rather than only events wholly inside it. Set expanded to get one row per occurrence of a recurring event instead of one row for the series.

Clio Manage: List Calendars

List the firm's calendars: each user's own calendar, shared firm calendars, and any ad-hoc ones. Filter on writeable to find the calendars the authorising user may actually create events on, which is what you want before wiring a create node. This is the source for the calendar picker.

Clio Manage: List Clio Payments

List payments taken through Clio Payments, the card and ACH rail built into Clio, with the amount, currency, state and the bills each one was applied to. Only available to firms that have Clio Payments enabled; a firm that takes payment by cheque or bank transfer records it as an allocation instead, so read Clio Manage: List Payment Allocations for the complete picture.

Clio Manage: List Communications

List the communication log: phone calls and emails recorded against a matter, with who sent and received each one. The bodies of these records ARE the privileged communications themselves, which makes this the most sensitive read on the connector - the default fields value deliberately includes subject but not body for that reason.

Clio Manage: List Contacts

List the firm's address book: clients, opposing parties, experts, vendors and everyone else, as either a Person or a Company. This is the source for every contact picker in this connector. From API version 4.0.9 contacts are also filtered and redacted by the firm's Contacts Visibility permission, so two users can legitimately get different counts from the same call. Clio strips rather than refuses: a record the caller may not fully see comes back with the forbidden fields removed and redacted set to true, at HTTP 200. Check for redacted before trusting a field is absent.

Clio Manage: List Custom Fields

List the firm's custom field DEFINITIONS - their names, types and whether they apply to matters or contacts. These are not the values: a field definition's id is a plain integer and is what you pass to set a value for the first time, while a stored VALUE has a composite id like text_line-55001 and is read through the custom_field_values association on a matter or a contact. Request picklist_options{id,option} on a picklist field to see the choices, because a picklist VALUE is the option's id rather than its label.

Clio Manage: List Documents

List documents stored in Clio, by matter, by contact, by category or by folder. Returns METADATA only - use Clio Manage: Download Document to get a URL for the file itself. Set scope to descendants with a parent_id to walk a whole folder tree rather than one level.

Clio Manage: List Expense Categories

List the firm's expense categories, with the default rate and whether each is a hard cost (money the firm actually paid out) or a soft cost (an internal charge such as photocopying). This is the source for the expense-category picker on the activity nodes.

Clio Manage: List Matter Contacts

List every contact attached to one matter - the client plus each related contact - with the RELATIONSHIP each one has to the matter (opposing counsel, expert, insurer, and whatever else the firm has defined). This is the node that answers who is involved in a case, which the plain contacts list cannot.

Clio Manage: List Matter Stages

List the workflow stages a firm has defined. Stages are the firm's own steps (intake, discovery, and so on) and are tied to a PRACTICE AREA, so filter by practice area to get the stages valid for a given matter. Stages are not the same thing as a matter's status, which is the fixed open/pending/closed lifecycle.

Clio Manage: List Matters

List the firm's matters (cases/files), with the client, practice area, responsible attorney, stage and open/close dates for each. This is the node most Clio workflows start from, and it is the source for every matter picker in this connector. Note the status filter's trap: passing status=open EXCLUDES pending and closed, while omitting it returns all three. Clio strips rather than refuses: a record the caller may not fully see comes back with the forbidden fields removed and redacted set to true, at HTTP 200. Check for redacted before trusting a field is absent.

Clio Manage: List Notes

List notes on matters or contacts. A note in Clio is attorney work product as often as not, so treat every field of this output as privileged - and be deliberate about where a workflow sends it. Clio requires the type parameter on this endpoint (Matter or Contact); the node defaults it to Matter.

Clio Manage: List Outstanding Client Balances

The firm's accounts-receivable list, computed by Clio: one row per client with the total still outstanding, any pending payments, when they last paid, and when their oldest unpaid bill fell due. Prefer this over summing bills yourself - Clio does the arithmetic across every invoice, credit and write-off, and it is one request instead of a page-by-page walk against a 50-per-minute rate limit.

Clio Manage: List Payment Allocations

List how money has been applied to bills. An allocation is one payment, credit note or write-off landing on one invoice, with its date, amount and payment type. This is the node that answers what has actually been paid and when - Clio Manage v4 has no separate payments index, so allocations are how payment history is read. voided_at is set when an allocation has been reversed, so filter it out before adding anything up.

Clio Manage: List Payment Links

List the firm's Clio Payments links: shareable URLs a client can pay through. Each row carries the live payment URL, so treat the output as sensitive even though it is not a credential - anyone with the link can open the payment page for that client's bill.

Clio Manage: List Practice Areas

List the firm's practice areas - the categories it organises work into, such as family, corporate or immigration. Matter stages hang off a practice area, so this is the first step in the practice area to stage chain, and it is the source for every practice-area picker here.

Clio Manage: List Task Types

List the task types a firm has defined - its own categories for work such as court filing or client follow-up. This is the source for the task-type picker on the task nodes.

Clio Manage: List Tasks

List tasks, filtered by matter, assignee, status, priority or due date. Two filters worth knowing: statute_of_limitations isolates the deadline tasks a firm cannot afford to miss, and permission distinguishes private tasks from ones the whole firm can see. This is the source for every task picker in this connector.

Clio Manage: List Users

List the firm's users: attorneys and staff who work in Clio, as distinct from Contacts, who are the people the firm works FOR and against. Every attorney field on a matter references one of these. This is the source for the user pickers throughout this connector.

Clio Manage: Who Am I

Return the firm user the stored credential belongs to. This is the cheapest authenticated call on the whole API and it is what this connector's auth test probes, so run it first when anything looks wrong: a 200 proves the token, the region and the header wiring all at once, and a 401 tells you one of them is off. It also answers the question that matters before any write - every action on this connector runs AS this user and inherits their role and visibility settings, not the firm's full access.

Action nodes 25

Clio Manage: Create Activity

Record a time entry or an expense against a matter. quantity is in SECONDS for time entries (changed in API version 4.0.4 - it used to be hours), and in units for expense entries. quantity_in_hours carries the hours form. total is CALCULATED by Clio from quantity and price, which is why the default fields value asks for it back - you get the computed amount in the same call instead of a second read. Reversible: an activity that has not been billed can be deleted.

Clio Manage: Create Calendar Entry

Put an event on a calendar: a hearing, a client meeting, an internal deadline. Setting send_email_notification emails every attendee, including any CONTACT attendees, who are the firm's clients and opposing parties - a bulk workflow with this on sends bulk mail to people outside the firm. Reversible: the entry can be updated or deleted, though a notification already sent cannot be recalled.

Clio Manage: Create Contact

Add a person or a company to the firm's address book. For a Person set first_name and last_name; for a Company set name. This is the first step before opening a matter, because a matter's client must be an existing contact. Note that Clio returns 422 Unprocessable Entity when a contact exceeds the association limits introduced in API version 4.0.13.

Clio Manage: Create Matter

Open a new matter for a client. The client must already exist as a contact - create it first with Clio Manage: Create Contact. Clio assigns the display number from the firm's numbering scheme unless one is supplied. Classed reversible because a matter created by mistake can be deleted, but read Clio Manage: Delete Matter before relying on that: the delete does not reverse.

Clio Manage: Create Note

Add a note to a matter or a contact. This is the natural landing place for automated summaries - a call transcript, an AI-drafted summary of an email thread, a status update from another system - because it puts the record where the firm already looks. Set type to match the association you fill in: a Matter note wants a matter, a Contact note wants a contact.

Clio Manage: Create Payment Link

Create a Clio Payments link a client can pay through. Requires the firm to have Clio Payments enabled and a destination account configured. This is a MONEY-FACING write: the response carries a live URL that will take a real card or bank payment, so treat the node's output as sensitive and be careful about where a workflow sends it. Classed reversible because a link can be deactivated, but a payment already taken through one cannot be un-taken from here.

Clio Manage: Create Task

Create a task, optionally on a matter and optionally assigned to someone. Setting notify_assignee sends a real notification to a real person, so a workflow that loops over matters sends one email per iteration - think about that before scheduling it. Reversible: the task can be deleted or completed.

Clio Manage: Delete Activity

PERMANENTLY DELETE a time entry or expense. Clio documents no undelete for activities, so the record and its narrative are gone: this is the firm's evidence that work was done, which matters if the bill it supports is ever challenged or audited. The reversible alternative is Clio Manage: Update Activity with non_billable set to true, which keeps the record and takes it off the invoice. Deletes return 204 No Content with an empty body, and the fields parameter does not apply to them.

Clio Manage: Delete Calendar Entry

PERMANENTLY DELETE a calendar entry. Clio documents no undelete for calendar entries. On a legal calendar this is the sharpest of the deletes: a hearing date or a court-rules deadline that disappears takes the firm's only reminder with it, and nothing in the API records that it ever existed. Deleting an entry with external attendees does not necessarily withdraw the invitation they already received. Deletes return 204 No Content with an empty body, and the fields parameter does not apply to them.

Clio Manage: Delete Contact

PERMANENTLY DELETE a contact. Clio documents no undelete and no trash state for contacts, so unlike a Document this cannot be recovered through the API. A contact who is a client on a matter, a bill recipient, or a party on a communication is referenced by records the firm must retain, and Clio will normally refuse the delete rather than orphan them - expect a 422 rather than a silent cascade. There is no archive flag on contacts, so the usual safe alternative is to leave the record in place. Deletes return 204 No Content with an empty body, and the fields parameter does not apply to them.

Clio Manage: Delete Document

Move a document to the trash. This is the ONE delete on this connector that Clio documents as recoverable: the document goes to the trash rather than being purged, and is permanently deleted only after 30 DAYS. Within that window it is still readable through Clio Manage: List Documents with include_deleted set, and restorable from Clio's own UI. Classed Destructive so the endpoint test matrix skips it - running it would trash a real firm's document - but NOT flagged destructive, because the 30-day trash is a genuine undo and saying otherwise would make the flag meaningless. Returns 409 Conflict if the document or an ancestor folder is being modified by another request. Deletes return 204 No Content with an empty body, and the fields parameter does not apply to them.

Clio Manage: Delete Matter

PERMANENTLY DELETE a matter. Clio documents no undelete for matters: the API has no restore endpoint and no trash state for them, unlike Documents, which Clio explicitly trashes for 30 days first. A matter is the firm's record of a client engagement and is usually under a professional or statutory retention obligation, so deleting one can be a compliance event as well as data loss. The reversible alternative is Clio Manage: Update Matter with status set to closed, which hides the matter from active views and keeps everything attached to it. Deletes return 204 No Content with an empty body, and the fields parameter does not apply to them.

Clio Manage: Delete Note

PERMANENTLY DELETE a note. Clio documents no undelete for notes and keeps no version history, so the text is unrecoverable. A note is frequently attorney work product and part of the file the firm is obliged to retain, so deleting one can be a records-retention problem as well as data loss. Deletes return 204 No Content with an empty body, and the fields parameter does not apply to them.

Clio Manage: Delete Or Void Bill

Delete or VOID an invoice. Clio chooses which, from the bill's current state: Draft becomes Deleted, Pending Approval becomes Deleted, and Unpaid becomes VOID. A bill can only be deleted or voided when it has NO PAYMENTS RECORDED and is in one of those three states; anything else is refused with a 403. Classed destructive even though the row survives (it stays readable at state=deleted or state=void), because Clio documents no transition back out of either state: voiding an issued invoice is an accounting event, not an edit, and the only way to bill that work again is to raise a new invoice. Deletes return 204 No Content with an empty body, and the fields parameter does not apply to them.

Clio Manage: Delete Task

PERMANENTLY DELETE a task. Clio documents no undelete for tasks. The sharp edge here is the statute-of-limitations flag: deleting a task carrying a real limitation deadline removes the firm's reminder of a date it cannot miss, with no trace that it existed. Completing the task instead (Clio Manage: Update Task, status complete) keeps the record and is reversible. Deletes return 204 No Content with an empty body, and the fields parameter does not apply to them.

Clio Manage: Log Communication

Record a phone call or an email against a matter, so it lands in the firm's communication log. This is the write half of the log: point a phone system, a shared mailbox or a chat channel at it and the matter's file stays complete without anybody retyping. It does NOT send anything - Clio records that a communication happened, it does not place the call or deliver the email.

Clio Manage: Start Timer

Start the authorising user's timer on an existing activity. Clio allows ONE running timer per user, so starting a second one is an error rather than a queue. To create the activity and start timing in a single call, use Clio Manage: Create Activity with start_timer set instead. Reversible: stop the timer.

Clio Manage: Stop Timer

Stop the authorising user's running timer and commit the elapsed time onto the activity it was attached to. This is a DELETE by HTTP verb but it is not a destructive one: it ends the timer, not the time entry, and the activity survives with its quantity updated. The activity can then be edited or deleted separately. Takes no parameters - Clio runs one timer per user. Deletes return 204 No Content with an empty body, and the fields parameter does not apply to them.

Clio Manage: Update Activity

Edit a time entry or expense: fix the duration, rewrite the narrative, change the rate, or mark it non-billable. quantity is in SECONDS for time entries (changed in API version 4.0.4 - it used to be hours), and in units for expense entries. quantity_in_hours carries the hours form. Two failure modes worth knowing: an entry that is already on a bill may be refused, and a user whose Activity Hours Visibility is restricted gets a 403 when trying to change quantity or user on an entry whose hours are redacted for them.

Clio Manage: Update Bill

Edit an invoice, or move it through the billing workflow by setting state (draft to awaiting_approval to awaiting_payment to paid). Read available_state_transitions on the bill first: Clio only accepts the transitions it lists, and a rejected one is a 422 rather than a no-op. Two of the transitions are one-way and are covered by Clio Manage: Delete Bill instead. Classed reversible because ordinary edits and forward transitions are; setting state to void or deleted through this node is NOT, so use the delete node, which says so.

Clio Manage: Update Calendar Entry

Reschedule or edit a calendar entry. On a recurring series this edits the series; Clio's _deleted parameter (single or future) is the mechanism for scoping a change to one occurrence, and it is reachable through extra_body. Setting send_email_notification re-notifies every attendee.

Clio Manage: Update Contact

Change a contact's details or write custom field values. Only the fields you fill in are sent. Careful with the collection fields: email_addresses, phone_numbers and addresses are nested-attribute collections, so an entry WITHOUT an id is added, an entry WITH an id is updated, and an entry with an id plus "_destroy": true is removed. Sending a bare list of new values does not replace the existing ones, it appends to them.

Clio Manage: Update Matter

Change a matter: move it to a new stage, close it, reassign the responsible attorney, or write custom field values. Only the fields you fill in are sent, so this is a genuine partial update. Setting status to closed deletes nothing and is undone by setting it back to open.

Clio Manage: Update Note

Edit a note's subject, body or date. Clio keeps no version history on notes, so an edit REPLACES the previous text with no way to read what was there before - which, on a record that may be work product, is worth knowing before automating it.

Clio Manage: Update Task

Change a task: complete it, reassign it, move its due date, or raise its priority. Setting status to complete is the normal way to close a task and is fully reversible - set it back to pending. Only the fields you fill in are sent.

Connecting Clio Manage takes one credential

There is no API key to copy or paste. You create a Developer Application in the Clio developer portal, which requires access to a paid Clio account, and then sign in and approve the connection. Two things about Clio's permission model are worth knowing before you do it. Clio's authorize endpoint takes no scope parameter at all: the permissions your application holds are configured on the application itself, per resource, as read-only or read/write, and the consent screen shows the user whatever the application was configured with. And once a user has authorized, their permissions are fixed even across token refreshes, so adding a permission later means every user reauthorizes. Getting the permission set right before anyone connects is therefore load-bearing rather than tidy. For the node set on this page that means read/write on Matters, Contacts, Activities, Bills, Tasks, Calendar, Notes, Communications, Documents and Clio Payments, plus read on Users. A firm that only wants reads can configure the application read-only throughout, and the write nodes then return a clear 403 instead of failing quietly.

1

Confirm the Clio plan supports it. Apps and integrations, including private apps, are not available on Clio's EasyStart tier, and creating an application needs access to a paid Clio account. This is a plan boundary rather than a bug to diagnose.

2

Decide which Clio user should hold the connection. Every action runs as that user and inherits their role and visibility settings rather than the firm's full access, and unattended automations keep running on it, so a user your firm controls beats an individual's personal login.

3

Create a Developer Application in the Clio developer portal and set its permissions per resource before anyone connects. Clio does not review private Clio Manage applications, so there is no wait here, but the permissions you pick now are the permissions every authorized token keeps.

4

In Mattering Automations, open Connectors, click Add Connector and choose Clio Manage, then click Connect and complete Clio's sign-in and consent screen. There is no key to type. The connect flow authorizes against Clio's United States deployment.

5

Click Test Connection. Mattering calls Clio's who_am_i endpoint, the cheapest authenticated call on the API, which proves the token, the region and the header wiring in one request. A 401 means the credential or the region is wrong; a 403 means the credential is fine and the application is missing a permission.

6

All 60 Clio Manage nodes appear in the canvas palette. Run Clio Manage: Who Am I first, then Clio Manage: List Matters, which returns real records rather than bare ids because the node already carries a fields value. The token is stored encrypted, refreshed before it expires, and revoking the application inside Clio ends the connection immediately.

Common uses for the Clio Manage MCP

A month-end pre-billing worklist that a person signs off

Clio Manage: List Billable Matters is the node to start from, because Clio computes unbilled hours, unbilled value and trust balance per matter server side, which is one request instead of walking every activity against a 50-per-minute budget. Clio Manage: List Activities then pulls the entries behind a chosen matter with the narrative and the amounts in a single wide call, and an AI step can summarise what the month looked like and flag entries with thin descriptions. One caution belongs in the design rather than in a surprise: Clio redacts money and hours per row according to the firm's Billing Rate Visibility and Activity Hours Visibility settings, returning HTTP 200 with nulls and a redacted or quantity_redacted flag, so a total that ignores those flags is silently low and looks right.

Intake that opens the file properly the first time

A form submission or an inbound email can become a real Clio file without anybody retyping it. Clio Manage: Create Contact adds the person or the company, which has to happen first because a matter's client must be an existing contact. Clio Manage: Create Matter opens the file, with Clio Manage: List Practice Areas and Clio Manage: List Matter Stages supplying the valid stage for the practice area you picked, since stages hang off a practice area rather than floating free. Clio Manage: Create Task can then lay down the intake checklist and Clio Manage: Create Calendar Entry the first deadline. Clio Manage: Update Matter writes custom field values back later as the file develops.

Collections driven from what Clio already computed

Clio Manage: List Outstanding Client Balances gives one row per client with the total outstanding, any pending payments, when they last paid and when their oldest unpaid bill fell due, arithmetic Clio does across every invoice, credit and write-off. Clio Manage: List Bills narrows to the invoices themselves, where state paired with balance is the collections filter, and Clio Manage: List Payment Allocations answers what has actually been paid and when. Clio Manage: Create Payment Link produces a link the client can pay through where the firm has Clio Payments enabled. Treat that output as sensitive: it is a live payment page for anyone holding the URL, which is why the node says so.

Deadline sweeps on the diary and the task list

Clio Manage: List Tasks carries a statute_of_limitations filter, which isolates exactly the deadlines a firm cannot afford to miss, and a permission filter that separates private tasks from firm-visible ones. Clio Manage: List Calendar Entries reads a window of hearings, meetings and deadlines, and its from and to filters overlap rather than contain: from matches events ending on or after it and to matches events beginning on or before it, so an event straddling a boundary is returned by both adjacent windows and concatenated chunks double count it unless you dedupe on id. A scheduled digest that opens a Mattering Productivity task for anything unassigned or unconfirmed is a read-only way to get value here.

Keeping the file complete from the systems around Clio

Clio Manage: Log Communication records that a phone call or an email happened against a matter, so a phone system, a shared mailbox or a chat channel can keep the communication log honest without anybody retyping it. It records rather than sends: Clio does not place the call or deliver the mail. Clio Manage: Create Note is the landing place for an automated summary, a call transcript or a status update from another system, because it puts the record where the firm already looks. Be deliberate with Clio Manage: Update Note, though: Clio keeps no version history on notes, so an edit replaces the previous text with no way to read what was there.

Document lookups without moving the file

Clio Manage: List Documents finds documents by matter, by contact, by category or by folder, and returns metadata only. Clio Manage: Get Document reads one record in full with its latest version and who created it. Clio Manage: Download Document is the one that reaches the bytes, and it deliberately does not follow Clio's redirect: it returns a short-lived signed URL at data.download_url for a following step to fetch. That URL grants access to a privileged document to anyone holding it, so it belongs nowhere the document itself should not go, and it expires, so fetch it promptly rather than storing it. Clio Manage: Delete Document is the gentlest delete on this connector, moving a file to the trash for 30 days rather than purging it.

Example: A month-end billing review where nothing is invoiced without a human

Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.

1

Trigger: a monthly schedule fires. This connector has no trigger nodes, so Clio workflows run on a schedule and read rather than listening for a push.

2

Clio Manage: List Billable Matters returns every matter with unbilled hours and unbilled value, computed by Clio, in one request rather than a walk over the firm's whole activity history.

3

For matters over a threshold, Clio Manage: List Activities pulls the entries behind the number in one wide call, with the narrative, the quantity in seconds and the computed total, filtered so that rows carrying redacted or quantity_redacted flags are excluded from any arithmetic rather than silently lowering it.

4

An AI step reviews the narratives for entries that are too thin to send to a client and drafts a plain summary of the month per matter. Nothing has been written to Clio at this point.

5

A task is created in Mattering Productivity with the matter, the figures and the draft, so a responsible attorney reads it before a client does.

6

On approval, Clio Manage: Create Note writes the agreed summary onto the matter so the decision is recorded where the firm looks. Invoicing itself stays in Clio with a person doing it, because Clio Manage: Delete Or Void Bill has no documented way back and an issued invoice is an accounting event rather than an edit.

Clio Manage MCP questions, answered

What can this connector actually do in Clio Manage?

60 nodes: 35 read and 25 act. Reads cover matters, matter contacts, contacts, activities, the running timer, activity descriptions, expense categories, bills, bill line items, payment allocations, outstanding client balances, billable matters, Clio Payments and payment links, tasks, task types, calendar entries and calendars, notes, communications, documents and document download URLs, practice areas, matter stages, custom field definitions, users, and the connection check. Writes cover creating and updating matters, contacts, activities, tasks, calendar entries and notes, starting and stopping the timer, logging a communication, updating and transitioning bills, creating a Clio Payments link, and the eight deletes. Not included and worth knowing before you plan: webhooks and secure client conversations, which are trigger surfaces this connector does not have; trust accounting and bank accounts; court rules and matter dockets; the personal injury module; reports, which are asynchronous; and document upload, which is a multi-step file transfer rather than a single call.

Does this work with Claude, ChatGPT, or other AI assistants?

Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant, including Claude and ChatGPT, can connect to your workspace and work with Clio Manage through them. Matter, the assistant built into the platform, uses the same nodes natively. The same nodes are also steps on the automation canvas, so the workflow an agent helps you design can then run on a schedule with nobody present. Given what is in a Clio account, the sensible split is to hand an assistant the read nodes and keep the writes, especially the deletes, behind a condition or an approval step.

Why does every read node ask which fields to return?

Because Clio will otherwise return almost nothing, and it will do it at HTTP 200 with no error to lead you to the cause. Clio's own documentation is explicit that a request without the fields parameter returns a minimal set of default fields, and that for most endpoints id and etag are the only ones. So a plain call to the matters endpoint returns a page of objects carrying an id and an etag and nothing else. Every node here that returns a Clio record carries a fields value with an authored default, which is why the nodes return usable records out of the box and why the pickers show display numbers and names rather than raw integers. Three details when you widen it: the format is comma separated with no spaces, an association can be expanded with a brace list such as matter{id,display_number}, and nesting is one level deep only, so a second level is refused with a 400. A field name Clio does not recognise is also a 400, which means typos fail loudly rather than silently.

Does Clio publish its own MCP server?

No. There is no first-party Clio MCP server. Clio's developer documentation covers the Clio Manage API, the Clio Platform, webhooks, SSO and the App Directory process, and does not mention MCP or the Model Context Protocol anywhere. That means this page is not competing with a vendor server, and the connector is the practical way to put Clio behind an MCP-capable assistant today: 60 nodes usable over MCP and as steps on an automation canvas, so the same capability runs on a schedule with nobody present, chains with every other connector in one workflow, holds the credential once in a shared workspace rather than in each person's local config, and carries destructive flags on the seven nodes that need them.

Can I connect a firm outside the United States?

Not through the connect flow today, and the reason is structural rather than an oversight. Clio runs four independent regional deployments, in the United States, the European Union, Canada and Australia, on different hosts, and states that a token issued in one region is not valid against another region's API. Region therefore lives on the credential. Clio also requires a separate Clio account and a separate Developer Application in each region, with a different application id per region, so an EU, Canadian or Australian firm needs a sibling OAuth provider with its own application, and those do not exist yet. The connector's runner honours the region recorded on a credential and refuses an unrecognised value rather than silently sending a European firm's token to a United States host, which would surface as a 401 that reads like a bad credential. We would rather say this plainly here than have you find it at the consent screen, and we are not putting a date on it.

Is it safe to point an AI assistant at privileged client data?

It is a decision to make deliberately rather than a yes or a no, and the connector is built to make the careful version easy. The defaults on the three most sensitive reads are narrow on purpose: the communications lister returns the subject and not the body, because a communication body is the privileged communication itself; the calendar lister leaves out the attendee list, which names clients and opposing parties; and the users lister leaves out billing rates. Each is available and documented as available, and none is returned unless you ask for it. Clio also redacts server side rather than refusing, returning a record with the forbidden parts stripped and a redacted flag at HTTP 200, so an absent field is not always an empty field. The practical habit is to select the fields a workflow needs instead of forwarding a whole Clio object into a chat window, a spreadsheet or an AI step. Privilege can be waived by disclosure, and no redaction afterwards undoes that.

What happens when a workflow deletes something in Clio?

Three different things, and flattening them is how people get hurt. Clio Manage: Delete Document is the mild one: Clio moves the file to the trash, where it stays readable through the documents lister with deleted records included, and purges it only after 30 days. Clio Manage: Delete Or Void Bill is not really a delete: Clio transitions a Draft or Pending Approval bill to Deleted and an Unpaid bill to Void, only when the bill has no payments recorded against it, refusing anything else with a 403, and Clio documents no transition back out of either state, so the only way to bill that work again is a new invoice. The other six are permanent: deleting a matter, contact, activity, task, calendar entry or note has no trash state and no restore endpoint documented anywhere in Clio's API description. Each of those six names the reversible alternative in the node itself, which is usually what the workflow wanted anyway: close the matter, complete the task, mark the activity non-billable. Deleting a task carrying a statute of limitations date is the sharpest of them, because it removes the firm's only reminder of a deadline it cannot miss and leaves no trace it existed.

Do I need Clio's approval, and is every Clio plan supported?

Approval and access are two different things, and the difference is worth being exact about. There is no approval gate on calling the Clio Manage API: any firm on a paid Clio plan can create a Developer Application in the Clio developer portal, get a key and secret, and call its own data straight away. Clio states plainly that private Clio Manage apps are not reviewed and cannot be published in its App Directory. The review process, which is a security questionnaire, a recorded demo and a listing form, gates being listed in Clio's App Directory, which is a distribution question rather than an access one. Two limits are hard, though. Apps and integrations, including private apps, are not available on Clio's EasyStart tier, so a firm on EasyStart cannot use this connector at all regardless of what anyone builds. And creating an application requires access to a paid Clio account. Clio also documents no separate sandbox: a Clio Manage trial account is the test environment.

What are Clio's rate limits?

Clio documents 50 requests per minute per access token at peak hours, with a higher off-peak allowance that varies by region, and states that it does not grant custom increases. The limit is per token rather than per application, and every response carries the remaining count and a reset timestamp, with a 429 carrying a retry delay. That number shapes how a Clio workflow should be built more than anything else here: one list call with a wide fields value beats a list call followed by one read per row, and a list-then-fetch-each loop over a mid-sized firm exhausts the budget in under a minute. Index calls return up to 200 records per page and this connector does not auto-paginate, so each node is one request and an unbounded walk never hides behind a single canvas step. Where Clio has already done the arithmetic, use it: Clio Manage: List Outstanding Client Balances and Clio Manage: List Billable Matters each replace a page-by-page walk with one call.

60 nodes waiting on the canvas

Put Clio Manage to work inside your workspace

Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.

All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Clio Manage is a product of its respective owner; Mattering is an independent platform.

Start Free Explore our Products