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.

Demo

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

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",
        "ENCRYPTION_KEY": "your_64_char_hex_key"
      }
    }
  }
}

Restart Claude Desktop and you're done.

Standalone / development

npm install -g @oktopeak/mycase-mcp

Generating an encryption key

Your tokens are stored encrypted on disk. You need to generate a random 32-byte key (64 hex characters) and keep it consistent across restarts — if you change it, you'll need to re-authenticate.

node -e "console.log(require('crypto').randomBytes(32).toString('hex'))"

Copy the output and use it as your ENCRYPTION_KEY.

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

# Generated above
ENCRYPTION_KEY=your_64_char_hex_encryption_key

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

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 and ENCRYPTION_KEY are sensitive credentials. When passed via claude_desktop_config.json, restrict that file's permissions:

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.

OS keychain integration is planned for a future release.

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

... View full README on GitHub