[ LEGAL TECH ]
We deploy the Clio or MyCase MCP connector in your firm with scoped credentials, audit log destination, a custom workflow designed with your team, and training. ABA Opinion 512 compliant from day one. Scoped to your firm.
ABA 512
audit logging built in
MIT
open-source connector
Production
scoped to your firm
On Clio, MyCase, or Filevine? We deploy those today. On something else? If your practice management, document, or billing system has an API, we can build a connector for it on the same architecture — scoped OAuth, audit logging, encrypted tokens. Tell us your stack and we'll tell you straight what's possible.
[ WHAT WE DELIVER ]
Two short demos from the connectors we ship and deploy. Same architecture, same audit logging, same encryption pattern in every Guided Setup engagement.
Clio MCP — Claude creates matters, books calendar, closes tasks
Active workflow over the Clio API. Read + scoped write. Every tool call logged.
MyCase MCP — Claude pulls live case data
Cases, contacts, documents, calendar — without copying client information into chat.
[ THE PACKAGE ]
[ HOW IT RUNS ]
Fixed scope and fixed price are set in the proposal after the discovery call. Here is the shape of the work.
Phase 1
Phase 2
[ WHY US ]
A weekend demo with Claude is not a production deployment. The gap between the two is where firms get into trouble.
Append-only, every tool call recorded, mapped to ABA Opinion 512 obligations. Not a checkbox — a real log a state bar will accept.
No "all data" tokens. Each connector requests only the scopes the tools actually use. Reviewable, revocable, scoped to the workflow.
Both connectors are MIT-licensed on GitHub. Read the code before you hire us. That is the differentiator. Clio MCP · MyCase MCP
[ WHO YOU'LL TALK TO ]
No SDR, no handoff. The people who built the connectors run the setup. Vet us on LinkedIn first if you like, or follow Oktopeak on LinkedIn.
Every client we lost to a cheaper option came back with a broken codebase and a missed compliance deadline. Ten years of watching the same mistake. So we quote a fixed price, put senior engineers on it, and don't move on until it passes. Regulated software has to work the first time. No second chances with HIPAA.
Co-founder & CEO, Oktopeak
Same pattern everywhere: great companies stuck with bad software options. SaaS that doesn't flex. Agencies that bill hourly and disappear. We built the opposite. Fixed price, compliance-first, shipped. Every project, I'm on the call and in the codebase. That won't change.
Co-founder & Technical Lead, Oktopeak
[ FAQ ]
Guided MCP Setup is a focused engagement to get the open-source connector deployed properly in your firm: scoped OAuth credentials, audit log destination, a custom workflow, and training.
The full Legal AI Integration service covers multi-workflow builds, document automation templates, intake automation, custom AI agents, and full compliance architecture spanning DMS, e-signature, calendar, and billing.
Most firms start with Guided Setup and graduate to the full service later, or skip directly to the full service when scope is already clear. Both are scoped and priced to your firm.
We deploy one connector during the Guided Setup. Pick the one that matters most for your first workflow and we deploy that. The second connector can be added in a follow-up engagement or as part of a graduated Legal AI Integration build.
Often, yes. Guided Setup productizes the Clio, MyCase, and Filevine connectors we already maintain, so those deploy fastest. For any other system — another practice management platform, a document management system, billing, or an internal tool — it comes down to one question: does it expose an API?
If it does, we can build and deploy an MCP connector for it on the same architecture: scoped OAuth, append-only audit logging, and encrypted tokens. Because that is a custom build, it usually runs as a Legal AI Integration engagement rather than the fixed Guided Setup package. Tell us your stack on the call and we will tell you straight what is possible.
Yes. The connector runs as a stdio MCP server on the same machine as the user's MCP client. For firms running a local LLM instead of Claude API or Claude Enterprise, the same connector pairs with LM Studio or Continue.dev to keep all client data on the firm's hardware. We document this pattern in the Privilege Stack guide.
Guided Setup includes selecting the right deployment topology for your firm.
You own the workflow, the audit trail, and the walk-away documentation. Your IT lead and the champion attorney we trained can operate independently. No retainer, no lock-in.
If you want to add workflows or expand to a multi-system integration, the next step is the Legal AI Integration service. If you want to keep operating with what we delivered, you can.
On the discovery call we walk through your stack, your security posture, your AI policy, the workflow you want first, and the team who will use it. We send a fixed-price proposal within five business days.
The scope typically includes:
[ NEED SOMETHING ELSE? ]
Guided Setup is the fastest entry point. If your needs are larger, here's what we build next.
Full AI Integration Build
Multi-tool AI agents for Clio, MyCase, or custom practice stacks. 4–6 weeks.
Custom Legal Software
Case management portals, document pipelines, billing dashboards — built to spec.
Legal Search (Elasticsearch)
100ms semantic search across 1M+ firm documents. On-prem. Like iManage — without the cost.
Software Rescue
Inherited a broken legal platform? Fixed-price rescue with a hard delivery date.
Healthcare Tech
HIPAA-compliant platforms for case managers, brokers, and care coordinators.
About Oktopeak
Seven-person agency. Co-founder-led projects. Every engagement.
[ GET THE CONNECTOR DEPLOYED ]
30-min call with a co-founder. We'll diagnose your stack, propose the workflow, and tell you straight if Guided Setup is the right fit or if you should skip to the full Integration build.
