{"id":"delltrak-wamcp","name":"wamcp","homepage":null,"repo_url":"https://github.com/delltrak/wamcp","category":"messaging","subcategories":[],"tags":["messaging","whatsapp","mcp","ai-agents","automation","typescript","docker","real-time","sse"],"what_it_does":"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.","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"],"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.","alternatives":["Twilio WhatsApp APIs (programmable messaging + webhooks)","WhatsApp Cloud API with custom server + webhooks","Other MCP servers/integration frameworks that wrap messaging providers","Baileys-based custom bots (where you implement your own tool layer and event plumbing)"],"af_score":71.0,"security_score":54.8,"reliability_score":43.8,"package_type":"mcp_server","discovery_source":["github"],"priority":"high","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-03-30T15:40:16.296639+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":true,"mcp_server_url":"http://localhost:3000/mcp","has_sdk":false,"sdk_languages":["Python (examples for Google ADK and LangChain MCP integration)"],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":["Baileys session/pairing via QR code or pairing code","Meta Cloud API token via wa_set_cloud_credentials"],"oauth":false,"scopes":false,"notes":"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":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"No pricing information in provided content; likely self-hosted open-source."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":71.0,"security_score":54.8,"reliability_score":43.8,"mcp_server_quality":88.0,"documentation_accuracy":78.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":60.0,"rate_limit_clarity":70.0,"tls_enforcement":70.0,"auth_strength":55.0,"scope_granularity":30.0,"dependency_hygiene":60.0,"secret_handling":60.0,"security_notes":"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.","uptime_documented":0.0,"version_stability":50.0,"breaking_changes_history":50.0,"error_recovery":75.0,"idempotency_support":"false","idempotency_notes":"No idempotency semantics were stated. Actions like sending messages are generally not guaranteed idempotent across retries unless the implementation includes deduplication logic (mentioned at a high level as 'Dedup' in architecture, but no contract-level guarantee is documented).","pagination_style":"none","retry_guidance_documented":true,"known_agent_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."]}}