Skip to main content
Glama
mycase-mcp

mycase-mcp

MyCase MCP server

CI Python 3.11+ License: MIT MCP 2026-07-28 PyPI version

Connect Claude and other MCP clients to MyCase to manage cases, clients, tasks, billing and documents.

MyCase MCP server is a Model Context Protocol server for MyCase, the legal practice management platform. It registers 112 tools that read and write MyCase data. It runs over stdio by default, for desktop clients such as Claude Desktop, and offers an opt-in stateless Streamable HTTP mode that implements MCP specification 2026-07-28. MyCase credentials stay on the machine that runs the server: they come from the setup command and your operating system's keyring, or from environment variables, never from the client.

Features

  • Cases: list, read, create, update and delete cases, and attach clients, companies and staff.

  • Clients and companies: list, read, create, update and delete clients and companies, with their notes.

  • Tasks and events: create, update and delete tasks and calendar events, and assign staff.

  • Time and billing: log time entries and expenses, list invoices and record invoice payments.

  • Documents and notes: upload, read, update and delete documents and versions, browse case folders, and write case, client and company notes.

  • Leads and messaging: list, read, create and update leads, manage referral sources, start message threads, post messages and log calls.

  • Firm setup: manage custom fields, case stages, locations, people groups, practice areas and webhook subscriptions.

Related MCP server: correo-despacho-mcp

Tools

The server registers 112 tools. They cover identity, cases, clients, companies, tasks, events, time entries, invoices and payments, expenses, notes, documents and folders, leads, calls, messaging, custom fields, case stages and roles, locations, referral sources, people groups, practice areas and webhooks. Tools that submit a URL accept only hosts approved in MYCASE_ALLOWED_DESTINATION_HOSTS (see Webhook destination allowlist).

  • add_client_to_case

  • add_client_to_company

  • add_company_to_case

  • add_staff_to_case

  • add_staff_to_event

  • assign_task_to_staff

  • create_call

  • create_case

  • create_case_message_thread

  • create_case_note

  • create_case_stage

  • create_case_subfolder

  • create_client

  • create_client_note

  • create_company

  • create_company_note

  • create_custom_field

  • create_custom_field_option

  • create_event

  • create_expense

  • create_lead

  • create_location

  • create_message_thread

  • create_people_group

  • create_practice_area

  • create_referral_source

  • create_task

  • create_time_entry

  • create_webhook_subscription

  • delete_call

  • delete_case

  • delete_case_stage

  • delete_client

  • delete_company

  • delete_custom_field

  • delete_custom_field_option

  • delete_document

  • delete_document_version

  • delete_event

  • delete_expense

  • delete_location

  • delete_note

  • delete_people_group

  • delete_practice_area

  • delete_task

  • delete_time_entry

  • delete_webhook_subscription

  • get_case

  • get_case_folder

  • get_client

  • get_company

  • get_custom_field

  • get_document

  • get_document_data

  • get_document_version_data

  • get_expense

  • get_firm

  • get_lead

  • get_note

  • get_staff_member

  • get_time_entry

  • list_all_document_versions

  • list_calls

  • list_case_documents

  • list_case_notes

  • list_case_roles

  • list_case_stages

  • list_cases

  • list_cases_for_client

  • list_client_message_threads

  • list_client_notes

  • list_clients

  • list_companies

  • list_custom_field_options

  • list_custom_fields

  • list_document_versions

  • list_documents

  • list_events

  • list_expenses

  • list_folder_documents

  • list_folder_subfolders

  • list_invoice_payments

  • list_invoices

  • list_leads

  • list_locations

  • list_people_groups

  • list_practice_areas

  • list_referral_sources

  • list_staff

  • list_tasks

  • list_time_entries

  • list_webhook_subscriptions

  • post_message

  • record_invoice_payment

  • update_call

  • update_case

  • update_case_stage

  • update_client

  • update_company

  • update_custom_field_option

  • update_document

  • update_event

  • update_lead

  • update_location

  • update_note

  • update_people_group

  • update_practice_area

  • update_task

  • upload_case_document

  • upload_document

  • upload_document_version

  • who_am_i

