What is a WhatsApp MCP server, and which kind can a sales team use?

What an MCP server is

MCP, the Model Context Protocol, is the open standard assistants use to call outside services. A server publishes a list of tools, each one a question it can answer, and the assistant chooses which to call for the question you typed. Claude, ChatGPT, Claude Code, Cursor and others speak it, so 1 server serves all of them.

A WhatsApp MCP server is any service that puts WhatsApp conversations behind such tools. The phrase is doing a lot of work: the servers that carry it differ in whose WhatsApp they read, where the record lives, and whether they can send.

The 3 kinds, and the job each was built for

1. An open-source bridge. A program on your own machine links to 1 WhatsApp account as a companion device, keeps a local copy of what the phone synced, and offers tools to read it and, usually, to send from it. It was built for 1 person's own chats. For a manager it reads 1 account, not the team's, it runs only while the machine does, and a tool that sends from a number through software WhatsApp did not issue is a risk to that number.
2. A Business API connector. An inbox vendor that runs your numbers on the WhatsApp Business API exposes its inbox as tools: read a thread, send a reply, send a template, start a broadcast. It was built for sending at volume, and it needs the API, which means leaving the WhatsApp Business app and the phones. If your team already runs on an API inbox, this is the natural route. Whether the API is right for a sales team of reps on phones is its own question.
3. An archive connector. A service that already holds the company's conversations opens that record to assistants, read-only. WAOversight is one: every company-owned number is linked as a companion device, the way WhatsApp Web is, every message is captured into an append-only archive, and the MCP server reads that archive as the login that connected it. It was built for a manager's questions about the team, and it has no tool that sends.

What a manager needs from one

Judge any of the 3 against the question you will type. 5 things decide it.

• Every number, in 1 place. A question about a customer spans the 3 reps who handled them. A server that reads 1 account cannot answer it.
• The record, not the phone. Deleted messages with their originals, edits with their history, and a number that dropped its link reported as such.
• Read-only, with no exceptions. An assistant that can send from your team's numbers can be talked into it by a message it read. The safe design has no send tool to misuse.
• Your login, your scope. A manager's assistant should see that manager's teams and nothing more, and the reply should say nothing about what else exists.
• A log your team can trust. When you linked the numbers you told the team every read is recorded. An assistant's read has to land in the same log, under your name.

What the WAOversight server reads

31 tools, every one read-only, each the same read your dashboard makes.

• The queue and the morning report: what is waiting, worst first, the items managers escalated, and the reminders due.
• Conversations, search, contacts and groups: each thread with its deleted originals and edit history; search as written, in any script, deleted and pre-edit text included.
• Analytics: the team scorecard, a rep's profile, trends, the pulse, coverage, calls and the call figures, each defined in the metrics guide.
• Nora's findings, rules and their analytics, cases and escalation notices.
• Exports and the integrity check: the evidentiary export with its hash chain, and proof a thread has not been altered.
• The access log and usage: who read what, every assistant included, and how many calls each person's assistant made.

Replies are paged, 50 messages or 25 rows at a time, and capped at 100 KB. Files come back as a list with a sign-in link, never the file. Nothing is redacted: you asked for the customer by name, and the reply is your own read. The prompts managers type, by kind, are on the AI assistants page.

What it never does

• It never sends. Not a reply, not a reminder, not a notice. The only WhatsApp message WAOversight sends is an escalation notice to your own rep, and no tool reaches that path.
• It never changes anything: no assigning, dismissing, snoozing or escalating an item, no case opened or closed, no rule or setting touched.
• It never reads past your login. Reps have no login, so no rep's assistant can connect.
• It keeps nothing of what you asked. What you ask for goes to your assistant's provider under your own account's terms; WAOversight stores counts only.

Which assistants connect

1 address, https://mcp.waoversight.com/mcp, and your own sign-in. Claude on the web, desktop, mobile and in Cowork adds it as a custom connector. Claude Code takes it from 1 terminal command, then /mcp to sign in. ChatGPT creates it under Developer mode. Cursor and VS Code read it from mcp.json. Microsoft 365 Copilot and Gemini Enterprise connect through their admin centres.

Before any of this works, an owner or admin switches AI assistants on at Settings › AI assistants, after an acknowledgement about what leaves and to whom. The steps for each client, the caps and the troubleshooting are on connecting an AI assistant.

Where this stops

• It reads WhatsApp conversations on linked company numbers, from the moment each was linked. Not a rep's own WhatsApp, not ordinary phone calls, and not history before the link beyond what the import carried.
• It is only as current as capture. A number that has dropped its link is reported as such, and nothing that was missed appears.
• It is not Nora. Nora reads on your workspace's own provider with identifiers redacted; an assistant is yours and reads unredacted. It can read Nora's findings; it does not make them.
• A workspace needs a live subscription or its trial, on any plan. There is no plan that adds this and none that lacks it.