SendKuy MCP server
OfficialRelated Servers
Alternatives to SendKuy MCP server
No user-submitted related servers found.
Related Servers
AlicenseAqualityDmaintenanceEnables any MCP-compatible AI agent to send WhatsApp messages, SMS, OTP codes, and email through a single REST API.18MIT
ChatPush MCP Serverofficial
AlicenseAqualityBmaintenanceEnables AI agents to send WhatsApp, Telegram, SMS, VK/OK, and MAX messages, files, and bulk mailings, and to manage delivery status, webhooks, and sub-accounts.19336 npm18MIT- FlicenseNot gradedqualityBmaintenanceEnables AI assistants to interact with WhatsApp by sending messages, triaging urgent conversations, scheduling messages, and managing automated replies with safety controls and human approval.-
- AlicenseBqualityCmaintenanceEnables AI assistants to manage WhatsApp business operations including chatbots, broadcasts, campaigns, and contacts through 120+ MCP tools.10046 npmMIT
- AlicenseAqualityDmaintenanceConnects AI assistants to the official Meta WhatsApp Cloud API for managing conversations and sending various message types through natural language. It provides tools for media management, template messages, and real-time webhook processing without the risk of account bans.1827MIT
- AlicenseNot gradedqualityBmaintenanceWhatsApp, Instagram, Telegram, SMS, Messenger & email in one AI-ready inbox. Manage conversations, send omnichannel messages, run campaigns, sync contacts, and query your knowledge base — 42 tools over a hosted, OAuth-secured MCP server.2MIT
TDQS
Scored across 17 tools
Every tool targets a distinct resource+action, and the descriptions explicitly cross-reference each other to draw the boundaries (send_message vs send_batch by uniform vs per-recipient content, get_messages vs list_messages by id vs filter, start_campaign vs control_campaign by lifecycle stage). The only surface overlap — sending to a group via send_message's `to` field versus starting a dashboard campaign — is called out in both descriptions, leaving little room for misselection.
All 17 tools use the same `sendkuy_` prefix plus a consistent snake_case verb_noun pattern (send_message, list_messages, get_campaign, control_campaign, check_whatsapp_numbers). No mixed casing or stray verb styles anywhere in the set.
17 tools is on the heavier side of the ideal band, but the surface genuinely spans several sub-domains — messaging, verification, contacts/groups/templates, campaigns, and webhook diagnostics — and each tool maps to a real operation rather than a thin wrapper. Nothing appears redundant enough to remove.
The send/read/cancel lifecycle for messages and full campaign control are well covered, but most supporting resources are read-only: contacts, groups, templates, and webhook subscriptions can only be listed or found, never created or updated, and campaign content must be authored in the dashboard. These are workable gaps for a send-focused agent but leave notable dead ends in the management surface.