lawmatics-mcp
Related Servers
Alternatives to lawmatics-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceConnects Claude to MyCase legal practice management, enabling natural language queries for cases, contacts, calendar, billing, and more.21 npm3MIT
- AlicenseNot gradedqualityAmaintenanceConnects 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.363 npm24MIT
- AlicenseCqualityAmaintenanceEnables Claude to access and manage your law firm's MyCase account, including cases, clients, tasks, invoices, and more.1001MIT
- FlicenseBqualityBmaintenanceConnects Claude to your JobNimbus account via API, enabling management of contacts, jobs, notes, and other CRM entities through natural language.19-
- AlicenseAqualityAmaintenanceEnables Claude to connect to your Raynet CRM, allowing you to search records, create leads and business cases, manage your sales pipeline, and perform CRM operations through natural language chat with built-in deletion safeguards.11MIT
- AlicenseNot gradedqualityDmaintenanceConnects Claude to the WhatConverts API, enabling management of leads, accounts, profiles, tracking numbers, and recordings through natural language.MIT
TDQS
Scored across 37 tools
Each tool targets a distinct entity or action, and overlapping categories like find-* vs get-* vs list-* are clearly separated by unique ID, exact match, or filtered listing. No tools appear to do the same thing.
All tool names follow a predictable verb_noun pattern with consistent separators and verbs (get, list, create, update, find, attach, detach, submit). The naming is uniform and easy to infer.
With 37 tools, this server is well over the 25-tool threshold for a heavy surface. While the domain is broad, many reference-data list tools could be consolidated, and the count will overwhelm agents.
Core workflows for matters, contacts, tasks, and forms are covered, but there are notable gaps: no delete for any entity, no create/update for companies, no update/delete for events/notes, and no true pipeline stage movement. These are workable limitations but leave lifecycle coverage incomplete.