Prompts and resources

The server also registers three prompts and three read-only resources.

Prompt

What it does

case_status_briefing

Morning briefing of open cases, overdue tasks and pending invoices.

intake_new_client

Intake workflow for a new client: create the client record, the case and the first task. Takes a case_description.

billing_cycle_review

Review unbilled time and outstanding invoices for billing cycle close.

Resource

What it holds

mycase://case_stages

The case stages configured in your MyCase firm.

mycase://practice_areas

The practice areas configured in your MyCase firm.

mycase://security-notes

Security notes for this server, as Markdown.

Requirements

  • Python 3.11+

  • A MyCase developer app with an OAuth Client ID and Client Secret

  • An MCP client such as Claude Desktop

Installation

Install uv, then clone the repository and install its locked dependencies:

git clone https://github.com/RosenAdvertising/mycase-mcp.git
cd mycase-mcp
uv sync --locked

Releases are also published to PyPI: pip install mycase-mcp installs version 0.2.0, which predates the HTTP mode described below. Install from source to use HTTP mode.

Configuration

Register http://127.0.0.1:8766/callback as a redirect URI in your MyCase developer app settings before you run setup. Authorization fails without it. If you do not have a MyCase developer app yet, contact MyCase support or your account manager to request API access.

Run the guided OAuth setup from your clone of the repository:

uv run --locked mycase-mcp-setup

Enter your Client ID and Client Secret when prompted. Your browser opens for MyCase authorization, and setup listens on port 8766 for the redirect. Setup saves the credentials to your operating system's keyring (or the file fallback described under Credential storage) and the OAuth tokens to ~/.mycase-mcp/tokens.json.

Verify the connection:

uv run --locked mycase-mcp-verify

Verify resolves your credentials through the configured secret store, including keyring-only installations, signs in to MyCase, and reads your profile and up to five cases.

The server reads these environment variables. A variable set in the process environment takes precedence over a stored value.

Variable

Required

Default

Purpose

MYCASE_CLIENT_ID

Yes

Stored value from setup

MyCase OAuth client ID.

MYCASE_CLIENT_SECRET

Yes

Stored value from setup

MyCase OAuth client secret.

MYCASE_MCP_USE_KEYRING

No

1

Set to 0 (or false, no, off) to skip the OS keyring and use the .env file fallback.

MYCASE_ALLOWED_DESTINATION_HOSTS

Only for tools that submit a URL

unset

Comma-separated hostnames approved as webhook destinations (see Webhook destination allowlist).

Usage with Claude Desktop

Add the server to Claude Desktop's configuration file (~/Library/Application Support/Claude/claude_desktop_config.json on macOS, %APPDATA%\Claude\claude_desktop_config.json on Windows):

{
  "mcpServers": {
    "mycase": {
      "command": "uv",
      "args": ["run", "--locked", "--directory", "/absolute/path/to/mycase-mcp", "mycase-mcp"]
    }
  }
}

Replace /absolute/path/to/mycase-mcp with the path of your clone. Restart Claude Desktop after saving. Any other stdio MCP client uses the same command and arguments.

HTTP mode

Stdio is the default. Set MYCASE_MCP_TRANSPORT=streamable-http to serve the stateless Streamable HTTP transport from MCP specification 2026-07-28 at /mcp. Each request stands alone: no initialization handshake and no Mcp-Session-Id. Clients on earlier protocol versions are served on the same endpoint.

Security: this endpoint has no authentication and no TLS. Anyone who can reach the port can run every tool, including write and delete tools, with this server's vendor credentials. Keep the default loopback bind (127.0.0.1), or put the server behind an authenticating TLS proxy on a private network. MYCASE_MCP_ALLOWED_HOSTS and MYCASE_MCP_ALLOWED_ORIGINS protect against browser DNS rebinding, not against direct callers. A proxy in front of it needs connection and idle timeouts: a legacy-style GET /mcp with Accept: text/event-stream holds a stream open until the client disconnects.

Variable

Default

