jetapi-mcp-server
OfficialRelated Servers
Alternatives to jetapi-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceMCP server for ManyContacts WhatsApp Business CRM that enables AI agents to manage contacts, send messages, run campaigns, and configure auto-replies through comprehensive CRM operations.5555 npmMIT
- AlicenseAqualityBmaintenanceMCP server for Kirimi WhatsApp API, enabling AI agents to send messages, broadcast, manage devices, and contacts.1914 npmMIT

lingtai-whatsappofficial
AlicenseNot gradedqualityFmaintenanceMCP server for interacting with the official Meta WhatsApp Business Platform/Cloud API, enabling sending messages, managing contacts, templates, and handling webhook callbacks.Apache 2.0
SendAPI MCP Serverofficial
AlicenseAqualityDmaintenanceEnables any MCP-compatible AI agent to send WhatsApp messages, SMS, OTP codes, and email through a single REST API.18MIT- FlicenseNot gradedqualityCmaintenanceRemote MCP server for Leporis WhatsApp Business platform, enabling AI agents to send and read WhatsApp messages through exposed REST API tools.-
- AlicenseBqualityCmaintenanceMCP server that enables AI agents to operate WhatsApp via Visto Azul API: send text, media, PIX charges, manage campaigns and contacts, and configure webhooks using natural language.119 npmMIT
TDQS
Scored across 14 tools
Most tools are clearly separated by resource and action (balance vs account vs delivery vs webhooks). The only potential confusion is get_balance vs get_account, but the descriptions explicitly differentiate them, and send_message vs send_bulk vs send_file are well delineated.
All tool names follow a consistent verb_noun pattern: get_*, send_*, create_*, list_*, update_*, delete_*. The verbs are predictable and the nouns clearly indicate the resource, making the API surface easy to navigate.
14 tools is well within the ideal range for a messaging API server. Each tool covers a distinct operation: account info, messaging (single, bulk, file), delivery tracking, phone lookup, and webhook management. No tool feels redundant or unnecessary.
The tool surface covers the core messaging lifecycle well: send (message/bulk/file), track (get_delivery_status), and delete (delete_delivery). Webhook CRUD is complete. Minor gaps include no explicit tool for listing sent messages or managing contacts, but these are not essential for the stated purpose.