MCP Advbox Server
Related Servers
Alternatives to MCP Advbox Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to read, search, and create/edit legal practice management data in Projuris ADV, including cases, people, tasks, updates, timesheet, files, contracts, subjects, court notices, service records, finance, and users via REST.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to read, create, and update legal practice data—cases with history and movements, clients, tasks, and financial transactions—using the firm's API token.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to read and create data in EasyJur legal practice management through the official API, including cases, parties, people, calendar items, opportunities, timesheet, finances, groups, and users. Works with any MCP-over-HTTP client.MIT
- AlicenseAqualityAmaintenanceConnects AI assistants to Brazilian judicial data from DataJud CNJ and 91 courts, enabling process consultation, monitoring, and deadline calculation under the Civil Procedure Code.954 PyPI114MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to read and, on explicit request, create or update legal practice management data through the Clio Manage API, covering matters, contacts, time and expense entries, tasks, communications, document metadata, calendar entries, and bills.Apache 2.0
- AlicenseBqualityDmaintenanceConnects AI assistants to Brazilian judicial data via DataJud CNJ, LexML, and local corpus, enabling process consultation, legal research, and document generation with Visual Law.262MIT
TDQS
Scored across 17 tools
Most tools are clearly distinct by resource and action (e.g., list_customers vs get_customer vs create_customer). The only minor overlap is between get_lawsuit_history and get_lawsuit_movements, but descriptions clarify their different scopes.
All tools follow a consistent advbox_verb_noun pattern, using standard verbs like list, get, create, and update. There are no mixed naming conventions or vague verbs.
17 tools is slightly heavy for a typical server, but it covers multiple entities (customers, lawsuits, tasks, transactions, settings) in a coherent way. Each tool has a clear role, and the count is justified by the broad domain.
Core workflows are covered (create/get/list lawsuits, customers, tasks), but there are gaps: no update or delete for customers and tasks, no transaction detail, and no create/delete for tasks. These omissions could require workarounds but do not break primary use cases.