Purpose

MYCASE_MCP_TRANSPORT

stdio

stdio or streamable-http. A set but empty value selects stdio.

MYCASE_MCP_HOST

127.0.0.1

Bind address. 127.0.0.1, localhost and ::1 use the SDK's built-in Host and Origin checks; any other value requires MYCASE_MCP_ALLOWED_HOSTS.

PORT

8080

Port; must be an integer.

MYCASE_MCP_ALLOWED_HOSTS

unset

Comma-separated Host header values accepted on a non-loopback bind, such as mcp.example.com:8080 or mcp.example.com:*.

MYCASE_MCP_ALLOWED_ORIGINS

unset

Comma-separated Origin values accepted on a non-loopback bind, such as https://client.example.com. Requests without an Origin header are accepted; with this unset on a non-loopback bind, a request that carries an Origin header is rejected.

MyCase credentials come from the same configuration as stdio (see Configuration), never from the request.

MYCASE_MCP_TRANSPORT=streamable-http PORT=8080 uv run --locked mycase-mcp

Point the MCP client at http://127.0.0.1:8080/mcp.

Error handling

A failed tool call returns an MCP error result (isError) with a fixed message. The server never passes a MyCase response body, a request URL or a credential back to the client.

Situation

What the tool returns

Setup missing or incomplete

"MyCase is not configured. Run mycase-mcp-setup to connect your account and configure the required OAuth credentials, then restart mycase-mcp."

HTTP 401 (after one automatic token refresh)

"The MyCase authorization expired or was rejected. Run mycase-mcp-setup to reauthorize the account."

HTTP 403

"MyCase access denied: the connected account lacks permission for this action (or the authorization expired; re-run mycase-mcp-setup if so)."

HTTP 404

"The requested MyCase record was not found (HTTP 404). Check the record ID."

HTTP 429

"MyCase rate limit reached. Retry after N seconds." N comes from the Retry-After header, or is 10 when the header is missing or unusable.

Other HTTP error statuses

"MyCase API returned HTTP 500: request failed." The reason is one fixed phrase chosen from the error code in the MyCase response: request rejected, authorization rejected, record not found, access denied, rate limited, response was not valid JSON, or request failed for any other code.

Timeout on a read

"MyCase request timed out. Retry shortly."

Connection failure on a read

"Could not connect to MyCase. Check connectivity and retry."

Timeout or connection failure on a write

"MyCase POST request outcome is unknown. Check whether it completed before retrying." (the method is POST, PUT or DELETE as appropriate)

Invalid arguments

A message that names the argument and the shape it expects, such as "Invalid argument 'limit': expected integer between 1 and 200." or "Supply at least one update field."

Destination URL or document path refused

"Destination refused: configure MYCASE_ALLOWED_DESTINATION_HOSTS with trusted comma-separated exact hostnames or .example.com for a domain and its subdomains; the URL host must match." or "Invalid document path: use a safe relative MyCase folder/name ..."

Anything else

Error executing tool <name> with no detail.

Every MyCase request has a 30-second timeout and redirects are not followed. On HTTP 401 the server refreshes the OAuth access token once and repeats the request. On HTTP 429 it waits for the Retry-After period and retries up to 3 times, as long as the waits together stay within 60 seconds; otherwise it returns the rate-limit message. Other failures are not retried.

Missing credentials do not stop the server from starting: each tool call reports them. At startup the server exits with a message and a non-zero status when MYCASE_MCP_TRANSPORT is neither stdio nor streamable-http, when PORT is not an integer, or when a non-loopback MYCASE_MCP_HOST is set without MYCASE_MCP_ALLOWED_HOSTS.

Troubleshooting

Setup prints "Did not receive authorization code" → The redirect URI http://127.0.0.1:8766/callback is not registered in your MyCase app. Add it and run uv run --locked mycase-mcp-setup again.

Setup prints "Token exchange failed (401)" → Check your Client ID and Client Secret, then run setup again.

