totvs-tickets-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TOTVS_DEBUG | No | Set to '1' to enable verbose login logging to stderr. | |
| TOTVS_TIMEOUT | No | Request timeout in seconds (default 60). | |
| TOTVS_PASSWORD | No | Override for the Fluig password stored in keyring. | |
| TOTVS_USERNAME | No | Override for the Fluig username stored in keyring. | |
| TOTVS_AUDIT_LOG | No | Set to '1' to append audit log to ~/.totvs-tickets-mcp-audit.log. | |
| TOTVS_TOTP_SEED | No | Override for the TOTP seed stored in keyring. | |
| TOTVS_DEFAULT_ORG | No | Default Zendesk organization ID for ticket search (see totvs_whoami). Empty means all visible orgs. | |
| TOTVS_NO_TOKEN_CACHE | No | Set to '1' to disable token caching on disk. |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| totvs_whoamiA | Identidade do usuario no portal TOTVS derivada do token: userId Zendesk,
customerCode padrao, organizacoes as quais pertence e validade do token.
Use pra descobrir os |
| totvs_contatoA | Dados cadastrais do contato logado no portal (nome, email, telefone, empresa/customerCode, cargo). Endpoint contact/find-contact. |
| totvs_tickets_listarA | Busca/lista tickets de suporte TOTVS por ORGANIZACAO, com filtros e paginacao. A busca ve tickets de qualquer solicitante da(s) organizacao(oes) — nao so os
do usuario logado.
|
| totvs_ticket_detalheA | Detalhe completo de um ticket (solicitante, colaboradores, organizacao,
status, produto/modulo, etc). |
| totvs_ticket_comentariosA | Comentarios/andamentos de um ticket, com anexos. |
| totvs_tickets_statusA | Lista oficial de status usaveis no filtro |
| totvs_tickets_filtrosA | Opcoes do catalogo para os filtros de
|
| totvs_tickets_motivos_prioridadeA | Lista de motivos de priorizacao (priority-reasons) usados no portal. |
| totvs_notificacoes_countA | Numero de notificacoes nao lidas do usuario no portal (ex: {'unread': 44}). |
| totvs_usuarios_buscarA | Busca usuarios/contatos do Zendesk por termo (nome/email), opcionalmente
escopado por organizacao. Util pra descobrir o
|
| totvs_departamentosA | Lista os departamentos/areas de atendimento do portal (key, label, nome, tags). Endpoint chats-departaments/get-departament-by-area. |
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 11 tools
Each tool has a clearly distinct purpose: contact info, departments, notifications count, ticket comments, ticket detail, filter options, ticket listing, priority reasons, status list, user search, and identity info. No two tools overlap in functionality.
All tools start with 'totvs_' followed by a descriptive noun or noun_action. There is a minor inconsistency between singular and plural forms (e.g., 'totvs_ticket_comentarios' vs 'totvs_tickets_listar'), but the overall pattern is predictable and clear.
With 11 tools covering identity, search, filtering, and ticket details, the count is well-scoped for a ticket support portal. It provides sufficient functionality without being excessive.
The tool set is heavily read-oriented, lacking essential create, update, or close operations for tickets. While it covers querying and listing well, there are no tools to modify tickets, making the surface incomplete for full ticket lifecycle management.