Why this comparison matters
Claude without MCP means copy-paste. A lawyer pastes a matter document into the chat window, gets a summary, moves on. In March 2026, a New York federal district court ruled that information entered into publicly available AI platforms is not protected by attorney-client privilege. Firms that built workflows around paste-into-Claude are now sitting on an exposure problem they didn't know they had.
Claude with MCP changes the shape. An MCP server reads data directly from Clio's API and hands results to Claude in your local session. Nothing goes to training. Nothing leaves your infrastructure. The difference is architectural, not cosmetic.
Four open-source connectors currently exist. Each solves part of the problem. None are identical. If you install the wrong one, you either miss capabilities you needed or carry risk you thought you avoided.
Side-by-side feature comparison
Data verified against each repository's README as of April 24, 2026.
| Feature | LegalContext | lawquarter | LegalMCP | Oktopeak |
|---|---|---|---|---|
| Tool count | 5 | ~6 | 18 | 12 |
| Matters | — | ✓ | ✓ | ✓ |
| Contacts | — | — | ✓ | ✓ |
| Documents | ✓ | — | ✓ | ✓ |
| Tasks | — | ✓ | ✓ | ✓ |
| Calendar | — | — | ✓ | ✓ |
| Billing (read) | — | — | partial | ✓ |
| Notes / Activities | — | ✓ | — | ✓ |
| ABA 512 audit logging | — | — | — | ✓ |
| Encrypted tokens at rest | — | env-var only | — | ✓ |
| License | MPL-2.0 | not listed | MIT | MIT |
| Language | TypeScript | — | Python | TypeScript |
| GitHub stars (Apr 2026) | 24 | — | 41 | ships Apr 30 |
| Jurisdiction focus | Global | Australia | US (with CourtListener/PACER) | Global |
| Bundles non-Clio sources | — | — | CourtListener + PACER | — |
1. LegalContext (protomated/legal-context-ce)
github.com/protomated/legal-context-ce — TypeScript, MPL-2.0, 24 stars as of April 2026.
What it does. Semantic document search over your Clio document library. Uses LanceDB to build a local vector index of documents and enables Claude to search them via natural language queries. Core tools: auth:simple (OAuth flow), index:batch (index documents), check:clio (verify connection), test:extraction, reset-index-tracking.
Clio scope. Documents and folders only. OAuth scopes requested are limited to documents and folders. The README explicitly does not support matters, contacts, tasks, calendar, billing, or any other Clio resource.
Compliance. Emphasizes local processing and no cloud dependencies. Tracks queries via a local counter (for enforcing the free tier's 50-query-per-day limit) but does not implement formal append-only audit logging aligned with ABA Opinion 512 requirements.
Known limitations. The free tier caps at 100 indexed documents and 50 queries per day. Designed as a single-user tool, not a firm-wide deployment. If your firm has more than 100 documents (essentially every firm), you either pay for the commercial tier or you hit the ceiling.
Who it fits. A solo attorney or very small firm wanting Claude to find documents inside Clio's document storage. If document search is 100% of what you want from Claude + Clio, this works within its cap.
2. lawquarter/MCP_Server_Clio
Listed on Glama, Awesome MCP Servers, and mcpservers.org. Still maintained as of March 2026 per directory listings. Limited public README; details drawn from directory metadata.
What it does. Enables Australian legal professionals to access matters, tasks, notes, and activities through natural language via Claude. Roughly six tools spanning those four resource types.
Clio scope. Matters, tasks, notes, activities. Does not cover documents, contacts, calendar, or billing. Uses environment variables for Clio OAuth credentials and an encryption key configured in a .env file — so tokens can be encrypted, but the encryption is user-managed rather than baked in.
Compliance. The listing notes the project "is not endorsed or sponsored by Clio" and that users bear responsibility for jurisdictional data protection compliance. No explicit ABA Opinion 512 alignment. No published audit-logging mechanism.
Known limitations. Built specifically for the Australian Clio endpoint. US, EU, and Canada firms will need to reconfigure or fork to point at their regional API. No support for document access or billing. License not clearly published on directory listings.
Who it fits. An Australian firm that wants Claude to manage matter-level activity (tasks, notes, activity logs) without touching documents or billing. Jurisdiction is a hard constraint.
3. LegalMCP (Mahender22/legal-mcp)
github.com/Mahender22/legal-mcp — Python, MIT, 41 stars and 13 forks as of April 2026.
What it does. Combines Clio practice management with US case law research. 18 total tools split across three domains: 7 Clio tools (clients, matters, matter details, time entries, matter tasks, matter documents, calendar), 8 CourtListener tools (4M+ US court opinions), and 3 PACER tools (federal court filings).
Clio scope. Search clients, search matters, get matter details, get time entries, get matter tasks, get matter documents, get calendar. No notes, activities, billing summaries, or write operations.
Compliance. Notes "your data stays on your machine" and supports local operation. No audit logging, no encryption of OAuth tokens at rest, no explicit ABA Opinion 512 alignment in the README. Demo mode available without API keys.
Known limitations. PACER downloads cost $0.10/page; the tool doesn't auto-download paid documents, which avoids runaway charges but means some filings require manual fetching. The bundling of CourtListener and PACER is useful for litigators but irrelevant (and adds complexity) for firms that only want Claude + Clio.
Who it fits. A US litigation-focused firm that wants Claude to pull practice-management data and case law in the same conversation. If you're regularly pulling opinions from CourtListener and filings from PACER alongside matter details, the bundling saves installation steps.
4. Oktopeak's Clio MCP Connector
github.com/oktopeak/clio-mcp — TypeScript, MIT. Launching April 30, 2026.
What it does. The most complete Clio coverage of any open-source MCP connector. 12 tools across 7 Clio resource areas: matters, contacts, documents, tasks, calendar, billing, and notes. Read operations across all seven. Limited write operations scoped deliberately to tasks and notes only, to minimize liability.
Clio scope. List and get matters (by status). Search contacts by name, email, or company. List documents in a matter or folder, get document metadata and download URLs. List tasks by matter, status, or date. Create tasks with priority, due date, and assignee. List calendar entries in a date range. List time entries with date filtering. Get billing summaries for a matter (read-only). Create notes on matters with an optional sensitivity flag. Expose auth status and a compliance notice as MCP resources.
Compliance. This is the differentiator. Every Claude-initiated interaction writes an append-only entry to a local audit log at ~/.oktopeak-clio/audit.jsonl. Minimum fields: timestamp, tool name, input parameters, result count or success flag, Clio user ID. This satisfies ABA Opinion 512's requirement that AI interactions with client data be logged and retrievable. OAuth tokens are encrypted at rest using AES-256. The connector exposes a clio://compliance/info resource that MCP clients display at session start as a privilege reminder.
Known limitations. stdio transport only in v1 (not hosted / HTTP). Single firm, single user per installation. No writes on matters, contacts, documents, calendar, or billing. No bundled non-Clio sources. Requires a Clio developer account and OAuth app registration (5-minute setup).
Who it fits. Any firm in any jurisdiction that wants comprehensive Clio access for Claude and needs ABA Opinion 512-aligned audit logging from day one. Built for US firms worried about the post-2026 privilege rulings, Australian and EU firms that need regional flexibility, and any firm that takes compliance as a first-class architectural concern rather than a checkbox.
Decision framework: which one do you install?
Short answer by use case:
You need document search only, and your firm has fewer than 100 documents. LegalContext is fine. Install, index, done. If you cross 100 documents, you need the commercial tier or a different tool.
You're an Australian firm that wants matter/task/activity management without documents or billing. lawquarter was built for you. Just verify the jurisdiction setup matches your Clio region.
You're a US litigation firm and you want Claude to pull practice management data alongside CourtListener opinions and PACER filings. LegalMCP saves you installing three separate connectors. Accept the lack of audit logging and plan to add it yourself.
You need complete Clio coverage with ABA 512 compliance baked in, or you operate outside Australia, or you cannot tolerate missing audit logs. Oktopeak's connector. Launches April 30, 2026.
Can you run multiple connectors? Technically yes. In practice, installing two Clio MCP servers in the same Claude Desktop creates tool-naming collisions (both expose list-matters), unpredictable behavior when Claude picks which to call, and a fragmented audit trail across different storage formats. Pick one.
The compliance question nobody is asking
ABA Formal Opinion 512 (July 2024) is the first comprehensive national AI ethics guidance for US lawyers. Among its requirements: lawyers must log AI interactions, verify AI output, evaluate vendor data handling practices, and maintain records that are retrievable under state bar review.
Of the four connectors surveyed, three lack explicit audit logging. If you install one of those and a state bar or judge later asks you to produce logs of AI interactions with client data, you have two choices: explain why you have no logs, or reconstruct from memory. Neither is a good position.
This isn't hypothetical. In March 2026, the Southern District of New York ruled that information entered into consumer AI platforms falls outside attorney-client privilege. Regulators and bar associations are now focused on how AI interacts with privileged material. An audit log isn't a nice-to-have — it's the evidence you preserved privilege properly.
The audit logger is a small file. A few dozen lines of code. Writing one into your fork of any of these connectors is not hard. But if you don't, you ship without it, and the exposure lives on the firm's side, not the tool's.
Building compliance in from day one is what we sell. We'd rather ship it in an open-source connector everyone can use than keep the pattern proprietary.
What the open-source connector doesn't do
Even the most complete connector is an input layer. It lets Claude read and touch Clio. What it doesn't do:
- Document automation templates. Claude can read a matter, but it can't draft a retainer agreement from your firm's template library without someone building that workflow. That's design work, not integration work.
- Intake automation. The connector reads Clio. It doesn't decide how new leads become matters, route them by practice area, or pre-populate intake forms. Someone has to design that pipeline.
- Custom AI agents. "Write me a memo with these citations" is a prompt. "Pull all matters where statute of limitations expires in 60 days and draft a client reminder" is a workflow. The latter requires orchestration on top of the connector.
- Multi-system compliance architecture. Most firms don't only use Clio. Document management systems, e-signature tools, calendars, billing exports to QuickBooks — integrating Claude across that stack with consistent audit logging and access controls is architectural work.
The open-source connector handles roughly 20% of what most firms want from Claude + Clio. The remaining 80% is implementation: workflows, templates, intake pipelines, and the compliance architecture that ties it together.
Need the other 80%?
Document automation, intake workflows, custom AI agents, and full compliance architecture — 4 to 6 weeks, fixed price, ABA Opinion 512 compliant from day one.
See Our Legal AI Integration Service →Data in the comparison table verified against each connector's public GitHub repository and directory listings as of April 24, 2026. Features and star counts change; we'll update this post at the first of each month. If you maintain one of the connectors and a detail here is incorrect, email office@oktopeak.com and we'll correct it.