ChatPush MCP Server
OfficialRelated Servers
Alternatives to ChatPush MCP Server
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityBmaintenanceEnables AI agents and tools to send and manage WhatsApp messages, media, statuses, and scheduled sends across multiple linked devices.MIT
SendKuy MCP serverofficial
AlicenseAqualityBmaintenanceEnables AI assistants and agents to send WhatsApp, SMS, and email messages, verify OTP codes, and run campaigns through an account-based messaging platform.41771 npm1MIT
SendAPI MCP Serverofficial
AlicenseAqualityDmaintenanceEnables any MCP-compatible AI agent to send WhatsApp messages, SMS, OTP codes, and email through a single REST API.18MIT
jetapi-mcp-serverofficial
AlicenseAqualityBmaintenanceOfficial JetAPI MCP server for sending WhatsApp, Telegram (personal account or bot), SMS, VK/OK and MAX messages and files from AI agents. Supports channel cascades, scheduling, bulk mailings, delivery status tracking, phone number lookup and webhook management.1450 npmMIT- AlicenseAqualityCmaintenanceLets AI agents send notifications, manage templates and read delivery status.130 npmMIT
- AlicenseNot 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.23ISC
TDQS
Scored across 19 tools
Most tools target clearly distinct resources and actions, and the descriptions explicitly route users between similar tools such as get_account vs get_balance and send_message vs send_bulk vs send_file. The main residual ambiguity is overlapping account/balance information, so it is not quite perfectly distinct.
All tools use consistent snake_case with predictable verb_noun phrasing such as get_webhook, create_webhook, list_webhooks, and delete_webhook. Singular/plural forms are used appropriately for single-resource versus list operations.
Nineteen tools is above the ideal 3-15 range and feels somewhat heavy for this server's scope. Most tools earn their place, but there is some natural overlap between account/balance and messaging variants that could be tightened.
Core messaging workflows are well covered: send, bulk send, file send, delivery status, deletion, webhook CRUD, account diagnostics, and auth linking. However, sub-customer management has create/list/get but no update or delete, delivery management lacks listing or cancelling operations, and UTM tags are read-only.