Whatsapp Mcp
Bridge WhatsApp into MCP so agents pause for your real replies on a target number with optional allowlisted controllers.
Overview
WhatsApp MCP is a MCP server for the Build phase that enables human-in-the-loop control of AI agents through WhatsApp messaging.
What is this MCP server?
- NPM @mhrj/whatsapp-mcp v2.0.1 with stdio transport
- Human-in-the-loop pattern: agent asks via WhatsApp, you approve or steer
- Required env: WHATSAPP_TARGET_NUMBER
- Optional WHATSAPP_ALLOWED_NUMBERS to restrict controlling JIDs
- Package version 2.0.1
- Registry identifier: @mhrj/whatsapp-mcp
- Required env var: WHATSAPP_TARGET_NUMBER
What problem does it solve?
Fully autonomous agents push risky actions without a fast mobile channel for you to approve or correct them.
Who is it for?
Indie builders who live on WhatsApp and want MCP stdio HITL for Claude Code or Cursor automation.
Skip if: Teams needing SLA-grade support desk software or EU workflows without reviewing WhatsApp data handling.
What do I get? / Deliverables
Your agent sends WhatsApp prompts and waits on your replies so critical steps stay human-gated.
- Agent-to-WhatsApp messaging for questions and approvals
- Optional JID allowlist via WHATSAPP_ALLOWED_NUMBERS
- Safer semi-autonomous loops with mobile human control
Recommended MCP Servers
Journey fit
How it compares
WhatsApp HITL MCP bridge, not a marketing broadcast API or email MCP.
Common Questions / FAQ
Who is whatsapp-mcp for?
Solo builders running MCP agents who want approvals and clarifications delivered to their WhatsApp number.
When should I use whatsapp-mcp?
When agent loops should stop for your input—deploys, spend, ambiguous product calls—while you are away from the desk.
How do I add whatsapp-mcp to my agent?
Install @mhrj/whatsapp-mcp, add stdio MCP config, set WHATSAPP_TARGET_NUMBER, optionally WHATSAPP_ALLOWED_NUMBERS, and complete WhatsApp pairing per the GitHub README.