LegalAIMCP

Setup guide

How to Connect Claude to Clio via MCP

Cloud-based legal practice management with AI-powered workflows and billing. Clio itself has not shipped an MCP server. Two open-source community servers have, and this guide covers what each does and how to install one.

First: this is not an official Clio product

Unlike CourtListener or Harvey, Clio (Themis Solutions) has not published its own MCP endpoint, install command, or connector documentation. Nothing on this page comes from Clio — both servers below are independent, open-source projects built by third parties against Clio's public API, and neither is built, endorsed, or supported by Clio.

That is a real difference from Harvey, where the setup problem is enrollment. Here, the setup problem is choosing between two working community options and reading their code before you point either one at production client data.

The two servers that connect Claude to Clio

oktopeak/clio-mcp

MIT · maintained by Oktopeak, a legal-tech and healthcare-AI product studio — not Clio

npx -y @oktopeak/clio-mcp
Tools:
36 tools (per its README, v2.2.0) covering matters, contacts, documents, tasks, calendar, billing, and time entries
Auth:
In-app authenticate tool opens a local OAuth flow in your browser; the token is encrypted with AES-256-GCM and stored in your OS keychain (macOS Keychain, Linux secret-service, or Windows Credential Manager)
Transport:
stdio for Claude Desktop/Code, or HTTP/SSE for a shared multi-user deployment
Also:
Built-in append-only audit log (timestamp, tool name, arguments, result) aimed at ABA Opinion 512 compliance; an optional read-only mode disables every write tool

lawyered0/clio-mcp

MIT · maintained by lawyered0 (independent) — not Clio

Tools:
10 tools: clio_who_am_i, clio_create_company_contact, clio_create_person_contact, clio_create_matter, clio_create_flat_fee_activity, clio_find_contact, clio_find_matter, clio_delete_matter, clio_delete_contact, and clio_api_request (a generic escape hatch onto the Clio Manage v4 API)
Auth:
Clio's own OAuth against the v4 API (repo README covers setup)
Transport:
Claude Desktop, Claude Code CLI, and MCP Inspector
Also:
Narrower and newer than oktopeak/clio-mcp; its standout feature is one-call flat-fee matter setup via the custom_rate association, and it supports Clio's US, Canada, EU, and Australia regions

Before you connect either one

  • Read the server's source before installing it — both are MIT-licensed and small enough to review in an afternoon.
  • Start read-only if the server offers it (oktopeak's does).
  • Confirm your firm's policy on third-party tools touching client data in Clio before connecting either server to a production account, not a sandbox.
  • Clio API access depends on your Clio plan — From $39/user/month (EasyStart) to $129/user/month (Complete).

Clio MCP vs. the officially published legal servers

Both Clio servers here are community-maintained, which is a different trust posture than a vendor-published connector. The official CourtListener MCP and Trellis's official Claude connector for state trial court data are both published and operated by the company whose data they expose. If you want to test whether MCP is useful for your practice management workflow specifically, these community servers are the only way in today — just go in knowing who wrote the code. See the full roundup of legal MCP servers for what else is available.

Sources and what we verified

Both repositories, their READMEs, and oktopeak's own setup page at oktopeak.com/clio-mcp were read directly on 24 September 2026, along with the official MCP registry entry for io.github.oktopeak/clio-mcp. Clio's own site was checked the same day for an official MCP announcement; none was found. Pricing, tagline, and vendor details for Clio itself render live from this site's directory listing, so they change when the listing does.

This page will read wrong the day Clio ships its own MCP server, or the day either community server goes stale. If you find either has happened, we would like to hear about it so we can correct the page.

Frequently asked questions

Does Clio have an official MCP server?

No, not as of this writing. Clio's own site and developer documentation do not publish an MCP endpoint, install command, or connector docs. Everything that connects Claude to Clio today is independent, open-source community software — not a Clio product.

Is it safe to connect an unofficial MCP server to my firm's Clio data?

That's a decision for your firm, not a claim we can make for you. Both servers on this page are open source under the MIT license, so you (or your IT person) can read exactly what the code does before installing it, unlike a closed-source connector. Neither is audited, endorsed, or supported by Clio, and installing either grants that server whatever access your Clio OAuth scope allows — read the server's README for its specific permission model before connecting it to production client data.

Which Clio MCP server should I use?

oktopeak/clio-mcp is the broader option — 36 tools, both local and shared-deployment transports, and audit logging aimed at ABA Opinion 512. lawyered0/clio-mcp is smaller and newer, with 10 tools and a specific strength in one-call flat-fee matter setup. Match the tool list to the Clio workflow you actually want Claude to touch, and start with read-only access if either server offers it.

Will Clio publish its own official MCP server?

We don't know, and we won't guess. If Clio publishes one, this page gets rewritten to point at it the same way the Harvey guide would if Harvey did the same. Check clio.com directly for the current state before relying on this page.

See the full Clio listing for current pricing and details, or the best case-management MCP servers for other practice-management options.

A practical next step

Pick one workflow.
Get a plan to improve it.

NYClaw helps scope one intake, document collection, or billing workflow. Start with your existing tools, identify the gaps, and agree a pilot before building.

  • ✓Check built-in features and vendor-supported integrations first
  • ✓Map data access and human review before connecting systems
  • ✓Written scope and fee before paid work begins

Serving law firms in Westchester County, NYC, and remotely nationwide. No commitment required for the initial call.