Meta Tech ProviderRun Your WhatsApp Inbox and Campaigns from Claude Code with the ThinnestAI MCP Server
The short version
The ThinnestAI MCP server now does what your team does in the inbox. Your assistant can find the conversations waiting for a person, read them, and — when you say so — resolve them, hand them back to the agent, take them over, or assign them to a teammate. It can read every campaign's results and pause, resume or cancel one.
It works in Claude Code, Cursor and VS Code with a ThinnestAI API key. If you have not connected it yet, start with the MCP server overview.
Triage what is waiting for your team
Ask: "Which conversations are waiting for us?" The assistant lists conversations by status — escalated (the agent handed over) and human_handling (a teammate took over) — reads the messages, and tells you in one line each: who it is, what they want and how long they have waited.
Then you decide, and it carries it out:
| You say | What happens |
|---|---|
| "Resolve it" | The conversation is marked done and your conversation.resolved webhook fires |
| "Give it back to the agent" | The agent picks the conversation up again |
| "I'll take this one" | The agent goes quiet until you hand it back |
| "Assign it to Priya" | It becomes your teammate's job, and they are notified |
Every status change leaves an internal note in the conversation saying an AI assistant made it, through which key — so your team never wonders who resolved a chat. Moving a conversation that is already where you asked changes nothing and says so. The shared inbox is part of the paid plans; pay-as-you-go has no monthly fee.
Replying to the customer is different: it needs a full-access key, and the assistant shows you the exact message and waits for your yes before it sends.
Watch and stop a campaign
Ask: "How did yesterday's broadcast do?" The assistant reads every WhatsApp broadcast and calling campaign with its results — recipients, sent, delivered, read, replied, failed and skipped.
- Pause stops further sends. Messages already handed to WhatsApp, and calls already placed, still complete.
- Resume starts sending again to everyone not yet reached — charged as usual — so it needs a full-access key and your approval.
- Cancel stops the campaign for good. It asks for your approval first, because it cannot be undone; to run it again, duplicate it in the console.
A campaign that already finished cannot be cancelled, and the assistant is told so plainly — it does not report a cancel that did not happen.
What still needs the console
Creating and launching a campaign stays in the console. Choosing an audience and a template and pressing send is a decision we want a person to make on screen, with the cost in front of them. The assistant can tell you what a campaign did and stop it; it does not start one.
Which key to use
A Build key can triage, resolve, assign, take over, pause and cancel — none of those contact a customer. Resuming a campaign and replying to a customer need a full-access key, and both still ask for your approval. Read more in giving an assistant a key that cannot message customers.
The triage_inbox prompt runs the whole triage as a plan with the decision points written in — see the five ready-made prompts.