Verify prints "Missing MyCase client credentials" or "Missing tokens" → Run uv run --locked mycase-mcp-setup first. Tokens are saved to ~/.mycase-mcp/tokens.json; the Client ID and Client Secret go to your operating system's keyring (see Credential storage).

Claude does not show the MyCase tools → Restart Claude Desktop after editing claude_desktop_config.json, and check that the path in the configuration points at your clone.

429 Too Many Requests → The server retries automatically (up to 3 times, see Error handling). 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. A credential already present in the server process environment takes precedence, including one set in your MCP client's configuration. Otherwise the server checks the OS keyring, then the .env file. If you change credentials after the server has loaded them, restart the MCP server to reload the new values.

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

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.

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.

Testing

The test suite runs offline and needs no MyCase account: MyCase API calls are replaced with test doubles. It covers the error messages tools return, argument validation, bounded list controls, path identifiers and document paths, the webhook destination allowlist, the OAuth setup callback and credential storage including private file permissions, logging that omits personal data, the setup and verify command help, MCP specification 2026-07-28 behavior, and the Streamable HTTP transport including Host and Origin checks and stateless requests.

uv sync --locked
uv run --locked pytest -q

CI runs the suite on every push and pull request to main.

License

MIT. See LICENSE.

Available Tools

112 tools
add_client_to_caseC

Add a client to a case with an optional role.

Inputs: case_id (required), client_id (required), role. Returns: result

add_client_to_companyC

Associate a client with a company.

Inputs: client_id (required), company_id (required). Returns: result

add_company_to_caseB

Add a company to a case with an optional role.

Inputs: case_id (required), company_id (required), role. Returns: result

add_staff_to_caseC

Associate a staff member with a case.

Inputs: case_id (required), staff_id (required). Returns: result

add_staff_to_eventB

Add a staff member to a calendar event.

Inputs: event_id (required), staff_id (required). Returns: result

assign_task_to_staffC

Assign a task to a staff member.

Inputs: task_id (required), staff_id (required). Returns: result

create_callC

Log a call. called_at: ISO 8601. call_type: inbound | outbound. call_for_staff_id: staff member the call is for.

Inputs: called_at (required), lead_id, message, resolved, +5 more. Returns: result

create_caseC

Create a case. case_stage: must match an existing stage name. status: open | closed.

Inputs: name (required), status, case_stage, description, +1 more. Returns: result

create_case_message_threadC

Create a message thread on a case. client_ids/staff_ids: comma-separated IDs.

Inputs: case_id (required), subject (required), first_message_body (required), sender_id, +2 more. Returns: result

create_case_noteC

Create a note on a case. All three fields (note body, subject, date ISO 8601) are required.

Inputs: date (required), note (required), case_id (required), subject (required). Returns: result

create_case_stageC

Create a new case stage.

Inputs: name (required). Returns: result

create_case_subfolderB

Create a subfolder within a case. path: relative path, e.g. 'Contracts/2026'.

Inputs: path (required), case_id (required). Returns: result

create_clientC

Create a new client.

Inputs: last_name (required), first_name (required), email, cell_phone_number. Returns: result

create_client_noteC

Create a note on a client. All three fields (note body, subject, date ISO 8601) are required.

Inputs: date (required), note (required), subject (required), client_id (required). Returns: result

create_companyC

Create a new company.

Inputs: name (required), email, website, main_phone_number. Returns: result

create_company_noteC

Create a note on a company. All three fields (note body, subject, date ISO 8601) are required.

Inputs: date (required), note (required), subject (required), company_id (required). Returns: result

create_custom_fieldA

Create a custom field. parent_type: Case|Client|Lead. field_type: text|date|list|checkbox|number. list_options: comma-separated option values for list type fields (e.g. 'Option A,Option B,Option C').

Inputs: name (required), field_type (required), parent_type (required), list_options. Returns: result

create_custom_field_optionC

Add an option to a list-type custom field.

Inputs: field_id (required), option_value (required). Returns: result

create_eventB

Create a calendar event. start/end: ISO 8601. staff_id is required. location_id: ID of a Location record.

Inputs: end (required), name (required), start (required), staff_id (required), +3 more. Returns: result

