whatsapplisted

# WhatsApp Send and read WhatsApp messages via the whatsapp-mcp bridge. > **Implementation: use the maintained fork `verygoodplugins/whatsapp-mcp`, not upstream `lharries/whatsapp-mcp`.** > Same architecture (Go whatsmeow bridge + Python MCP server, QR linked-device auth, local > `whatsapp.db`), but upstream went quiet after ~April 2025 (~91 open issues / ~131 open PRs); the fork > is actively maintained (CI/CD, call capture, media, LID resolution). This is still the *only* mature > way to reach a **personal** WhatsApp number — every 2025–26 alternative (Meta Business Agent, > Composio/Wati/360dialog MCP gateways) is Business-Cloud-API-only and can't touch personal threads. > Tradeoffs are real and unchanged: unofficial → violates ToS + genuine account-ban risk, ~20-day QR > re-auth, and protocol breakage that halts messaging until a maintainer fix is pulled + redeployed. > See memory `[[reference_whatsapp_connection_options]]`. Not yet installed on Educloud (needs Go in > the sandbox image). ## Before any WhatsApp tool call Check if the bridge is running: ```bash curl -sf http://localhost:8080/api/send 2>/dev/null ``` If no response, start it: ```bash nohup ~/whatsapp-mcp/whatsapp-bridge/bridge > /tmp/whatsapp-bridge.log 2>&1 & sleep 8 # wait for connection + history sync ``` If the bridge fails with a QR code auth error, tell the user to run: ``` ! cd ~/whatsapp-mcp/whatsapp-bridge && ./bridge ``` and scan the QR code with their phone (WhatsApp → Linked Devices → L