Add WhatsApp to Claude Desktop — Run Your Business by Talking to Claude

Claude Desktop is the most common MCP client by far — millions of people use it daily. It's also one of the most underrated AI agents on the market: it can read your files, browse the web, run code, and call any MCP tool you give it.

Here's a tool worth giving it: the ability to message your customers, team, and suppliers on WhatsApp — the channel humans actually read.

Once you wire this up, prompts like these just work:

Text the on-call engineer (+14155551234) — production deploy succeeded, no further action needed.

Send the invoice attached to this conversation to my client on WhatsApp.

WhatsApp our delivery driver the next 5 stops on the route.

Send the team a status update: deployed v2.1, customers can now use multi-currency. Use the team's WhatsApp group.

Claude figures out the phone numbers (from your files or context), the language, the tone, and calls the WhatsApp MCP tool to send the message. You write one sentence.

Heads up — what this is for. WhatsApp Business API (which Gavi runs on) is for messaging your customers, team members, and business contacts who have opted in to hear from you. Meta strictly enforces this: messaging personal contacts (family, friends) on a Business API is a policy violation that can get your number suspended. Use the regular WhatsApp app for personal messaging — they're different products.

Setup (2 minutes)

1. Get a Gavi WhatsApp API key

Sign up at gaviventures.com. Free tier works for testing and small businesses.

2. Edit Claude Desktop's MCP config

On macOS:

open ~/Library/Application\ Support/Claude/claude_desktop_config.json

On Windows:

%APPDATA%\Claude\claude_desktop_config.json

Add the gaviwhatsapp server (merge with anything you already have):

{
  "mcpServers": {
    "gaviwhatsapp": {
      "command": "npx",
      "args": ["@gaviwhatsapp/mcp", "--api-key", "gv_YOUR_KEY"]
    }
  }
}

3. Restart Claude Desktop

When it boots, you'll see a small hammer/tool icon in the bottom-right of the chat input. Click it to verify the WhatsApp tools are loaded:

• send_message
• send_template
• send_media
• send_broadcast
• list_templates
• list_messages

That's it.

What you can ask Claude Desktop now

Customer notifications

WhatsApp customer +14155551234 — their order #1247 has shipped, tracking number TRK-9981. They opted in at checkout.

Send the "appointment_reminder" template to +447700900000 with their booking confirmed for Tuesday 3pm.

Team and ops messages

Text the on-call engineer (+14155551234): the staging build is failing on test_payment_flow. Pasting the stack trace below.

WhatsApp our warehouse lead (+919876543210) — there's a rush order to pack today, SKU SKU-882, qty 5, ship to address in the attached file.

Send a WhatsApp summary of this design doc to my cofounder (+919898989898). Keep it under 200 words.

Supplier and vendor coordination

WhatsApp our printer (+14155551234) the attached PDF and ask if they can deliver 200 copies by Friday.

Send our delivery contractor a WhatsApp summary of tomorrow's pickup list — first stop 9am, last stop 5pm.

Sending files

Send the contract.pdf I attached to my client at +14155551234. They asked for it on WhatsApp earlier today.

Claude reads the file and uses send_media to deliver it as a WhatsApp document.

Multi-step automation

Read sales-summary.csv. WhatsApp the top 3 customers by revenue a personalized "thank you" message using the vip_thanks template. Only message customers who have an opt_in: yes field.

Claude reads the CSV, filters for opted-in customers, picks the top 3, drafts personalized messages, and sends them one by one. You watch the tool calls fire in the chat.

A note on first-contact messages (and the 24-hour rule)

WhatsApp has a rule: you can only send free-form text to someone who has messaged your business number in the last 24 hours.

For first-contact messages — like notifying a customer their order shipped, or pinging a supplier you haven't spoken to today — you need a Meta-approved template. Create the templates you'll actually use (e.g. order_shipped, appointment_reminder, invoice_ready) in the Gavi dashboard, submit for approval (~1 hour), and Claude can use them like:

Send the "order_shipped" template to +14155551234 with variables "1247" (order number) and "TRK-9981" (tracking).

For active conversations (someone messaged you within the last 24h), free-form text works directly — no templates needed.

Required: opt-in

Every recipient of a business-initiated message must have opted in to receive WhatsApp from your business — at signup, at checkout, via a website form, or by messaging you first. This is Meta's rule and it's strictly enforced. Cold-messaging contacts who never opted in will tank your quality rating fast and can get your number suspended.

Why this beats every other "AI ops assistant" right now

There are a lot of AI assistants in 2026. Most of them can talk eloquently. Almost none of them can actually do anything in the real world that matters. WhatsApp is the rare exception — a channel that 3 billion humans actively check, that connects you to your customers, team, and partners, that closes loops in the real world.

When Claude Desktop can message customers and operators on WhatsApp, it crosses a meaningful threshold. It stops being a research assistant and starts being a real ops assistant.

What it costs

• Gavi: $9.99/mo flat (no per-message markup)
• Meta: per-message charges billed directly to your WhatsApp Business Account at Meta's published rates (varies by country and message category)
• Claude Desktop: comes with your Anthropic Pro/Team plan

For most small businesses (a few hundred messages/month), Meta's pass-through charges are typically a few dollars on top of the flat Gavi fee.

Other agents this also works in

The same @gaviwhatsapp/mcp server works in:

• Cursor (when you want your coding agent to text you)
• Claude Code (terminal-based agent)
• OpenAI Codex CLI
• OpenAI Agents SDK and LangChain (for production agentic apps)

One API key, every agent runtime.

Troubleshooting

• "Tools not showing up" — make sure you fully quit Claude Desktop (not just close the window) and reopen. macOS: ⌘Q.
• "Permission denied" on the MCP config file — try chmod 644 or open it through the Claude Desktop UI's Developer settings.
• "npx: command not found" — install Node.js 18+ from nodejs.org.
• Message not arriving — first-contact messages need a Meta-approved template. See the section above.

Try it: gaviventures.com · GitHub · npm