Integration

ADVBOX integration

ADVBOX is a Brazilian law-practice management system. Manage the office's contacts (clients and parties), lawsuits (create, read, update, with their tasks, court movements and publications), tasks assigned to the team, income and expense entries, and attached documents (list them and get a 5-minute download link). get_settings returns the account's users, contact origins, task types, procedural stages, lawsuit types, bank accounts, categories, cost centers and departments, whose ids the other tools need. Contacts come back without their CPF/CNPJ, document, CTPS, PIS and CID (health) numbers, which stay usable as search filters and on creation. ADVBOX issues the access token itself, on request: to offices that buy its API plan and to approved partners. It is sent as a Bearer token. Limits per account: 30 reads per minute, 500 creations per day per route and 500 updates per day. Every documented route is exposed; the API has no delete routes.

Connect ADVBOX How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in ADVBOX.Built from the 22 ADVBOX tools below, on the connection you add once.

Common ADVBOX use cases

fetching a petition PDF attached to a task

What you can do with ADVBOX

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Lawsuit, 4 operations

create_lawsuitCreate lawsuitPOSTAgents: ask firstCreates a lawsuit in the office's account and returns its lawsuits_id. Needs users_id, customers_id (at least one contact), stages_id and type_lawsuits_id, all from the office (get_settings, list_customers). Group and step are derived.
get_lawsuitGet lawsuitGETAgents: ask firstReturns one lawsuit by id: CNJ and protocol numbers, folder, fees, type and group, stage and step, responsible user, linked contacts and closing dates. An unknown id returns 404 Lawsuit not found.
list_lawsuitsList lawsuitsGETAgents: ask firstLists the office's lawsuits with filters combined with AND; returns totalCount and data with each lawsuit's type, stage, responsible user and contacts. Date filters are ranges: send both _start and _end.
update_lawsuitUpdate lawsuitPUTAgents: ask firstChanges the fields sent on one lawsuit; fields left out stay unchanged. Send an empty string to clear process_number or a closing date. An id outside the account is refused with 422.

Transaction, 4 operations

create_transactionCreate transactionPOSTAgents: ask firstRecords an income or expense entry in the office's finances and returns its transactions_id. Take the ids from get_settings. amount is a string with a comma decimal separator, for example 250,50.
get_transactionGet transactionGETAgents: ask firstReturns one income or expense entry by id: amount, type, category, bank account, cost center, department, due and payment dates and the linked lawsuit and client ids. An unknown id returns 404.
list_transactionsList transactionsGETAgents: ask firstLists the office's income and expense entries with filters combined with AND. Text filters match partially; dates are ranges (send both _start and _end); competence uses MM/YYYY.
update_transactionUpdate transactionPUTAgents: ask firstChanges the fields sent on one income or expense entry, for example marks it paid with date_payment; fields left out stay unchanged. Changing categories_id needs entry_type in the same call.

Customer, 3 operations

create_customerCreate customerPOSTAgents: ask firstCreates a contact in the office's ADVBOX account and returns its customers_id. Needs users_id (get_settings users) and customers_origins_id (get_settings origins). A contact with the same name, or a CPF/CNPJ already used, is refused.
get_customerGet customerGETAgents: ask firstReturns one contact by id with its linked lawsuits (personal data); text fields come back in upper case and the birth date as DD/MM/YYYY. An unknown id returns 404 Customer not found.
list_customersList customersGETAgents: ask firstLists the office's contacts (clients, parties and related people; personal data) with filters combined with AND; returns totalCount and data. name matches any part of the name; email, city, state, document and occupation match exactly.

Task, 2 operations

create_taskCreate taskPOSTAgents: ask firstCreates a task on a lawsuit and assigns it to the users in guests, where the office's team sees it; returns posts_id. Needs from, guests, tasks_id, lawsuits_id and start_date. The same type, lawsuit and date twice is refused.
list_tasksList tasksGETAgents: ask firstLists the office's tasks with their lawsuit and assigned users. Filtering by user returns only tasks that user still has pending, by lawsuit_id only pending tasks, by completed dates only completed ones.

Account settings, 1 operation

get_settingsGet settingsGETAgents: ask firstReturns the account's reference lists: users, contact origins, task types, procedural stages, lawsuit types and financial banks, categories, cost centers and departments. Call it first: other tools need these ids.

Customer birthday, 1 operation

list_customer_birthdaysList customer birthdaysGETAgents: ask firstLists the contacts (personal data, birth dates included) whose birthday falls in the current month, with the same fields as list_customers. The reference documents a month filter (1 to 12) but says this route always returns the current month.

Document, 1 operation

list_documentsList documentsGETAgents: ask firstLists files attached in the account, filtered by at least one of name (3+ characters), customer_id, transaction_id or post_id, combined with AND. Pass an item id to get_document_download_url for a link.

Document download link, 1 operation

get_document_download_urlGet document download urlGETAgents: ask firstCreates a signed download link for one attached file, valid for 300 seconds (5 minutes); each call makes a new one. An unknown id answers HTTP 500, not 404.

Latest lawsuit movement, 1 operation

list_last_movementsList last movementsGETAgents: ask firstReturns the most recent movement of each lawsuit of the office, one row per lawsuit, newest first; totalCount counts distinct lawsuits. Use list_lawsuit_movements for every movement of one lawsuit.

Lawsuit movement, 1 operation

list_lawsuit_movementsList lawsuit movementsGETAgents: ask firstReturns every movement (andamento) of one lawsuit, optionally only TRIBUNAL (from the court) or MANUAL ones. No movement, or an unknown id, answers HTTP 204 with an empty body.

Lawsuit publication, 1 operation

list_lawsuit_publicationsList lawsuit publicationsGETAgents: ask firstReturns the publications (court notices such as intimacoes) recorded for one lawsuit, with their text and date. Empty data when there are none.

Lawsuit task, 1 operation

list_lawsuit_tasksList lawsuit tasksGETAgents: ask firstReturns every task (history) of one lawsuit at once, filtered by status pending or completed when given; no pagination. An unknown or inaccessible lawsuit returns an empty list, not 404.

Movement, 1 operation

create_lawsuit_movementCreate lawsuit movementPOSTAgents: ask firstAdds a manual movement (andamento) to a lawsuit of the office; it is stored with origin MANUAL. The date is DD/MM/YYYY here, unlike other routes, and the description needs at least 10 characters.

Use ADVBOX from Claude Code, Cursor or Codex

Connect ADVBOX in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its ADVBOX operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect ADVBOX

Create your workspace
Sign up free. Nothing to install.
Connect ADVBOX once
Add your ADVBOX connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

ADVBOX integration FAQ

What can you do with the ADVBOX integration?

LiveContext exposes 22 operations on ADVBOX, covering lawsuit, transaction, customer and task. Common uses include fetching a petition PDF attached to a task.