SendPulse WhatsApp MCP
Related Servers
Alternatives to SendPulse WhatsApp MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables Claude to manage WhatsApp templates, flows, and send messages through the WhatsApp Cloud API.3119 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables interaction with SendPulse Chatbots API to manage chatbot accounts, retrieve bot information, and access dialog conversations. Supports flexible authentication through API credentials or OAuth tokens for comprehensive chatbot management through natural language.4 npmMIT
- AlicenseAqualityDmaintenanceEnables Claude to interact with WhatsApp through a unified backend API, providing 20 tools for messaging, media, groups, contacts, and chat management.2213 npmMIT

ConverZAP MCP serverofficial
AlicenseNot gradedqualityCmaintenanceEnables AI assistants and agents to work with WhatsApp through the official WhatsApp Business Platform (Meta Cloud API), exposing tools to search contacts, read conversations, send messages and approved templates, manage CRM deals, run campaigns, enroll contacts in automations and pull reports. All actions run through a hosted public API, so they honor the account's existing roles, scopes and rate limits, with write operations supporting dry-run validation and confirmation for destructive calls.MIT- FlicenseNot gradedqualityBmaintenanceEnables Claude to read and operate a TimelinesAI WhatsApp team inbox, including chats, messages, labels, assignments, and sending, with built-in read-only and confirmation safeguards.-
- AlicenseNot gradedqualityDmaintenanceEnables sending WhatsApp messages through Claude Desktop and other MCP-compatible LLMs. Supports single and bulk messaging, phone number validation, and session management via the zapr.link service.MIT
TDQS
Scored across 26 tools
Most tools have clearly distinct resource+action purposes, but several pairs can be confused: send_campaign vs send_template_campaign, send_template vs send_template_by_phone, and run_flow vs run_flow_by_trigger. Descriptions clarify the differences, so an agent can recover, but selection requires careful reading.
All tool names follow a consistent sendpulse_ prefix plus snake_case verb_noun/verb_noun_qualifier pattern (e.g., sendpulse_create_contact, sendpulse_get_contacts_by_tag, sendpulse_set_contact_variable). No mixed conventions or vague naming.
At 26 tools, the surface is heavy for a WhatsApp bot-management server, and some pairs feel like variants of the same operation (run_flow/run_flow_by_trigger, enable/disable contact, send_campaign/send_template_campaign). It is not extreme, but the count is borderline bloated.
Core lifecycle operations are covered: contacts (create/get/enable/disable/tag/variable/name/pause/resume), messaging and templates, campaigns, flows, triggers, chats, bots, and stats. Minor gaps exist, such as no hard delete-contact operation and no direct listing of templates or campaigns, but agents can work around them.