AdvBox
Server Details
Wrapper for the official AdvBox API (legal practice management): cases (with history, movements, pub
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- mcp-dir/advbox-mcp
- GitHub Stars
- 0
- Server Listing
- AdvBox
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 26 tools
The advbox_* tools map to clearly distinct resources and actions (customers, lawsuits, movements, posts, transactions, settings), so an agent can usually pick correctly. The main soft spot is the trio advbox_lawsuit_history / advbox_lawsuit_movements / advbox_last_movements, whose boundaries between 'full history', 'all movements' and 'recent summary' are not immediately obvious; the platform tools (connect, toolkit_info, show_version) also overlap mildly in what they report about the account.
All domain tools share a predictable advbox_ snake_case prefix with mostly verb_noun shape (create_customer, get_lawsuit, list_transactions, update_transaction). Minor deviations exist where the noun comes first or the verb is absent (advbox_customers_birthdays, advbox_settings, advbox_publications, advbox_last_movements), and the six platform tools carry no prefix at all, but the overall convention is readable and stable.
At 26 tools the surface is heavy for a single integration, and roughly six of them (authenticate, connect, marketplace, report_bug, show_version, toolkit_info) are generic platform plumbing rather than AdvBox operations, which inflates the list an agent must sift through. The ~20 domain tools themselves are reasonably earned given the breadth of customers, lawsuits, movements, posts and finance, so this is borderline rather than badly over-scoped.
Read/create/update are covered for lawsuits and transactions, and reads are covered for customers, but there is no delete or archive operation anywhere in the set, and customers and posts lack update tools (posts have create + list only, no get/update/delete). These are notable lifecycle gaps that will force workarounds, though the core read and creation workflows a legal-practice agent needs are present.
Available Tools
26 toolsadvbox_create_customerAInspect
Cria um novo contato/cliente. Campos conforme a API oficial (ex.: name, type, cpf/cnpj, email, phone) — envie o restante via extra.
Inputs: cpf, cnpj, name, email, +1 more.
advbox_create_lawsuitAInspect
Cria um processo. Campos conforme a API oficial (use advbox_settings para descobrir IDs de tipo/responsável); envie via campos nomeados + extra.
Inputs: extra, number.
advbox_create_movementCInspect
Adiciona uma movimentação manual a um processo. Vincule ao processo (campo conforme a API oficial) + descrição; demais campos via extra.
Inputs: extra, description.
advbox_create_postBInspect
Cria um novo post/anotação. Campos conforme a API oficial via campos nomeados + extra.
Inputs: text, extra.
advbox_create_transactionBInspect
Cria um lançamento financeiro (receita ou despesa). Obrigatórios: entry_type, amount, date_due, categories_id, debit_account, cost_centers_id e users_id (IDs em advbox_settings).
Bulk support: accepts categories_ids, cost_centers_ids, users_ids, customers_ids, lawsuits_ids for batched execution.
Inputs: type, extra, value, amount, +16 more.
advbox_customers_birthdaysARead-onlyIdempotentInspect
Lista aniversariantes (para campanhas de relacionamento).
Inputs: page, query, page_size.
advbox_get_customerARead-onlyIdempotentInspect
Busca os dados completos de um contato por ID.
Bulk support: accepts ids for batched execution.
Inputs: id (required), ids, query.
advbox_get_lawsuitARead-onlyIdempotentInspect
Busca um processo por ID (dados completos).
Bulk support: accepts ids for batched execution.
Inputs: id (required), ids, query.
advbox_get_transactionARead-onlyIdempotentInspect
Detalha uma transação por ID.
Bulk support: accepts ids for batched execution.
Inputs: id (required), ids, query.
advbox_last_movementsCRead-onlyIdempotentInspect
Última atualização de cada processo (resumo recente).
Inputs: page, query, page_size.
advbox_lawsuit_historyBRead-onlyIdempotentInspect
Histórico completo de um processo.
Bulk support: accepts lawsuit_ids for batched execution.
Inputs: lawsuit_id (required), page, query, page_size, +1 more.
advbox_lawsuit_movementsBRead-onlyIdempotentInspect
Lista todas as movimentações de um processo.
Bulk support: accepts lawsuit_ids for batched execution.
Inputs: lawsuit_id (required), page, query, page_size, +1 more.
advbox_list_customersBRead-onlyIdempotentInspect
Lista clientes/contatos com filtros avançados (nome, cpf, cnpj, e-mail etc. via query).
Inputs: cpf, cnpj, name, page, +3 more.
advbox_list_lawsuitsARead-onlyIdempotentInspect
Lista/busca processos (22+ filtros). Filtros comuns via query: numero, parte, cpf, cnpj, responsavel, status, comarca, uf, datas.
Inputs: cpf, cnpj, page, query, +3 more.
advbox_list_postsBRead-onlyIdempotentInspect
Lista posts e anotações (tarefas/notas).
Inputs: page, query, page_size.
advbox_list_transactionsARead-onlyIdempotentInspect
Lista transações financeiras com filtros de data/tipo/status (via query).
Inputs: page, type, query, status, +3 more.
advbox_publicationsARead-onlyIdempotentInspect
Lista as publicações oficiais de um processo.
Bulk support: accepts lawsuit_ids for batched execution.
Inputs: lawsuit_id (required), page, query, page_size, +1 more.
advbox_settingsARead-onlyIdempotentInspect
Obtém todos os IDs e configurações da conta (usuários, origens, tipos de tarefa, fases, tipos de processo). Use para descobrir os IDs exigidos por create/update.
Inputs: query.
advbox_update_lawsuitAInspect
Atualiza um processo existente por ID. Envie só os campos a alterar (nomeados + extra).
Bulk support: accepts ids for batched execution.
Inputs: id (required), ids, extra.
advbox_update_transactionCInspect
Atualiza uma transação por ID. Envie só os campos a alterar: amount, date_due e date_payment (AAAA-MM-DD), description; entry_type é obrigatório junto com categories_id.
Bulk support: accepts ids for batched execution.
Inputs: id (required), ids, extra, value, +2 more.
authenticateAIdempotentInspect
MCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header Authorization: Bearer <token> for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "" } after the user pastes, or with no args to get the link.
Inputs: token.
connectARead-onlyIdempotentInspect
Returns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.
Inputs: no named parameters.
marketplaceAInspect
The official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin. It also carries the mcp.ai PROMPT LIBRARY, which is about ready-made prompt TEXT rather than MCPs: search_prompts finds one, get_prompt returns its full text with {{variables}} filled, and publish_prompt saves a prompt and returns a shareable mcp.ai/p/ link that opens without login.
Inputs: limit, query, action, mcp_id, +19 more.
report_bugAIdempotentInspect
Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.
Inputs: message (required), context, conversation.
show_versionARead-onlyIdempotentInspect
Show the current MCP platform and adapter versions.
Inputs: no named parameters.
toolkit_infoARead-onlyIdempotentInspect
Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Wrapper for the official Projuris ADV REST API (legal practice management): cases, people (clients/p
Wrapper for the official EasyJur API (legal practice management): cases (with parties, claims, finan
Wrapper for the official LegalOne API (Thomson Reuters / Novajus, Premium package): lawsuits and lit
USPTO PTAB MCP — wraps the USPTO Open Data Portal (ODP) PTAB APIs
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables AI agents to interact with the Advbox legal management system, supporting operations on clients, lawsuits, tasks, and financial transactions.172MIT
- FlicenseNot gradedqualityCmaintenanceEnables querying Brazilian judicial case data through CNJ public APIs: fetching case metadata and movements via DataJud, searching publications and intimations from the national electronic justice gazette (DJEN) by case number or OAB, and downloading publication certificates as PDFs.-
- AlicenseNot gradedqualityCmaintenanceEnables querying public Brazilian court proceedings metadata and movements via the CNJ/DataJud API, covering multiple courts.4MIT
- AlicenseNot gradedqualityDmaintenanceEnables 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
Glama MCP Gateway
Add one secure layer between your agents and this server.