create_expenseC

Create an expense entry. cost is per-unit cost. entry_date: YYYY-MM-DD.

Inputs: cost (required), activity_name (required), units, case_id, +4 more. Returns: result

create_leadC

Create a new lead.

Inputs: last_name (required), first_name (required), email, cell_phone_number, +1 more. Returns: result

create_locationC

Create a new location.

Inputs: name (required), city, state, country, +2 more. Returns: result

create_message_threadC

Create a message thread. client_ids/staff_ids: comma-separated IDs.

Inputs: subject (required), first_message_body (required), sender_id, staff_ids, +1 more. Returns: result

create_people_groupC

Create a new people group.

Inputs: name (required). Returns: result

create_practice_areaC

Create a new practice area.

Inputs: name (required). Returns: result

create_referral_sourceC

Create a new referral source.

Inputs: name (required). Returns: result

create_taskC

Create a task. priority: Low | Medium | High. due_date: YYYY-MM-DD. staff_id is required.

Inputs: name (required), due_date (required), priority (required), staff_id (required), +2 more. Returns: result

create_time_entryB

Create a time entry. entry_date: YYYY-MM-DD. rate: dollars/hr. hours: decimal hours worked.

Inputs: rate (required), hours (required), case_id (required), staff_id (required), +4 more. Returns: result

create_webhook_subscriptionA

Create a webhook. model: resource type (case|client|company|event|lead|message). actions: comma-separated list of created|updated|deleted (e.g. 'created,updated').

Inputs: url (required), model (required), actions (required). Returns: result

delete_callB

Delete a call log entry by ID.

Inputs: call_id (required). Returns: result

delete_caseC

Delete a case by ID.

Inputs: case_id (required). Returns: result

delete_case_stageB

Delete a case stage by ID.

Inputs: stage_id (required). Returns: result

delete_clientC

Delete a client by ID.

Inputs: client_id (required). Returns: result

delete_companyB

Delete a company by ID.

Inputs: company_id (required). Returns: result

delete_custom_fieldB

Delete a custom field by ID.

Inputs: field_id (required). Returns: result

delete_custom_field_optionC

Delete an option from a list-type custom field.

Inputs: key (required), field_id (required). Returns: result

delete_documentC

Delete a document by ID.

Inputs: doc_id (required). Returns: result

delete_document_versionC

Delete a specific version of a document.

Inputs: doc_id (required), version_number (required). Returns: result

delete_eventB

Delete a calendar event by ID.

Inputs: event_id (required). Returns: result

delete_expenseC

Delete an expense entry by ID.

Inputs: expense_id (required). Returns: result

delete_locationB

Delete a location by ID.

Inputs: location_id (required). Returns: result

delete_noteC

Delete a note by ID.

Inputs: note_id (required). Returns: result

delete_people_groupC

Delete a people group by ID.

Inputs: group_id (required). Returns: result

delete_practice_areaC

Delete a practice area by ID.

Inputs: area_id (required). Returns: result

delete_taskC

Delete a task by ID.

Inputs: task_id (required). Returns: result

delete_time_entryC

Delete a time entry by ID.

Inputs: entry_id (required). Returns: result

delete_webhook_subscriptionA

Delete a webhook subscription by ID.

Inputs: subscription_id (required). Returns: result

get_caseB

Get a case by ID.

Inputs: case_id (required). Returns: result

get_case_folderB

Get the root document folder for a case.

Inputs: case_id (required). Returns: result

get_clientB

Get a client by ID.

Inputs: client_id (required). Returns: result

get_companyC

Get a company by ID.

Inputs: company_id (required). Returns: result

get_custom_fieldC

Get a custom field by ID.

Inputs: field_id (required). Returns: result

get_documentB

Get document metadata by ID.

Inputs: doc_id (required). Returns: result

get_document_dataC

Get the download URL or data for a document's latest version.

Inputs: doc_id (required). Returns: result

get_document_version_dataC

Get the download URL or data for a specific document version.

Inputs: doc_id (required), version_number (required). Returns: result

get_expenseB

