mycase-mcp
Related Servers
Alternatives to mycase-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.22 npm4MIT
- 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
- AlicenseAqualityBmaintenanceConnects 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.3723 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables Claude to read, search, organize, and optionally send email via IMAP/SMTP for a law firm, with multi-account support and safety locks.-
- AlicenseAqualityBmaintenanceEnables Claude to access IntakeQ practice management data including scheduling, intake forms, treatment notes, invoices, and client records with HIPAA-compliant audit logging.2241 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables managing ClickUp workspaces, tasks, comments, time tracking, and docs through Claude, with OAuth and password protection keeping the ClickUp API token server-side.26 npmMIT
TDQS
Scored across 112 tools
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.
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.
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.
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.