WAzion MCP Server
Related Servers
Alternatives to WAzion MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceBridges the WhatsApp HTTP API with AI assistants to enable full control over messaging, chat management, and interactive workflows through 63 specialized tools. It allows users to automate WhatsApp tasks and receive real-time AI feedback directly on their mobile devices.6312 npm6MIT
- AlicenseBqualityDmaintenanceEnables AI assistants to manage WhatsApp sessions, send multi-format messages, control group participants, and configure webhooks by wrapping the OpenWA REST API with 44 tools.442MIT
- AlicenseAqualityCmaintenanceProvides comprehensive WhatsApp Business API functionality with 18 tools for sending messages, media, interactive buttons/lists, templates, reactions, and managing message status through the PyWA library.183MIT
- AlicenseAqualityDmaintenanceEnables LLMs to interact with WhatsApp via the official WhatsApp Cloud API, providing tools for sending messages, templates, media, and managing conversations.1313 npmMIT
- AlicenseBqualityDmaintenanceEnables AI agents to control WhatsApp, including sending messages and media, reading chats, managing groups and communities, with QR/pairing auth and session persistence.1417 npm2MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to send WhatsApp messages, templates, and retrieve media through the WhatsApp Cloud API. Provides webhook handling and seamless integration with Meta's WhatsApp Business platform.23-
TDQS
Scored across 366 tools
There are many overlapping tools, especially in the marketing and contact management areas (import_contacts_csv, import_contacts_manual, import_marketing_contacts, import_contacts_from_all_conversations, import_contacts_from_crm, import_contacts_from_conversations, import_contacts_from_platform, import_contacts_txt, import_mapped_contacts, add_contacts_to_list, create_list_from_inactive, create_list_from_followup, etc.) which create confusion about which to use. Similarly, multiple tools for managing knowledge snippets (update_knowledge_snippet, edit_knowledge_snippet, approve_knowledge_snippet, reject_knowledge_snippet, resolve_knowledge_conflict, reject_and_propose_knowledge_snippet, keep_both_knowledge_snippets, delete_knowledge_snippet) and numerous email tools with similar purposes make selection difficult.
Most tools follow a consistent verb_noun pattern (e.g., list_*, get_*, create_*, update_*, delete_*), but there are inconsistencies such as 'precheck_delete_whatsapp_session', 'dry_run_workflow', 'global_search', 'bulk_toggle_workflows', 'reorder_whatsapp_workflows', and several tools with non-standard naming like 'get_crm_health_status', 'get_whatsapp_health', 'get_email_unread_count' that mix nouns and verbs. There are also some English descriptions mixed with Spanish, but naming is mostly consistent.
With 366 tools, this is an extreme mismatch. The server tries to cover an entire e-commerce customer service platform with WhatsApp, email, calendar, marketing, CRM, plugins, knowledge base, and many other modules, but the sheer number makes it overwhelming and impractical for an agent to navigate effectively. Even for a comprehensive platform, 366 tools is far too many and will lead to performance issues and misselection.
The tool set is extremely comprehensive, covering almost every aspect of the platform: conversations, agents, tasks, marketing campaigns, WhatsApp workflows, email management, calendar, CRM, knowledge base, plugins, analytics, and configuration. There are very few gaps; for example, there is no explicit tool to list all customers, but global_search and search_customers cover that. The coverage is thorough for a platform of this scope.