wati-mcp-server
wati-mcp-server is a Python Model Context Protocol (MCP) server that integrates with the WATI WhatsApp Business API, exposing MCP tools for messaging, contacts, template/broadcast messaging, media file handling, and conversation history retrieval (with pagination/filtering), plus a demo get_weather tool.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Uses API_ENDPOINT over an HTTPS URL in the example config and bearer-token authentication via environment variables. The README does not describe scope granularity, token rotation, storage/log redaction guarantees, or rate-limit handling. Dependency hygiene is unknown from provided content; requests/python-dotenv/mcp are standard libraries but no CVE/lockfile evidence is included.
⚡ Reliability
Best When
You want a straightforward MCP integration to automate WhatsApp Business actions (send templates/messages, manage contacts, fetch history) from an AI assistant using environment-variable credentials.
Avoid When
You need guaranteed safety around retries/idempotency for message sends, or you require clear, provider-level limits (rate limits, quotas) and strong confidentiality guarantees beyond storing an access token in environment variables.
Use Cases
- • Let an MCP-capable AI assistant send WhatsApp messages (including template messages) via a WATI WhatsApp Business account
- • Manage WhatsApp contacts (list, add, update attributes) through MCP tool calls
- • Retrieve conversation/message history with pagination and filtering
- • Send media files to WhatsApp sessions from the assistant
- • Run bulk/template broadcasts to multiple recipients (including CSV-based bulk send)
Not For
- • A production-grade WhatsApp gateway without verifying MCP tool contracts against the actual server implementation
- • Use cases requiring fine-grained OAuth authorization flows per end-user (the README describes bearer token usage)
- • Environments that require documented rate-limit behavior and retry/idempotency semantics for safe automated retries
Interface
Authentication
Authentication is configured via environment variables: API_ENDPOINT and ACCESS_TOKEN (described as a Bearer token). The README does not describe fine-grained scopes or per-tool authorization.
Pricing
Pricing for the integration itself is not described; WATI API usage would still incur provider costs.
Agent Metadata
Known Gotchas
- ⚠ Automatic retries for send_message/template/bulk operations may cause duplicate WhatsApp messages because idempotency behavior is not documented
- ⚠ Bulk operations from CSV may be sensitive to formatting/encoding; README does not document expected CSV schema constraints
- ⚠ The README includes a demo get_weather tool; ensure the agent uses only WhatsApp-related tools for production
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for wati-mcp-server.
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-04-04.