Get a specific expense entry by ID.

Inputs: expense_id (required). Returns: result

get_firmA

Get this firm's profile and settings.

Inputs: no named parameters. Returns: result

get_leadB

Get a lead by ID.

Inputs: lead_id (required). Returns: result

get_noteB

Get a note by ID.

Inputs: note_id (required). Returns: result

get_staff_memberC

Get a staff member by ID.

Inputs: staff_id (required). Returns: result

get_time_entryB

Get a specific time entry by ID.

Inputs: entry_id (required). Returns: result

list_all_document_versionsA

List all document versions across the firm.

Inputs: no named parameters. Returns: result

list_callsC

List calls in the firm's call log. updated_after: ISO 8601.

Inputs: page_size, updated_after. Returns: result

list_case_documentsC

List all documents for a case.

Inputs: case_id (required), page_size. Returns: result

list_case_notesC

List all notes for a case.

Inputs: case_id (required), page_size. Returns: result

list_case_rolesA

List all case roles (e.g. plaintiff, defendant, attorney).

Inputs: no named parameters. Returns: result

list_casesC

List cases. status: open | closed.

Inputs: status, page_size. Returns: result

list_cases_for_clientB

List all cases associated with a client.

Inputs: client_id (required), page_size. Returns: result

list_case_stagesA

List all case stages configured in this firm.

Inputs: no named parameters. Returns: result

list_client_message_threadsB

List all message threads for a client.

Inputs: client_id (required), page_size. Returns: result

list_client_notesC

List all notes for a client.

Inputs: client_id (required), page_size. Returns: result

list_clientsB

List clients. Filter by email, first_name, last_name, cell_phone_number, or updated_after (ISO 8601).

Inputs: email, last_name, page_size, first_name, +2 more. Returns: result

list_companiesC

List companies. Filter by name, email, or updated_after (ISO 8601).

Inputs: name, email, page_size, updated_after. Returns: result

list_custom_field_optionsC

List all options for a list-type custom field.

Inputs: field_id (required). Returns: result

list_custom_fieldsA

List all custom fields configured in this firm.

Inputs: no named parameters. Returns: result

list_documentsC

List documents, optionally filtered by case.

Inputs: case_id, page_size. Returns: result

list_document_versionsC

List all versions of a document.

Inputs: doc_id (required). Returns: result

list_eventsC

List calendar events. start_date/end_date: YYYY-MM-DD.

Inputs: case_id, end_date, page_size, start_date. Returns: result

list_expensesB

List expense entries. updated_after: ISO 8601 datetime to filter by last update.

Inputs: page_size, updated_after. Returns: result

list_folder_documentsC

List documents inside a specific folder.

Inputs: folder_id (required), page_size. Returns: result

list_folder_subfoldersC

List subfolders inside a specific folder.

Inputs: folder_id (required). Returns: result

list_invoice_paymentsA

List invoice payments. status: pending|success|failure|error|timeout. payable_id: filter by invoice ID.

Inputs: status, page_size, payable_id. Returns: result

list_invoicesC

List invoices. status: draft | sent | paid | overdue.

Inputs: status, case_id, page_size. Returns: result

list_leadsC

List leads. status: new | contacted | qualified | converted | closed.

Inputs: status, page_size. Returns: result

list_locationsA

List all locations (courthouses, offices, etc.) in this firm.

Inputs: no named parameters. Returns: result

list_people_groupsA

List all people groups (contact categories) in this firm.

Inputs: no named parameters. Returns: result

list_practice_areasA

List all practice areas defined in this firm.

Inputs: no named parameters. Returns: result

list_referral_sourcesA

List all referral sources configured in this firm.

Inputs: no named parameters. Returns: result

list_staffC

List all staff members in this firm.

Inputs: page_size. Returns: result

list_tasksC

List tasks. updated_after: ISO 8601 datetime to filter recently changed tasks.

Inputs: page_size, updated_after. Returns: result

list_time_entriesC

List time entries. updated_after: ISO 8601 datetime to filter by last update.

Inputs: page_size, updated_after. Returns: result

