MCP Advbox Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Porta interna (default: 3000) | 3000 |
| MCP_TOKEN | Yes | Token de autenticação do MCP | |
| ADVBOX_BASE_URL | No | URL base da API (default: https://app.advbox.com.br/api/v1) | https://app.advbox.com.br/api/v1 |
| ALLOWED_ORIGINS | No | Domínios permitidos (CORS) | |
| ADVBOX_API_TOKEN | Yes | Token de acesso à API Advbox |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| advbox_list_customersA | List customers from Advbox with various filter options including name, phone, email, location, and creation date. Returns paginated results. |
| advbox_get_customerB | Get a specific customer by ID from Advbox |
| advbox_create_customerB | Create a new customer in Advbox. Requires user ID, origin ID, and customer name. |
| advbox_get_birthdaysA | Get customers with birthdays in the current month |
| advbox_list_lawsuitsA | List lawsuits from Advbox with various filter options including customer, process number, dates, stage, and responsible. Returns paginated results. |
| advbox_get_lawsuitA | Get a specific lawsuit by ID from Advbox |
| advbox_create_lawsuitA | Create a new lawsuit in Advbox. Requires user ID, customer IDs, stage ID, and lawsuit type ID. |
| advbox_update_lawsuitC | Update an existing lawsuit in Advbox |
| advbox_get_lawsuit_historyA | Get the task history of a specific lawsuit |
| advbox_get_lawsuit_movementsC | Get the movements/updates of a specific lawsuit |
| advbox_create_movementB | Create a new movement/update for a lawsuit |
| advbox_get_last_movementsA | Get the latest movements across all lawsuits with filter options |
| advbox_list_tasksA | List tasks/appointments from Advbox. Note: Date filters require both start AND end dates. Maximum range is 90 days. |
| advbox_create_taskB | Create a new task/appointment in Advbox. Requires creator ID, guests, task type, lawsuit, and start date. |
| advbox_get_publicationsB | Get publications for a specific lawsuit |
| advbox_list_transactionsA | List financial transactions from Advbox with comprehensive filter options |
| advbox_get_settingsA | Get Advbox account settings and configuration |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.