MyCase MCP Server

Connect Claude to your MyCase legal practice management system. Ask Claude to look up cases, find contacts, check your calendar, review billing — all without leaving your conversation.

Built by Oktopeak — AI transformation & automation for law firms

Digital transformation for legal and healthcare businesses. We build AI integrations, workflow automation, and custom software your firm owns outright — including this connector. → Book a 30-min call

Jump to: Demo · Installation · Available tools · Security · Need it deployed for you?

Demo

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

Setup tips + ABA Opinion 512 compliance updates for firms building with Claude + MyCase.

→ Subscribe to Oktopeak Builder Notes — short emails, easy unsubscribe.

Related MCP server: clio-mcp

What it does

Once connected, Claude can talk directly to your MyCase firm data. You can ask things like:

• "What open cases do we have for Jane Smith?"

• "Show me all tasks due this week"

• "What's the outstanding balance on the Anderson case?"

• "Log a 20-minute call with client #1234 about the settlement"

• "List documents attached to case 98765"

Everything goes through MyCase's official OAuth 2.0 API. Your credentials never leave your machine — tokens are stored locally, encrypted with AES-256-GCM.

Prerequisites

• Node.js 18+

• A MyCase account with firm admin access

• MyCase API credentials — reach out to MyCase support to request OAuth client credentials for your firm. You'll receive a client_id and client_secret.

Installation

With Claude Desktop (recommended)

Add this to your Claude Desktop config file:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "mycase": {
      "command": "npx",
      "args": ["-y", "@oktopeak/mycase-mcp"],
      "env": {
        "MYCASE_CLIENT_ID": "your_client_id",
        "MYCASE_CLIENT_SECRET": "your_client_secret"
      }
    }
  }
}

Restart Claude Desktop and you're done.

Standalone / development

npm install -g @oktopeak/mycase-mcp

Configuration

If running locally (not via Claude Desktop env vars), copy .env.example to .env and fill it in:

cp .env.example .env

# From MyCase support
MYCASE_CLIENT_ID=your_client_id
MYCASE_CLIENT_SECRET=your_client_secret

# OAuth callback port (default: 5678)
# Must match the redirect URI registered with MyCase support
MYCASE_REDIRECT_PORT=5678

# ENCRYPTION_KEY is optional — a key is auto-generated on first run and
# stored in your OS keychain. Only set this for CI or headless environments.
# ENCRYPTION_KEY=your_64_char_hex_encryption_key

Note: The redirect URI registered with MyCase support must match http://127.0.0.1:{MYCASE_REDIRECT_PORT}/callback. If you're unsure which port was registered, check with MyCase support.

Secret handling

MYCASE_CLIENT_SECRET is the only sensitive credential that needs to live in your config file. The encryption key is managed automatically by the OS keychain — it never appears in any config file.

When using claude_desktop_config.json, restrict that file's permissions so other users on the machine can't read your client secret:

macOS:

chmod 600 ~/Library/Application\ Support/Claude/claude_desktop_config.json

Windows: Right-click the file → Properties → Security → Edit → remove access for all accounts except your own user.

log-call (experimental)

The log-call tool is gated behind an environment variable while its API endpoint is being verified:

MYCASE_EXPERIMENTAL_TOOLS=1

Add this to your claude_desktop_config.json env block or .env file to enable it. Leave it unset to keep it hidden from Claude.

Authentication

The first time you use it, you need to authenticate with MyCase:

1. In Claude, call the authenticate tool

2. Your browser will open the MyCase login page

3. Log in and grant access

4. Return to Claude — you're connected

Access tokens are valid for 24 hours and refresh automatically. Refresh tokens typically last 2 weeks (set by the MyCase API). Once the refresh token expires you'll need to re-authenticate.

Your encrypted token file lives at ~/.oktopeak-mycase/tokens.enc. To log out and remove it, call the logout tool.

