Open-source connector, professionally deployed

Guided MCP Setup
for law firms

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.

Book a 30-min setup call → Read the source on GitHub

30 min with a co-founder. No sales pitch.

ABA 512
audit logging built in
MIT
open-source connector
Production
scoped to your firm
What we deliver

This is what your setup looks like when we are done

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

Three things you walk away with

What's included
  • Deploy the Clio or MyCase MCP connector in your firm's environment
  • OAuth credentials configured at the right scope
  • Audit log destination wired into your stack
  • A custom workflow designed with your team
  • Train your IT lead and one champion attorney
  • Walk-away documentation
Who it's for
  • Firms who installed the open-source connector and got stuck
  • Firms whose IT does not yet speak MCP
  • Partners who want to test AI before committing to a full build
  • Anyone who wants production-ready, not a weekend demo
What you keep
  • Full ownership of the workflow and the audit trail
  • Walk-away documentation your team can operate
  • No retainer, no lock-in, no surprise renewal
  • Scale to a full build later if you want, no obligation
How it runs

Two phases, scoped to your firm

Fixed scope and fixed price are set in the proposal after the discovery call. Here is the shape of the work.

Phase 1

Deploy and configure

  • Discovery call with your IT lead and champion attorney
  • Environment audit — your stack, your security posture, your AI policy
  • Connector deployed in your environment (stdio or HTTP transport, your call)
  • OAuth credentials configured at the right scope
  • Audit log destination wired in — local file, shared drive, or SIEM
Phase 2

Workflow and handoff

  • A custom workflow designed with your team (intake summary, matter timeline, deadline tracking, you pick)
  • Workflow tested against real matters in your environment
  • Training session for your IT lead and one champion attorney
  • Walk-away documentation handed off
  • 30-day post-handoff email support for setup questions
Why us

We built the connector. We know what production looks like.

A weekend demo with Claude is not a production deployment. The gap between the two is where firms get into trouble.

Audit logging that survives a bar audit

Append-only, every tool call recorded, mapped to ABA Opinion 512 obligations. Not a checkbox — a real log a state bar will accept.

OAuth scopes minimized

No "all data" tokens. Each connector requests only the scopes the tools actually use. Reviewable, revocable, scoped to the workflow.

Source-available proof

Both connectors are MIT-licensed on GitHub. Read the code before you hire us. That is the differentiator. Clio MCP · MyCase MCP

FAQ

Guided MCP Setup — 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.

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:

  • A discovery session with your IT lead and champion attorney
  • OAuth credentials configured at the right scope for your firm
  • Audit log destination wired into your stack so ABA Opinion 512 logging is satisfied from day one
  • A custom workflow designed and tested with your team
  • Training for your IT lead and one champion attorney
  • Walk-away documentation

Let's scope your deployment.

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.

→

Prefer email? office@oktopeak.com

Book a Call