Skip to main content
Glama

clio-mcp – Claude ↔ Clio Manage

An MCP server that lets Claude work inside your Clio Manage account through Clio's official API v4. It is installed as a Desktop Extension for Claude Desktop (also available in Cowork) and runs only on your own computer – there is no server in between you and Clio.

Version: 1.0.0 · Windows x64 · all Clio regions (US, EU, CA, AU) · licence Apache-2.0 This project is not affiliated with Clio or Anthropic.

What it does

Area

What Claude can do

Documents

Find documents in a matter · read the text of DOCX/PDF/TXT files · read scanned PDFs and images (pages are handed to Claude as pictures, so it reads them itself) · download a document to a folder on your PC for editing · upload the edited file as a new version · create a new document on your letterhead (Claude writes the text, the server puts it into your Clio Document Template and saves it in a "Claude" folder in the matter) · rewrite a document Claude created · create folders · add comments

Time & expenses

List and summarise time entries (per matter, user, period, billed/unbilled) · record time and expenses · edit entries · activity codes and rates · timer status/start

Billing data

Matters with unbilled work · list bills · bill details with line items · update a bill (state, memo, dates) or a line item · outstanding balances

Matters & contacts

Search, view, create and update matters and contacts · practice areas · custom fields

Tasks & calendar

Tasks (create, update, complete) · calendars and calendar entries

Other

Notes · communication log · users · text snippets

Anything else in the API

clio_describe_api finds the right endpoint in Clio's OpenAPI description; clio_api_request calls it (GET/POST/PATCH) with validation of path, parameters and body

55 tools in total. Claude sees short instructions from the server (check sign-in first, preview before writing, where new documents go), so in practice you just ask: "Record 0.5 h on the Smith matter for today's call", "What's unbilled on Smith?", "Read the last letter in the Smith matter and draft a reply on my letterhead."

Related MCP server: LegalContext