Note: If the OS keychain is cleared or the encryption key is lost, the existing token file can no longer be decrypted. The server will silently treat it as absent and you'll need to re-authenticate — no data is lost, just the stored session.

Available tools

Authentication

Cases

Contacts

Tasks

Documents

Calendar

Calls

Staff

Billing

A note on multi-user support

This server is single-tenant by design — it stores one set of credentials at a time and is intended for a single firm running it locally. If you authenticate as a different user, the previous token is overwritten.

If you need multiple firms or users, you'd need to run separate instances with separate configurations.

Development

git clone https://github.com/oktopeak/mycase-mcp.git
cd mycase-mcp
npm install
cp .env.example .env   # fill in your credentials
npm run build
npm run inspect        # opens the MCP inspector in your browser

Running tests

npm test               # run once
npm run test:watch     # watch mode

Security

• OAuth tokens are encrypted at rest using AES-256-GCM

• The encryption key is auto-generated on first run and stored in your OS keychain (macOS Keychain / Linux Secret Service / Windows Credential Manager) — it never appears in any config file

• Token and audit log files are stored in ~/.oktopeak-mycase/ with mode 0600 (owner-read/write only) on Unix/macOS

• On Windows, restrict %APPDATA%\.oktopeak-mycase via folder Properties → Security

• All API calls go directly from your machine to external-integrations.mycase.com

Vulnerability scan

npm audit --omit=dev reports 0 production vulnerabilities. The vitest dev-dependency carries 5 moderate findings (esbuild, vite) that are unreachable in production and require a major vitest version bump to resolve. They have no impact on deployed server instances.

Need more than the connector?

The open-source connector reads your MyCase data and lets Claude work with it. That handles about 20% of what most firms eventually want.

We help two ways, depending on your scope:

→ Guided MCP Setup — We deploy the connector in your firm with scoped credentials, audit log wired into your stack, a custom workflow designed with your team, and training. Scope and pricing tailored to your firm. → oktopeak.com/services/mcp-guided-setup/

→ Legal AI Integration — For multi-workflow builds, document automation, intake automation, custom AI agents, and full compliance architecture across your stack. → oktopeak.com/services/legal-ai-integration/

ABA Opinion 512 compliant from day one. Want a polished overview of this connector with video demo and FAQ? → oktopeak.com/mycase-mcp/

Want to talk first? → Book a 30-min scoping call

Related projects

We ship the same kind of connector for other practice management platforms:

• Clio MCP — open-source MCP connector for Clio practice management. npm: @oktopeak/clio-mcp

• Filevine MCP — open-source MCP connector for Filevine practice management. npm: @oktopeak/filevine-mcp

• IntakeQ / PracticeQ MCP — HIPAA-aware MCP connector for IntakeQ/PracticeQ (healthcare / behavioral & allied-health clinics). Audit logging on every PHI read/write, BAA + Zero-Data-Retention guidance. npm: @oktopeak/intakeq-mcp

Same architecture, same audit logging, same encryption at rest. All MIT licensed.

Supporting this project

This connector is free, MIT licensed, and maintained by Oktopeak. It always will be — we don't take donations. If it saved you time, the things that actually help:

• Star this repo. It is genuinely how other firms find it.

• Tell another firm running MyCase.

• Leave a review if we helped you directly.

• Need it deployed, extended, or maintained for your firm? Commercial support — that is what funds the free work.

Who we are

Oktopeak — digital transformation for law firms and healthcare.

We're a 7-person in-house product team building AI solutions for regulated industries: AI integrations, workflow automation, and custom software our clients own outright. We maintain four open-source MCP connectors — Clio, MyCase, Filevine, and IntakeQ — and deploy them inside real practices with scoped credentials, audit logs, and workflows built around how your team actually works.

• 🌐 oktopeak.com

• 📅 Book a 30-min call

• ✉️ office@oktopeak.com — security reports welcome

• 💼 LinkedIn

License

MIT — see LICENSE.

Built with the Model Context Protocol SDK by Anthropic.