wamcp
WA MCP is a Model Context Protocol (MCP) server that exposes WhatsApp functionality to MCP-compatible AI agents. It provides 63 tools (prefixed with wa_), 10 read-only resources (whatsapp:// URIs), and 12 real-time events (SSE) for both WhatsApp Web via Baileys and WhatsApp Cloud API via a dual-channel backend. It can be deployed with Docker using Redis and supports multi-instance WhatsApp connections with queueing and persistent storage.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Security guidance is limited in the provided README. The server exposes powerful WhatsApp operations, so it should be run with network access controls and protected credentials/session storage. Docker deployment and server-side tokens/session state increase the importance of secret management, TLS termination, and least-privilege for any upstream access to the MCP endpoint.
⚡ Reliability
Best When
You want an MCP-native bridge so an agent can discover and call WhatsApp tools automatically, and you can run/secure a long-lived MCP server with Redis and WhatsApp credentials.
Avoid When
You cannot securely manage WhatsApp session/credential material, or you lack operational support for reconnect/retry behavior and rate limiting.
Use Cases
- • Letting AI agents send and manage WhatsApp messages (text, media, polls, reactions, edits/deletes, etc.)
- • Building customer-support or workflow agents with real-time WhatsApp event streaming
- • Automating group management (create/manage members, settings, invite links, ephemeral toggles)
- • Implementing contact and profile management tools for WhatsApp-integrated agents
- • Creating notification-driven assistants that react to incoming messages and updates
Not For
- • General-purpose messaging relay without appropriate governance/auditing
- • Use cases requiring guaranteed delivery/ordering semantics beyond WhatsApp/transport constraints
- • Handling sensitive personal data without considering compliance, consent, and data protection controls
Interface
Authentication
Auth is not described as OAuth-style; it appears to rely on WhatsApp account connectivity (Baileys pairing/session) and/or a Cloud API credential token set in the server configuration/tools.
Pricing
No pricing information in provided content; likely self-hosted open-source.
Agent Metadata
Known Gotchas
- ⚠ WhatsApp connectivity may require QR/pairing flows and may fail until instance is connected.
- ⚠ Rate limiting is queue-based; agents that fire many sends may still hit backlogs or receive errors during throttling.
- ⚠ Real-time events are delivered via SSE; ensure the agent runtime maintains the SSE connection.
- ⚠ Multi-instance setups require correct instance IDs and consistent routing of tool calls to the intended instance.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for wamcp.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.