What it deliberately does not do

  • Nothing is ever deleted. The connector has no delete tools and the generic API call refuses the DELETE method – both in the tool definition and in the HTTP client. If something needs deleting (a test time entry, a duplicate folder, a timer that must be stopped – Clio stops timers with DELETE /timer), do it in Clio itself.

  • You decide how writes are confirmed. The Write confirmation setting has two modes (details below): auto (default) – Claude records the time, creates the document or updates the task directly when your request is complete, and asks only when information is missing; ask – every write first shows you a preview and is carried out only after your approval, which the server enforces with a confirmation token.

  • No bills are created or sent. Clio's API only lets bills be read and edited; sending invoices to clients stays in Clio.

  • No way around Clio permissions. If your Clio role hides something (rates, bills, other users' time), the API returns it as redacted and the connector shows exactly that.

  • No cloud component. Tokens, the audit log and downloaded documents stay on your computer. The only parties that see your data are Clio and the Claude model you talk to (under your Anthropic plan's terms).

Installation (step by step)

You need: Claude Desktop on Windows (64-bit), a Clio Manage account whose plan allows developer applications (not available on Clio's EasyStart plan), and about 15 minutes.

Step 1 – Create a Developer Application in Clio

The connector signs in to Clio with OAuth, like any Clio integration. For that Clio needs to know the application, so you register one yourself. One application per firm is enough – every user then signs in with it on their own PC.

  1. Open the developer portal for your region and sign in with your Clio login:

  2. Click Add (new application) and fill in:

    • Name: e.g. Claude connector (your users will see this name on Clio's consent screen and under Settings → Apps).

    • Website URL: your firm's website (any valid URL).

    • Redirect URIs – add all three, exactly as written:

      http://127.0.0.1:53682/callback
      http://127.0.0.1:53683/callback
      http://127.0.0.1:53684/callback
    • Permissions (scopes): tick read and write for the areas you want Claude to use. For the full tool set that is: Activities, Api, Billing, Calendars, Communications, Contacts, Custom fields, Documents, General, Matters, Reporting, Settings, Tasks, Users. (Scopes are fixed when a user authorises the app; if you add scopes later, every user has to sign in again.)

    • Accept Clio's Developer Terms of Service and save.

  3. Clio shows the application's App Key and App Secret. Keep this page open – you will paste both values in step 3. Treat the App Secret like a password (do not send it by e-mail or paste it into a chat).

Clio's own guide: https://docs.developers.clio.com/api-docs/clio-manage/applications/

Step 2 – Install the extension in Claude Desktop

  1. Download clio-mcp-<version>.mcpb from the release/ folder of this repository (open the file and click Download raw file), or from the Releases page.

  2. In Claude Desktop open Settings → Extensions → Advanced settings and click Install Extension…, then pick the downloaded .mcpb file. (Double-clicking the file in Explorer works too.)

  3. Claude Desktop shows the extension's settings form (step 3).

Step 3 – Fill in the settings

Setting

What to enter

Clio region

us, eu, ca or au – the region your Clio account lives in (look at the address bar when you use Clio: app.clio.com = us, eu.app.clio.com = eu, …).

Language of messages

Optional, default en. Language of previews, errors and notes (en or cs). Tool descriptions are always English; Claude answers in whatever language you write.

Write confirmation

Optional, default auto. How Claude confirms writes to Clio – see Write confirmation modes.

Clio App Key (Client ID)

The App Key from step 1.

Clio App Secret (Client Secret)

The App Secret from step 1. Claude Desktop stores it in the Windows Credential Manager, not in a file.

Work folder for documents

Optional. Folder on your PC where documents are downloaded for editing (default Documents\Clio MCP). If you use Cowork, connect the same folder there.

Folder name in Clio for documents created by Claude

Optional, default Claude. Created automatically in each matter's documents.

Default letterhead / template

Optional. Name (or beginning of the name, or id) of the Clio Document Template to use for new documents. Leave empty if you have only one template or want to choose per document.

Per-user letterheads

Optional. If each lawyer has their own letterhead template: jane@firm.com=Jane_letterhead;john@firm.com=John_letterhead. The connector picks the template by the e-mail of the signed-in user.

Template for internal documents

Optional. Template used when Claude is asked for an internal document (kind=internal).

Save, enable the extension and restart Claude Desktop.

Step 4 – Sign in to Clio (once per user and PC)

In a new chat type: "Sign me in to Clio." Claude calls clio_authenticate, which returns a link and opens your browser. Sign in to Clio, review the permissions and click Allow. Back in the chat ask "Who am I in Clio?" – you should see your name. The sign-in is remembered (Clio refresh tokens do not expire), so you will not be asked again unless you revoke access.

Each colleague repeats steps 2–4 on their own PC with the same App Key and App Secret; they sign in with their own Clio account.

Updating

Install the new .mcpb over the old one (or uninstall → install). Settings are kept; if Claude Desktop asks for the App Secret again, paste it from your password manager. Saved sign-ins in %USERPROFILE%\.clio-mcp are kept.

Everyday use

Read a document: "Open the latest filing in matter 2026-0042 and summarise it." – Claude uses clio_document_search → clio_document_read. The text comes back directly; scanned pages come back as images (4 pages per call, more on request).

Draft on letterhead: "Draft a letter to the opposing counsel in matter 2026-0042 on my letterhead." – Claude writes the text and calls clio_document_create_from_letterhead with content; you see a preview; after your OK the server fills your Clio template and saves the DOCX in the matter's Claude folder. Later corrections: "Change the second paragraph…" → clio_document_write creates a new version.

Edit an existing document (Cowork): download → Claude edits the file in your connected work folder → clio_document_upload_version after your confirmation. The previous version stays in Clio's version history.

Record time: "Record 1.2 h on 2026-0042, 'review of expert report'." → preview → confirm.

Prepare billing: "Which matters have unbilled time this month?" → clio_billable_matters_list, then clio_time_entries_list with status: unbilled, clio_bill_get for an existing draft bill.

Everything else: "Find the API endpoint for court rules" → clio_describe_api → clio_api_request.

Documents from text – formatting

Claude passes plain text with a tiny markup; the server converts it into Word paragraphs that use the styles of your template:

You write

You get

# Heading, ## Sub-heading, ### Sub-sub-heading

Heading 2 / 3 / 4 of the template

[ 1. ] Text…

Numbered paragraph: number at the margin, text indented (hanging indent, default 1.4 cm)

Evidence:: Contract dated 1 May 2026

Evidence: in bold, a tab, then the text (any label works with ::)

- item

Bullet with indent

**bold**, a tab character

Bold run, tab

:::center Text, :::right Text

Centred / right-aligned paragraph

---pagebreak---

Page break

empty line

Empty paragraph

Header, footer, page numbers and fonts come from the template, so the result looks like a document created with Clio's New document function. Advanced: the hanging indent (default 1.4 cm) and extra single-colon labels can be set through the environment variables CLIO_DOCX_INDENT_CM and CLIO_DOCX_LABELS when the server is run outside Claude Desktop.

Write confirmation modes

Every tool that changes data in Clio (time entries, documents, tasks, contacts, bills…) can be called in two steps: a preview (nothing is sent) and the write. The Write confirmation setting decides who approves the write:

Mode

What happens

For whom

auto (default)

When your request already contains everything the write needs – "Record 0.5 h on Smith for today's call" – Claude writes it straight away and tells you what it did. It asks first only when something is missing or ambiguous (which matter, what text, which activity) and it never invents content. Claude may still use the preview internally to check the data.

Users who want speed and give complete instructions.

ask

Claude must first show you a preview of exactly what will be written and wait for your approval. The server enforces this: the preview contains a one-time confirmation token bound to those exact arguments, confirm=true is rejected, and the write is accepted only with the token – so a write without a preceding preview is technically impossible.

Firms that want a human check on every change, shared PCs, onboarding of new users.

In both modes deleting is impossible and every call is written to the audit log. You can switch modes at any time in the extension settings (restart Claude Desktop afterwards).

Safety model

  • Write confirmation – auto (direct writes when the request is complete) or ask (server-enforced preview → token → write); see above.

  • DELETE is impossible. Not offered as a tool, rejected by clio_api_request, and refused again inside the HTTP client.

  • Audit log of every call (%USERPROFILE%\.clio-mcp\audit.jsonl, append-only; secrets redacted): who, when, which tool, parameters, result.

  • Tokens are encrypted with Windows DPAPI (bound to your Windows account and PC); the App Secret lives in the Windows Credential Manager.

  • Revoking access: say "Sign me out of Clio" (clio_logout, optionally with revoke=true), or in Clio Manage remove the application under Settings → Apps – that invalidates all tokens at once.

  • Details and how to report a vulnerability: SECURITY.md. What is stored where: PRIVACY.md.

Confidentiality and professional rules

Everything Claude reads from Clio is processed by the Claude model under the terms of your Anthropic plan (consumer plans and commercial/Team/Enterprise plans differ in data-retention and training terms). Before using the connector on client files, check your plan's terms and any guidance from your bar or law society on the use of generative AI with confidential client information (for example ABA Formal Opinion 512 in the US, or the guidance of your national bar in Europe). This README is not legal advice.

Languages

The server's messages (previews, errors, notes, the instructions Claude receives) are available in English (default) and Czech; choose with the Language of messages setting. Adding a language means translating the six small JSON files in src/locales/en/ into src/locales/<code>/ and registering the code in src/i18n.ts – pull requests welcome. Tool names, descriptions and output field names are English only, since they are read by the model.

Known limitations

  • Windows x64 only in this version (token storage uses Windows DPAPI; the PDF/image renderer is a native module). macOS/Linux are planned.

  • Clio's rate limit is 50 requests/minute per user; the connector queues and waits, so very large listings are slow.

  • Field selection follows Clio's rules (nested fields only one level deep); clio_describe_api {schema: "Matter"} lists valid fields.

  • Stopping a timer requires DELETE /timer, which this connector never sends – stop timers in Clio.

  • Clio's API cannot create bills; bills are created in Clio and only read/edited here.

  • Document Automation (Clio-side generation) needs templates with merge fields; the connector's own text → letterhead filling works with any DOCX template.

Troubleshooting

Symptom

What to do

"Not signed in"

Ask Claude to sign you in (clio_authenticate); afterwards check with clio_auth_status.

Browser shows a Clio error after Allow

The redirect URIs in your Developer Application must be exactly the three http://127.0.0.1:5368x/callback addresses.

401 keeps coming back

Token revoked in Clio or wrong region – check the Clio region setting matches your account, then sign in again.

403 Forbidden

Missing scope on the Developer Application (add it, then every user re-authorises) or your Clio role does not allow the action.

400 … is not a valid field

Wrong fields parameter; clio_describe_api {schema: "…"} shows valid fields.

429

Rate limit; the connector waits for Retry-After automatically.

Claude cannot open a downloaded file

In Cowork connect the folder set as Work folder; in a normal Claude Desktop chat use clio_document_read (text) instead of downloading.

clio_diagnostics

Shows configuration, token store, work folder and version – useful when reporting an issue.

Building from source

npm install
npm run fetch-spec   # downloads Clio's OpenAPI description into spec/ (not committed)
npm run catalog      # regenerates src/generated/catalog.json from it
npm run build        # type-check + bundle → dist/index.js
npm run pack         # → release/clio-mcp-<version>.mcpb (Windows x64; needs @napi-rs/canvas-win32-x64-msvc in node_modules); the built package is committed to release/
npm test             # type-check + locale catalog consistency

GitHub Actions runs type-check, catalog check, build and a smoke start on every push, packs the .mcpb on Windows, and attaches it to the GitHub Release when a v* tag is pushed (git tag v1.0.0 && git push --tags).

Project layout: src/index.ts (server, instructions for the model), src/config.ts (settings), src/oauth.ts (OAuth with loopback redirect), src/store.ts (encrypted token store), src/client.ts (HTTP client: refresh, queue, rate limit, paging), src/catalog.ts (OpenAPI catalog and request validation), src/extract.ts (DOCX/PDF text and page images), src/docx.ts (text → DOCX on a template), src/tools/* (the tools), pkg/manifest.json (Desktop Extension manifest).

Contributing

Issues and pull requests are welcome at https://github.com/marshall1727/clio-mcp. Please do not include real client data, App Secrets or tokens in bug reports; the output of clio_diagnostics and the relevant lines of the audit log (with identifiers removed) are usually enough.

Licence

Apache License 2.0 – see LICENSE and NOTICE.

Available Tools

55 tools
clio_activity_descriptions_listActivity descriptions and ratesA

Lists ActivityDescriptions (activity/expense types with their default rate) – needed to fill in activity_description_id correctly when recording time.

Inputs: query, flat_rate, matter_id.

clio_activity_updateUpdate time entry / expenseB

Updates an existing entry (as long as it has not been billed): date, hours, note, rate, activity description, billable/non-billable. Write operation – preview first, then confirm with the token from the preview.

Inputs: activity_id (required), date, note, hours, +7 more.

clio_api_requestGeneric Clio API v4 callA

Performs a GET, POST or PATCH on any Clio API v4 endpoint (path relative to /api/v4, e.g. '/matters' or '/matters/123'; or a full URL from meta.paging.next). DELETE is not allowed. The request is validated against the OpenAPI catalog (unknown path = error; unknown parameters = warning). For GET pass query.fields (without it the API returns only id and etag). The POST/PATCH body is automatically wrapped in {"data": ...}. Writes follow the preview → confirm handshake: the first call returns a preview with a confirmation token; repeat with confirm set to that token after the user approves.

Inputs: path (required), method (required), body, query, +2 more.

clio_authenticateSign in to ClioA

Starts the Clio Manage sign-in (OAuth 2.0) and IMMEDIATELY returns the sign-in URL. It tries to open the browser; if it does not open, show the URL to the user so they can open it manually. The user signs in to Clio in the browser and approves access; the tokens are then stored encrypted on this computer in the background. Verify the result with clio_auth_status (or clio_who_am_i). Use on first run or whenever another tool reports that you are not signed in.

Inputs: force.

clio_auth_statusClio sign-in statusB

Checks whether a valid Clio token is stored on this computer, who it belongs to and when it expires; also reports the state of a sign-in in progress.

Inputs: verify.

clio_billable_matters_listMatters with unbilled timeB

Lists matters with unbilled hours/amounts (basis for preparing bills), optionally for a period and client. Intended for monthly billing.

Inputs: limit, query, end_date, client_id, +4 more.

clio_bill_getBill detail including line itemsB

Returns the bill detail and its line items (date, description, quantity, price, total, link to the time entry). Optionally also the pre-rendered HTML of the bill.

Inputs: bill_id (required), include_html.

clio_bills_listList billsC

Lists bills (in Clio only the basis for the actual invoice) by state (draft, awaiting_approval, awaiting_payment, paid, void), client, matter, issue period, or overdue only.

Inputs: type, limit, query, state, +6 more.

clio_bill_updateUpdate billA

Updates the bill header (subject, memo, issue date, due date, state – e.g. draft → awaiting_approval, void). Write operation – preview first, then confirm with the token from the preview. The connector does not send bills to clients.

Inputs: bill_id (required), memo, state, due_at, +4 more.

clio_calendar_entries_listCalendarB

Lists calendar entries in a period (from–to), optionally only for a matter or from a specific calendar. Default: the signed-in user's calendars.

Inputs: to (required), from (required), limit, query, +3 more.

clio_calendar_entry_createCreate calendar entryB

Creates a calendar entry (hearing, deadline, meeting) in the user's calendar (defaults to the default calendar), optionally linked to a matter, with attendees and an event type. Write operation – preview first, then confirm with the token from the preview.

Inputs: summary (required), start_at (required), end_at, all_day, +9 more.

clio_calendar_entry_updateUpdate calendar entryB

Updates the title, time, location, description or matter of a calendar entry. Write operation – preview first, then confirm with the token from the preview.

Inputs: entry_id (required), end_at, all_day, confirm, +5 more.

clio_calendars_listList calendarsA

Lists the calendars available to the signed-in user (ids for creating calendar entries) and the calendar entry event types.

Inputs: no named parameters.

clio_communication_logLog communicationB

Logs a record of a phone call or an e-mail to a matter (subject, body, date, sender/receiver = user or contact). Write operation – preview first, then confirm with the token from the preview.

Inputs: body (required), type (required), subject (required), matter_id (required), +4 more.

clio_communications_listCommunications (e-mails, calls)C

Lists logged communications (EmailCommunication, PhoneCommunication) of a matter or a contact, newest first; optionally filtered by text or period.

Inputs: type, limit, query, matter_id, +3 more.

clio_contact_createCreate contactA

Creates a person (first_name + last_name) or a company (name) with e-mail addresses, phone numbers, address, tax/VAT number (sales_tax_number) and a link to a company. Write operation – preview first, then confirm with the token from the preview.

Inputs: type (required), name, email, phone, +10 more.

clio_contact_getContact detailB

Returns contact detail including all e-mail addresses, phone numbers, addresses and custom fields; optionally also the list of the contact's matters.

Inputs: contact_id (required), include_matters.

clio_contact_updateUpdate contactA

Updates a contact's basic details; adds an e-mail address/phone number/address (existing ones are kept). Write operation – preview first, then confirm with the token from the preview.

Inputs: contact_id (required), name, title, prefix, +9 more.

clio_custom_fields_listCustom field definitionsA

Lists custom fields for matters or contacts (id, name, type, picklist options) – required to fill in custom_field_values.

Inputs: parent_type.

clio_describe_apiDescribe the Clio API (OpenAPI catalog)A

Searches Clio API v4 endpoints by keywords (e.g. 'matters', 'time entry', 'bills line items', 'document templates') or describes a specific endpoint (method + path). Returns parameters, request-body fields and response fields usable in the fields parameter. Use it before clio_api_request when no curated tool exists.

Inputs: path, limit, query, method, +1 more.

clio_diagnosticsConnector diagnosticsA

Returns the server configuration (without secrets): region, URLs, ports, file paths, the work folder for documents, Node version and the token storage method.

Inputs: no named parameters.

clio_document_comment_addComment on documentA

Adds a comment to the current version of a document (visible in Clio next to the document). Write operation – preview first, then confirm with the token from the preview.

Inputs: message (required), document_id (required), confirm.

clio_document_create_from_letterheadNew document from letterheadA

Creates a new document in a matter from a letterhead / template (Document Template in Clio): selected by template_id or template, otherwise by configuration (user → template map, default template, kind=internal → internal template). RECOMMENDED APPROACH (works everywhere, even without disk access): pass the finished text in the content parameter – the server inserts it into the letterhead (docx) and uploads it to the "Claude" folder in the matter (preview, then confirm with the token). content format: empty line = empty paragraph; '# ' / '## ' / '### ' = Heading 2/3/4 of the template; bold; '[ 1. ] text' = numbered paragraph (number in the margin, text with a hanging indent); 'Label:: text' = bold label + tab; '- ' bullet; '\t' tab; '---pagebreak---' page break; ':::center text' centred, ':::right text' right-aligned. Follow the user's conventions for the document structure (addressee, reference numbers, date, heading, enclosures) if they state them. Alternatives: without content, mode='download' only downloads the template for manual editing (Cowork with a connected folder); mode='automation' lets Clio generate the document via Document Automation. Without a letterhead only with without_letterhead=true. Do not create empty documents: if the user has not provided the text (and the document type, addressee, matter), ask before calling this tool. mode='download' serves only a user who will edit the file in a connected folder (Cowork) – never download a template just to upload it unchanged. Choose filename from the document type and addressee (e.g. 'Letter_to_opposing_counsel_2026-10-03.docx') unless the user names it.

Inputs: filename (required), matter_id (required), kind, mode, +8 more.

clio_document_downloadDownload document to the work folderA

Downloads a document (or a specific version) from Clio to the work folder on the PC (default /root/Documents/Clio MCP, subfolder per matter) and returns the file path. Intended for opening and editing the document with Claude; upload the edited file back as a new version with clio_document_upload_version.

Inputs: document_id (required), target_dir, document_version_id.

clio_document_getDocument detailsA

Returns document metadata and the version history (version id, number, size, author, date). Does not return a download URL – use clio_document_download.

Inputs: document_id (required).

clio_document_readRead document content (text / scan)A

Returns the content of a Clio document directly in the response – no disk access needed. DOCX/PDF with a text layer/TXT/EML/HTML → text (paginate with offset/max_chars). Scanned PDFs without a text layer and images (JPG/PNG) → returns the pages as images that Claude reads (visual OCR); select pages with page_from/page_to (max 4 per call). mode: auto (default), text (text layer only), images (always page images – e.g. for stamps, signatures, tables). Accepts document_id or file_path.

Inputs: mode, offset, page_to, file_path, +4 more.

clio_document_uploadUpload new document (existing file)A

Uploads a local file as a new document into a matter. Without folder_id the document is stored in the "Claude" folder in the root of the matter's documents (created if it does not exist) – every document created by Claude belongs there. For new letters/filings first use clio_document_create_from_letterhead (letterhead), then this tool. Write operation – preview first, then confirm with the token from the preview.

Inputs: file_path (required), matter_id (required), name, confirm, +2 more.

clio_document_upload_versionUpload new document versionA

Uploads a local file as a new version of an existing document in Clio (previous versions stay in the history). Write operation – preview first, then confirm with the token from the preview.

Inputs: file_path (required), document_id (required), name, confirm.

clio_document_writeRewrite document from text (new version)A

Creates a new version of an existing DOCX document in Clio from the given text (same markdown-lite format as clio_document_create_from_letterhead). The document body is REPLACED by the new text; header, footer and styles are kept (template = the document itself, or base='letterhead' = the current letterhead of the user). Suitable for fixing documents created by Claude; for third-party documents with complex formatting prefer downloading and editing in Cowork. Write operation – preview first, then confirm with the token from the preview.

Inputs: content (required), document_id (required), base, confirm.

clio_expense_createRecord expenseA

Records an expense (ExpenseEntry) on a matter: date, amount (price × quantity), description, optionally expense category. Write operation – preview first, then confirm with the token from the preview.

Inputs: date (required), note (required), price (required), matter_id (required), +4 more.

clio_folder_createCreate folderA

Creates a folder in a matter (parent = Matter) or inside another folder (parent = Folder). Write operation – preview first, then confirm with the token from the preview.

Inputs: name (required), confirm, matter_id, parent_folder_id.

clio_folder_listMatter foldersB

Lists the folders (and optionally documents) in a matter or under a given folder – to find out where to store a document.

Inputs: limit, matter_id, parent_id, include_documents.

clio_letterheads_listLetterheads and templatesA

Lists the document templates (Document Templates) in Clio including letterheads and shows which template will be used for the signed-in user and for internal documents.

Inputs: no named parameters.

clio_line_item_updateUpdate bill line itemA

Updates a bill line item (description, quantity, price, date, note); with update_original_record=true the change is also written back to the original time entry. Write operation – preview first, then confirm with the token from the preview.

Inputs: line_item_id (required), date, note, price, +4 more.

clio_logoutSign out of ClioA

Deletes the tokens stored on this computer. With revoke=true it also asks Clio to invalidate the access token.

Inputs: revoke.

clio_matter_createCreate matterB

Creates a new matter: client (client_id), description, status, billing method, responsible attorney (defaults to the signed-in user), practice area, custom fields. Write operation – preview first, then confirm with the token from the preview.

Inputs: client_id (required), description (required), status, confirm, +9 more.

clio_matter_getMatter detailB

Returns matter detail including client, custom fields, account balances, statute of limitations, relationships and related contacts. Optionally also a summary of unbilled time.

Inputs: matter_id (required), include_unbilled, include_related_contacts.

clio_matter_updateUpdate matterB

Updates a matter: description, status (open/pending/closed), responsible attorney, practice area, custom fields, close date etc. Write operation – preview first, then confirm with the token from the preview.

Inputs: matter_id (required), status, confirm, billable, +7 more.

clio_note_createAdd noteA

Adds a note to a matter or a contact (subject + text). Write operation – preview first, then confirm with the token from the preview.

Inputs: detail (required), subject (required), date, confirm, +2 more.

clio_notes_listMatter / contact notesC

Lists the notes of a matter or a contact, newest first.

Inputs: limit, query, matter_id, contact_id, +1 more.

clio_outstanding_balancesOutstanding client balancesC

Lists clients with outstanding bills: total amount owed, last payment, newest due date, list of outstanding bills.

Inputs: limit, page_token.

clio_practice_areas_listPractice areas and matter stagesA

Lists practice areas and matter stages (for creating/updating matters).

Inputs: no named parameters.

clio_task_createCreate taskB

Creates a task for a matter (or a general one) with a due date, priority and assignee (defaults to the signed-in user). Write operation – preview first, then confirm with the token from the preview.

Inputs: name (required), due_at, confirm, priority, +6 more.

clio_task_listTasksA

Lists tasks by matter, assignee, status, due date (from–to) or text. Default: the signed-in user's incomplete tasks sorted by due date.

Inputs: limit, query, status, complete, +6 more.

clio_task_updateUpdate / complete taskA

Updates a task (name, description, due date, priority, assignee) or changes its status – status=complete marks the task as done. Write operation – preview first, then confirm with the token from the preview.

Inputs: task_id (required), name, due_at, status, +4 more.

clio_text_snippets_listText snippetsC

Lists your firm's text snippets (shortcuts) from Clio – reusable phrases for documents and notes.

Inputs: query.

clio_time_entries_listList time entries and expensesA

Lists time entries (TimeEntry) and optionally expenses by matter, user, period and billing status (unbilled/billed/non_billable/draft). Also returns a summary of hours and amounts for the listed page. Without matter_id and user_id it returns entries for the whole firm – for large periods use limit and page_token.

Inputs: type, limit, query, status, +6 more.

clio_time_entry_createRecord timeB

Records a time entry (TimeEntry) on a matter: date, hours (decimal, e.g. 0.5), note, optionally activity description (activity_description_id), rate (price per hour), user (default: signed-in user), billable/non-billable. Write operation – preview first, then confirm with the token from the preview.

Inputs: date (required), note (required), hours (required), matter_id (required), +7 more.

clio_timerTimerA

Shows the signed-in user's running timer, or starts a new timer on a matter (action=start; creates an in-progress TimeEntry). Stopping: action=stop. Starting/stopping is a write operation – confirm (preview → token).

Inputs: note, action, confirm, matter_id, +1 more.

clio_time_summaryTime summary per matter/periodB

Sums hours and amounts across all time entries by matter, user and period (walks all pages, max. 2000 entries). Broken down by user and billing status.

Inputs: status, user_id, end_date, matter_id, +1 more.

clio_users_listFirm usersA

Lists Clio users (id, name, e-mail, roles, rate) – for assigning tasks and matters and for recording time on behalf of another user.

Inputs: enabled_only.

clio_who_am_iWho am I in ClioA

Returns the signed-in Clio user (id, name, e-mail, roles) and the current rate-limit state. Use it to verify the connection and to find your own user id.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.2/5.0

    Scored across 55 tools

    Disambiguation4/5

    Most tools target distinct resources and actions, with clear separation between matter, contact, document, billing, time, task, and calendar operations. A few areas overlap (document creation/upload/write variants, time entry vs. timer vs. activity update), but descriptions provide enough detail to choose correctly.

    Naming Consistency4/5

    The dominant pattern is clio_<resource>_<action> in snake_case (e.g., clio_matter_get, clio_task_create), applied consistently across most domains. Minor deviations exist, such as clio_activity_update for time entries, clio_who_am_i, clio_describe_api, and clio_outstanding_balances.

    Tool Count2/5

    55 tools is heavy and well above the ideal 3–15 range, risking agent overload and selection difficulty. The breadth of Clio Manage justifies many tools, but the set could likely be consolidated (especially document and lookup tools).

    Completeness3/5

    Core create/read/update coverage is strong across matters, contacts, documents, time, tasks, calendars, notes, and billing. However, delete/removal operations are absent for nearly every resource and DELETE is explicitly disallowed, leaving lifecycle gaps that agents cannot work around.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Connects Claude to Clio practice management, enabling AI-assisted access to matters, contacts, documents, tasks, and billing with audit logging and encryption for law firm compliance.
      356 npm
      28
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables secure access to legal documents from Clio via Claude Desktop, with local processing and semantic search to ground AI responses in actual documents.
      29
      Mozilla Public 2.0
    • F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables Claude (or any MCP client) to read and write Clio Manage data—contacts, matters, activities—directly from chat, with flat-fee billing support in one call.
      -
    • F
      license
      B
      quality
      D
      maintenance
      A standalone MCP server that enables Claude Desktop to manage Clio legal practice matters, documents, billing, and more via ~46 tools, with secure OAuth and audit logging.
      46
      -