list_webhook_subscriptionsA

List all active webhook subscriptions for this firm.

Inputs: no named parameters. Returns: result

post_messageC

Post a message to an existing message thread.

Inputs: body (required), thread_id (required), sender_id. Returns: result

record_invoice_paymentC

Record a payment against an invoice. date: YYYY-MM-DD (required).

Inputs: date (required), amount (required), invoice_id (required), notes. Returns: result

update_callC

Update a call log entry. resolved: 'true' or 'false' to set resolved status.

Inputs: call_id (required), message, call_for, resolved, +3 more. Returns: result

update_caseC

Update a case's name, status, description, or stage.

Inputs: case_id (required), name, status, case_stage, +1 more. Returns: result

update_case_stageC

Rename a case stage.

Inputs: name (required), stage_id (required). Returns: result

update_clientD

Update a client's details.

Inputs: client_id (required), email, last_name, first_name, +1 more. Returns: result

update_companyC

Update a company's details.

Inputs: company_id (required), name, email, website, +1 more. Returns: result

update_custom_field_optionC

Update an existing option on a list-type custom field.

Inputs: key (required), field_id (required), option_value (required). Returns: result

update_documentC

Update a document's filename or description.

Inputs: doc_id (required), name, description. Returns: result

update_eventC

Update a calendar event.

Inputs: event_id (required), end, name, start, +1 more. Returns: result

update_leadC

Update a lead. status: new | contacted | qualified | converted | closed.

Inputs: lead_id (required), email, status, last_name, +1 more. Returns: result

update_locationC

Update a location's name.

Inputs: location_id (required), name. Returns: result

update_noteB

Update a note's body text, subject, or date. date: ISO 8601.

Inputs: note_id (required), date, note, subject. Returns: result

update_people_groupB

Rename a people group.

Inputs: name (required), group_id (required). Returns: result

update_practice_areaB

Rename a practice area.

Inputs: name (required), area_id (required). Returns: result

update_taskC

Update a task. completed: 'true' or 'false' to set completion status. priority: Low | Medium | High.

Inputs: task_id (required), name, due_date, priority, +1 more. Returns: result

upload_case_documentC

Upload a document directly to a case.

Inputs: path (required), case_id (required), filename (required), description, +1 more. Returns: result

upload_documentC

Upload a new document. path is the file storage path/URL.

Inputs: path (required), filename (required), staff_id, description, +1 more. Returns: result

upload_document_versionC

Initiate a new version upload for an existing document. Returns upload instructions.

Inputs: doc_id (required). Returns: result

who_am_iA

Get the currently authenticated staff member's profile.

Inputs: no named parameters. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    C2.8/5.0

    Scored across 112 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes with detailed descriptions. There is minor potential confusion between generic and entity-specific tools (e.g., create_message_thread vs create_case_message_thread), but overall boundaries are clear.

    Naming Consistency4/5

    The naming convention is predominantly verb_noun (e.g., create_case, list_clients). A few tools like 'who_am_i' and 'add_client_to_case' break the pattern but are still recognizable.

    Tool Count2/5

    With 112 tools, the count is extremely high for an MCP server. While the domain is broad, it exceeds typical scopes (3-15) and can overwhelm an agent's selection process.

    Completeness5/5

    The tool set covers nearly all CRUD operations, relationships, and specialized actions (e.g., document versions, invoice payments, webhooks). No obvious gaps exist for a practice management system.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Connects Claude to Clio practice management, enabling AI-assisted access to matters, contacts, documents, tasks, and billing with audit logging and encryption for law firm compliance.
      265 npm
      27
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to read, search, organize, and optionally send email via IMAP/SMTP for a law firm, with multi-account support and safety locks.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Connects Claude to MyCase legal practice management, enabling natural language queries for cases, contacts, calendar, billing, and more.
      101 npm
      6
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Connects Claude to Lawmatics legal CRM, enabling natural-language queries and management of matters, contacts, pipeline data, tasks, intake forms, and more without leaving the conversation.
      37
      45 npm
      1
      MIT