mycase-mcp

MCP server for MyCase — gives Claude full access to your law firm's MyCase account.

112 tools. One setup command.

What It Does

• Read and manage cases, clients, contacts, and companies
• Create and update tasks, events, and calendar entries
• Log time entries, expenses, and manage invoices
• Access case notes, documents, folders, and custom fields
• Manage leads, lead intake, and referral sources
• Message thread access and call logging
• Webhooks, people groups, practice areas, and more

Requirements

• Python 3.10+
• Python MCP SDK >=2.2,<3 (MCP protocol revision: 2026-07-28)
• A MyCase developer app (see setup below)
• Claude Desktop or any MCP-compatible client

Before You Start — Register the Redirect URI

The OAuth flow uses http://127.0.0.1:8766/callback as the redirect URI. You must register this URI in your MyCase developer app settings before running setup. Without it, authorization will fail.

If you don't have a MyCase developer app yet, contact MyCase support or your account manager to request API access.

Installation

pip install mycase-mcp

Setup (5 steps)

1. Register redirect URI in your MyCase app: http://127.0.0.1:8766/callback

2. Run setup:

   mycase-mcp-setup
   

   Enter your Client ID and Client Secret when prompted. Your browser will open for MyCase authorization.

3. Verify:

   mycase-mcp-verify
   

4. Add to Claude Desktop config (see below)

5. Restart Claude Desktop

Claude Desktop Config

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "mycase": {
      "command": "mycase-mcp"
    }
  }
}

Restart Claude Desktop after saving the config.

Troubleshooting

"No code received" after authorizing in browser → The redirect URI http://127.0.0.1:8766/callback is not registered in your MyCase app. Add it and try again.

Token exchange failed (401) → Double-check your Client ID and Client Secret. Re-run mycase-mcp-setup.

"Missing credentials" on verify → Run mycase-mcp-setup first. Credentials are saved to ~/.mycase-mcp/.

Claude doesn't see the mycase tools → Make sure you restarted Claude Desktop after editing claude_desktop_config.json.

429 Too Many Requests → The server retries automatically (up to 3 times). If it persists, wait a moment and retry.

Credential storage

By default credentials are stored in your operating system's native secret store via the cross-platform keyring library:

OS	Backend
macOS	Keychain
Windows	Credential Manager
Linux	Secret Service (GNOME Keyring / KWallet)

Keyring entries use the service name mycase-mcp.

File fallback. On a host with no keyring backend (e.g. a headless Linux box without Secret Service), or if you set MYCASE_MCP_USE_KEYRING=0, credentials fall back to a ~/.mycase-mcp/.env file with 0600 permissions.

On Windows, the file is stored in the user's profile and protected by Windows' default per-user access rules. On POSIX, files are created with 0600 permissions and writes fail closed if private permissions cannot be established.

Read order. Credentials resolve in the order OS keyring → process environment → .env file. So a rotated secret in the keyring always wins, and a MYCASE_CLIENT_ID / MYCASE_CLIENT_SECRET exported in your shell overrides the file fallback without touching the keyring.

OAuth tokens are stored separately at ~/.mycase-mcp/tokens.json (mode 600) and refreshed automatically on expiry.

Tools

Category	Tools
Identity	who_am_i, get_firm, list_staff, get_staff_member
Cases	list_cases, get_case, create_case, update_case, delete_case, list_cases_for_client, add_client_to_case, add_company_to_case, add_staff_to_case
Clients	list_clients, get_client, create_client, update_client, delete_client, list_client_notes, list_client_message_threads
Companies	list_companies, get_company, create_company, update_company, delete_company, add_client_to_company
Tasks	list_tasks, create_task, update_task, delete_task, assign_task_to_staff
Events	list_events, create_event, update_event, delete_event, add_staff_to_event
Time Entries	list_time_entries, get_time_entry, create_time_entry, delete_time_entry
Invoices	list_invoices, delete_invoice, record_invoice_payment, list_invoice_payments
Expenses	list_expenses, get_expense, create_expense, delete_expense
Notes	get_note, update_note, delete_note, list_case_notes, create_case_note, create_client_note, create_company_note
Documents	list_documents, get_document, update_document, delete_document, list_case_documents, list_document_versions, list_all_document_versions, get_case_folder, upload_document, upload_case_document, upload_document_version, get_document_data, get_document_version_data, delete_document_version
Folders	list_folder_documents, list_folder_subfolders, create_case_subfolder
Leads	list_leads, get_lead, create_lead, update_lead
Calls	list_calls, create_call, update_call, delete_call
Messaging	create_message_thread, create_case_message_thread, post_message
Custom Fields	list_custom_fields, get_custom_field, create_custom_field, delete_custom_field, list_custom_field_options, create_custom_field_option, update_custom_field_option, delete_custom_field_option
Case Reference	list_case_stages, create_case_stage, update_case_stage, delete_case_stage, list_case_roles
Locations	list_locations, create_location, update_location, delete_location
Referral Sources	list_referral_sources, create_referral_source
People Groups	list_people_groups, create_people_group, update_people_group, delete_people_group
Practice Areas	list_practice_areas, create_practice_area, update_practice_area, delete_practice_area
Webhooks	list_webhook_subscriptions, create_webhook_subscription, delete_webhook_subscription

License

MIT

Document paths

upload_document and upload_case_document take a relative MyCase folder/name, including the document name, such as example_folder1/example_folder2/example_name. This is the example in both the case document schema and firm document schema. MyCase creates missing folders and returns a separate upload URL; see the document creation reference. For compatibility, the registered tool description is unchanged; this section specifies the accepted path contract.

Paths may contain ASCII letters, digits, spaces, _, -, ., parentheses and / between segments, up to 1024 characters total and 255 per segment. All URLs (including HTTPS and hostname/path forms), absolute paths, empty or dot segments, leading/trailing segment spaces or dots, backslashes, percent encodings, Unicode and control characters are refused before requests. A filename alone, such as report.pdf, is valid.

Webhook destination allowlist

Set MYCASE_ALLOWED_DESTINATION_HOSTS in the server process environment, for example MYCASE_ALLOWED_DESTINATION_HOSTS=hooks.example.com,.callbacks.example.com. Entries are exact hostnames; a leading dot permits that domain and its subdomains. Matching ignores case and a trailing dot and uses IDNA normalization. Empty or unset configuration refuses webhook registration before any request. This prevents model-supplied URLs from sending firm data to arbitrary destinations, including private-address hostname services and unlisted redirectors. Only administrators can configure this setting; tools cannot change it. List only trusted hosts whose DNS and redirect behavior you control. The existing HTTPS, userinfo, fragment, port, local-name, non-global-IP and encoded/Unicode-host checks still apply. Explicit destination keys in nested objects receive the same validation; unrelated keys are not matched by substring. No DNS lookup or destination fetch is performed.

Updates require at least one supplied field. Verification resolves client credentials through the configured secret store, including keyring-only installations.