[ OPEN-SOURCE · MIT · ABA 512 ]
The first open-source Clio MCP server with ABA Opinion 512 audit logging built in. Connect Claude AI directly to your Clio practice management in five minutes. MIT licensed. On npm and the official Anthropic MCP Registry.
26 tools
matters, contacts, docs, tasks, calendar, billing
ABA 512
append-only audit logging
5 min
install with your Clio credentials
[ LIVE DEMO ]
Two short clips. The first shows Claude reading live case data, creating matters, booking calendar events, and closing tasks. The second is the install walkthrough.
Workflow demo
Claude creates matters, books calendar events, and closes tasks in Clio. Read + scoped write. Every tool call audit-logged.
Install walkthrough
From npm install to authenticated Claude session with live Clio data. Roughly five minutes.
[ QUICK INSTALL ]
1. Install from npm
npm install -g @oktopeak/clio-mcp2. Add to your Claude Desktop or Claude Code MCP config
{
"mcpServers": {
"clio": {
"command": "npx",
"args": ["-y", "@oktopeak/clio-mcp"],
"env": {
"TRANSPORT": "stdio",
"CLIO_CLIENT_ID": "your-clio-client-id",
"CLIO_CLIENT_SECRET": "your-clio-client-secret"
}
}
}
}3. Inside Claude, run the authenticate tool
Claude calls the local OAuth flow, you confirm in your browser, the token gets encrypted at rest in your OS keychain, and the connector is ready. From this point Claude can read your Clio matters, contacts, documents, tasks, calendar, and billing data on demand.
[ WHAT MAKES OURS DIFFERENT ]
Every Claude tool call is logged append-only with timestamp, tool name, arguments, and result. Mapped to ABA Formal Opinion 512 obligations out of the box. Not a checkbox — a real log a state bar would accept.
OAuth tokens encrypted with AES-256-GCM and stored in macOS Keychain, Linux secret-service, or Windows Credential Manager. Never plaintext. Never on our servers.
Single-user stdio for Claude Desktop. Multi-session HTTP/SSE for shared deployment. Same tool surface either way. Choose the transport that fits your firm's setup.
[ OTHER CLIO MCP OPTIONS ]
If you're evaluating options, we wrote a frank feature-by-feature comparison covering LegalContext, lawquarter, LegalMCP, and ours. Yes, we placed ours first — and we explain where each alternative wins.
Read the full comparison[ PRIVILEGE-SAFE DEPLOYMENT ]
For firms with maximum confidentiality requirements, the same Clio MCP server pairs with LM Studio or Continue.dev running a local model on your hardware. No data leaves your firm. Full guide is the Privilege Stack post.
Read the Privilege Stack guide[ FAQ ]
@oktopeak/clio-mcp, listed on the official Anthropic MCP Registry as io.github.oktopeak/clio-mcp. MIT licensed.npm install -g @oktopeak/clio-mcp, add the server entry to your Claude Desktop or Claude Code MCP config with your Clio API credentials, then call the authenticate tool inside Claude to complete the local OAuth handshake. Full guide on GitHub.[ GET STARTED ]
Two paths: install the OSS yourself (free, MIT, on GitHub), or have us deploy it in your firm with scoped credentials, audit log destination, and a workflow designed with your team.