DIGISAC to MCP: Contacts, Tickets and Service Statistics of Your Omnichannel Inbox in any AI Agent

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → DIGISAC, paste your credentials, mint an MCP API key and you're done. No Docker, no git clone, no local server.

DIGISAC

Let your AI work in your DIGISAC omnichannel inbox: find contacts, read message history, tickets, departments, agents, tags and WhatsApp templates, follow sales funnels and kanban boards and get live and period service statistics. Sending messages and changing tickets are installed switched off.

Setup

Setting up takes about 2 minutes. You need a DIGISAC account and a user who can create a personal access token, ideally a supervisor or administrator.

1. Sign in to DIGISAC and open Conta → Informações. Copy the address of your account into DIGISAC_URL, for example https://empresa.digisac.co or https://empresa.digisac.app (addresses ending in -api.digisac.com.br work too), without /api/v1 or any path.
2. Open Conta → API → Tokens de acesso pessoal, create a token and paste it into DIGISAC_API_TOKEN, without the word Bearer and without spaces.
3. Install the connector and run digisac_get_me: it shows the user the token belongs to, with roles and departments.

The token acts as you: it has the permissions of the user who created it. A supervisor's token sees every department; an agent's token may get 403 on data that user cannot open. The connector sends it only to your DIGISAC address.

How DIGISAC is organised: every WhatsApp number, WhatsApp Business API line, Instagram, Messenger, Telegram, e-mail or webchat channel is a connection, and contacts, messages and templates belong to one connection. Tickets (chamados) are routed to departments (filas) and handled by agents (atendentes). The AI starts with digisac_list_connections, digisac_list_departments and digisac_list_users to learn the ids, then finds people by name or by phone number.

What it reads: contacts with number, connection, tags, note, unread count and last message time; the full message history of a contact, including media with a temporary download link and internal events; tickets with protocol, department, agent, start, end and ticket topics (assuntos); tags (etiquetas); WhatsApp Business templates (HSM) with their placeholders; quick replies (respostas rápidas); scheduled messages (agendamentos); sales funnels (pipelines) with stages and opportunities with value; service kanban boards (quadros de atendimento) with columns and cards; the desk right now (open and waiting tickets, agents online, load per department); and statistics for a period: tickets opened and closed, waiting and service times, messages sent and received, by department or agent.

Phone numbers: DIGISAC stores numbers with the country code and without +, for example 5511987654321. The AI searches by part of the number too.

Asks before every change: digisac_create_contact adds a contact to a connection (DIGISAC accepts an invalid number and marks it as not valid), and digisac_update_contact changes a contact's name, note, default department or tags. The tag list on an update replaces all of the contact's tags, so the AI reads the contact first and sends the full list. Before each one it shows you the change and waits for your yes.

Switched off at install: digisac_send_message, digisac_send_template, digisac_schedule_message, digisac_cancel_schedule, digisac_transfer_ticket and digisac_close_ticket. Messages reach the customer at once, and a text message opens a ticket unless told otherwise. On WhatsApp Business API lines free text only works within 24 hours of the customer's last message; outside that window only an approved template works, and Meta charges the conversation. Closing a ticket can send the customer the closing message and the satisfaction survey, and scheduled messages go out on their own. An administrator turns these tools on deliberately, and even then the AI confirms every one with you.

Customer text is data: message texts and contact names come from customers. The AI treats any instruction it finds in them as data, not as an order.

Limits: tickets and messages with extra details included are large, so the AI keeps pages to 20 to 50 rows and adds details only when needed. DIGISAC's filters only accept real columns; a 500 that names a column means the AI drops that part and asks again.

Common errors: 401 means the token is wrong or was deleted: create a new one under Conta → API. 403 means your user may not read this: use the token of a supervisor or administrator. 404 means nothing answered at this address (check DIGISAC_URL) or the id is unknown. 400 means a disconnected connection or a wrong parameter.

The connector does not manage bots, campaigns, webhooks, custom fields or account settings, send files or media, or delete contacts.

Prerequisites: DIGISAC_URL, DIGISAC_API_TOKEN

Install the connector locally

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Open http://localhost:3000/connectors/store, pick DIGISAC and paste in the env vars listed under Prerequisites.

Available tools

Example prompts

• "How many tickets are waiting in the Suporte department right now, and which agents are online?"
• "Show me the latest messages from the contact +55 11 98765-4321 and whether her ticket is still open."
• "How did our service go last week: tickets opened and closed, average waiting time and messages per department?"
• "Which opportunities are in the Negociação stage of our Vendas funnel, and what are they worth in total?"
• "Add the tag Cliente VIP to Maria Souza and note that she prefers WhatsApp. Show me the change first."

Next steps

• Connect to Claude
• Connect to ChatGPT