# WhatsApp MCP Server: Connect Claude to Your Team Inbox > WhatsApp MCP server for sales teams: link Claude or ChatGPT to your shared Levvo inbox and ask which enquiries sit unanswered and who replied last. - Language: en - Canonical: https://levvoapp.com/whatsapp-mcp/ - Hreflang es: https://levvoapp.com/es/servidor-mcp-whatsapp/ - Hreflang en: https://levvoapp.com/whatsapp-mcp/ - Hreflang x-default: https://levvoapp.com/whatsapp-mcp/ - Schema: SoftwareApplication - Primary keyword: WhatsApp MCP server --- ## WhatsApp MCP server: your team inbox inside Claude Link Claude or ChatGPT to your team's shared inbox: ask which enquiries sit unanswered, get a thread summary or assign the chat to its owner. With your authorisation and the app's own limits. - [Connect my inbox](https://levvoapp.com/hello/) - [See pricing](https://levvoapp.com/pricing/) - Showcase Video: /ui-images/levvo-mcp.mp4 --- ## You open the dashboard to see who hasn't replied. Ask Claude. Your assistant reads the shared Levvo inbox and answers with the contact's name, the channel and the minutes since the last message. Nothing to export. ### Which conversations have been waiting longest? UNANSWERED ENQUIRIES The list lands coldest first, with the contact's name, the channel and the minutes since their last message. ### Summarise the thread with Maria before I ring her back SUMMARY BEFORE YOU CALL It reads the full history and gives it to you in two sentences, including the chat's last saved deal verdict. ### Reply to the viewing request and confirm Saturday at ten REPLIES FROM YOUR CHAT Claude sends your words from the business line, after your confirmation and with the send recorded. ### Give this enquiry to whoever covers second-hand cars ASSIGN AND LABEL The chat lands with one named owner and the right label, exactly as if you had done it in the app. ### How did the team do this week? THE DASHBOARD, IN WORDS Reply-time KPIs, SLA risk and the team's recent activity, read straight off your reports panel. --- ## The tools, grouped by what they touch Every tool reads and writes what you already see in the app, inside the permissions of the role that authorised the connection. ### See the team's conversations Filtered by channel, status or unanswered only, with readable contact names. - Tag: Read ### Read one thread in full The whole history of that chat, with the last saved sales verdict attached. - Tag: Read ### Reply inside an existing chat Text leaves from the business line with your confirmation, quota and a record of who asked. - Tag: Write ### Assign the chat to its owner One conversation, one named owner: the same rule the app already applies. - Tag: Organise ### Labels from the team catalogue Adds or removes labels that already exist. No invented labels. - Tag: Organise ### Reports and the sales funnel Reply-time KPIs, SLA risk, recent activity and the funnel with its top objections. - Tag: Reports --- ## It walks in with your permission and the app's limits You authorise it once, on Levvo's consent screen. - Visual Video: /ui-images/claude-levvo-prompt.mp4 - Visual Alt: Claude answering questions about the team's shared WhatsApp inbox through the Levvo MCP server. Only workspace roles can grant that permission, and every call rechecks the account and the role. ### Every send has a quota and an author Replies sent by Claude pass the same per-user cap and prepaid quota as the app, and are recorded against whoever asked for them. ### It cannot write to strangers The connector only replies inside existing conversations: no cold outreach to new numbers. ### You can cut it off at once Remove the member or revoke the connection and their access dies on the next call. No waiting. --- ## Three steps, then your first question Nothing to install on your computer and nothing to program: the server address copies with one click. ### Your WhatsApp line, already in Levvo If the team already answers from Levvo there is nothing to do here: the connector uses that same line. - Tag: Step 01 ### Paste the address into your AI app In Claude: Settings, Connectors, add a custom connector. In ChatGPT: Connectors and apps, developer mode. Paste the address and you are done. - Highlight: https://be.levvo.space/mcp - Tag: Step 02 ### Authorise with your Levvo account Approve the consent screen, then ask for your first report of unanswered enquiries. - Tag: Step 03 - Rail Status: 1 WhatsApp line connected - Rail Time: < 2 minutes - Rail Left Note: No number migration - Rail Right Note: 100% cloud sync --- ## Levvo MCP against rolling your own Three routes to put WhatsApp in front of an AI, stated plainly. A personal repo runs on your number and your PC; Meta's API needs your own technical team; Levvo already holds your line connected. | Feature | Levvo | A personal repo | Meta's API, hand-rolled | | --- | --- | --- | --- | | Set-up | Copy one address | Go or Python on your PC, session kept alive | Meta Business account, tokens and your own build | | Built for | The owner or sales manager | Personal use of one number | Whoever writes the integration | | Per-role permissions | Yes | No | No | | Send quota and audit trail | Yes | No | Meta's per-message fee | | Team reports | Yes | No | No | | Who keeps it running | Levvo | Your PC, switched on | Your engineers | --- ## The doubts that come up before you connect the team Security, limits and cost of the AI connector for your shared inbox. ### What can Claude see of my business? Only the workspace you authorise: the lines connected in Levvo, their conversations and your team's reports. Nothing from other companies and nothing from your personal WhatsApp. ### Can it send messages without me knowing? It never writes to new or cold numbers: it only replies inside existing conversations. In Claude you can require confirmation before every send, and Levvo records who authorised each one. ### What can't the connector do? It cannot create, connect or delete WhatsApp lines, touch billing, delete conversations, contact numbers that have never written to you, or see anything outside your workspace. Every send is one existing conversation, capped and charged like the app. ### Do I need to write code? No. The whole set-up is copying an address, pasting it into your AI app and approving the consent screen with your Levvo account. ### Does it work with ChatGPT or only Claude? Both, and with any client that accepts remote MCP servers with OAuth sign-in. The server address is the same. ### What does it cost? The connection itself costs nothing. Each reply your assistant sends draws on the same prepaid quota and per-user cap as the app. Reading and reporting never touch the quota. ### Will my team notice any change? None. Your reps keep answering from the app or their own WhatsApp as always; the connector only adds a second door, for you. ### What if I want to cut it off? Revoke the connection from your AI app or remove the member in Levvo: their access dies on the next call, without waiting for the token to expire. --- ## Put your WhatsApp inbox where you already talk. No card, no numbers to migrate, every enquiry with an owner. - Founder Comment: Owners already ask their AI questions all the time. With the MCP server that same AI finally sees the inbox: which enquiry has been waiting 20 minutes, who replied, which thread is going cold. You ask in your chat and it answers with names, not screenshots. - Founder Name: Frank - Founder Role: Ex sales lead, founder - [Connect my inbox](https://levvoapp.com/hello/) - [See pricing](https://levvoapp.com/pricing/)