MyCase MCP Server — open-source Claude + MyCase integration

The first and only open-source MyCase MCP server. Connect Claude AI directly to your MyCase practice management in five minutes. 18 tools, ABA Opinion 512 audit logging baked in, MIT licensed. On npm and the official Anthropic MCP Registry.

View on GitHub → Book a setup call →
18 tools
cases, contacts, docs, tasks, calendar, billing
ABA 512
append-only audit logging
First OSS
no other MyCase MCP server existed before us

See Claude actually working with MyCase

Watch Claude pull live data from MyCase in under a minute — cases, contacts, documents, calendar — without copying client information into chat.

MyCase MCP — Claude pulls live case data

Cases, contacts, documents, calendar — without copying client information into chat. Every tool call audit-logged.

Three commands, five minutes

1. Install from npm

npm install -g @oktopeak/mycase-mcp

2. Request OAuth credentials from MyCase support, then add to your Claude config

{
  "mcpServers": {
    "mycase": {
      "command": "npx",
      "args": ["-y", "@oktopeak/mycase-mcp"],
      "env": {
        "MYCASE_CLIENT_ID": "your-mycase-client-id",
        "MYCASE_CLIENT_SECRET": "your-mycase-client-secret"
      }
    }
  }
}

Note: MyCase Advanced tier is required because Open API access is gated to that tier. Email MyCase support to request OAuth client credentials for your firm.

3. Inside Claude, run the authenticate tool

Claude runs 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 MyCase cases, contacts, documents, tasks, calendar, calls, staff, time entries, and billing summaries on demand.

Full setup guide on GitHub →

The first open-source MyCase MCP — and the only one with ABA 512 audit logging

ABA 512 audit logging

Every Claude tool call is logged append-only at ~/.oktopeak-mycase/audit.log with timestamp, tool name, arguments, and result. Mapped to ABA Formal Opinion 512 obligations. The artifact a state bar would request.

OS keychain encryption

OAuth tokens encrypted with AES-256-GCM and stored in your OS keychain (macOS Keychain, Linux secret-service, Windows Credential Manager). Auto-generated on first run.

Conservative write scope

Read access across cases, contacts, documents, tasks, calendar, calls, staff, time entries, and billing. Write access scoped to tasks, time entries, and call logging only. No silent mutations to client matters.

There are five paths to integrate Claude with MyCase. Ours is one of them.

Open-source MyCase MCP (this), Clerx AI (intake), Smith.ai (receptionist), Zapier (no-code), custom build. We wrote a frank comparison covering all five — including where each alternative beats ours.

Read the full comparison →

Want to run this with a local LLM instead of consumer Claude?

For firms with maximum confidentiality requirements, the same MyCase 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 →

MyCase MCP Server — frequently asked

What is the MyCase MCP server?

An open-source Model Context Protocol implementation that connects Claude AI (or any MCP-compatible client) directly to MyCase practice management. 18 tools across cases, contacts, documents, tasks, calendar, calls, staff, time entries, and billing. The first and only open-source MyCase MCP connector as of May 2026. Published on npm as @oktopeak/mycase-mcp, listed on the official Anthropic MCP Registry as io.github.oktopeak/mycase-mcp. MIT licensed.

How do I install it?

Three steps: npm install -g @oktopeak/mycase-mcp, request OAuth credentials from MyCase support (Advanced tier required), then add to your Claude Desktop or Claude Code MCP config and call the authenticate tool. Full guide on GitHub.

Does it send my client data to AI training?

No. The server runs locally, talks directly to the MyCase API, and hands results to Claude inside your local session. No data is routed through Oktopeak servers and no data is used to train external models. OAuth tokens are encrypted at rest with AES-256-GCM in your OS keychain.

How is this different from MyCase IQ?

MyCase IQ is a feature inside MyCase Pro and Advanced tiers with pre-configured prompts on a limited task set. The MyCase MCP server gives full Claude capabilities operating on your data with no prompt restrictions, full audit logging, and the ability to combine MyCase with other tools in the same Claude session.

What does it cost?

The connector is free under MIT license. MyCase Advanced tier is required because Open API access is gated to that tier; Claude Pro or Claude API is paid separately. If you want us to deploy it for you with scoped credentials, audit log wired into your stack, and a custom workflow for your team, scope and pricing are tailored to your firm — book a 30-min call to scope it.

Start with the free connector. Hire us if you need help.

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. Book a 30-minute call and we'll scope it together.

Install free from GitHub → Book a setup call →
Book a Call