chatkazi-mcp
Related Servers
Alternatives to chatkazi-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityNot gradedmaintenanceEnables WhatsApp automation through MCP protocol, allowing users to manage sessions, send messages, handle groups/communities, and access contacts through natural language interactions with AI agents.5 npm-
- AlicenseBqualityDmaintenanceEnables sending messages, images, documents and more on WhatsApp directly from any MCP-compatible AI, with tools for chat management, groups, and webhooks.371MIT
- FlicenseNot gradedqualityCmaintenanceBridge WhatsApp Business Cloud API to MCP-compatible clients, enabling AI assistants to read, search, and send WhatsApp messages.3 npm1-
- AlicenseNot gradedqualityCmaintenanceIntegrates WhatsApp with AI agents, enabling message sending, chat search, media sharing, approval workflows, and activity summaries via any MCP client.1Apache 2.0

green-api-mcp-gatewayofficial
AlicenseNot gradedqualityCmaintenanceMCP gateway for GREEN-API WhatsApp that lets AI agents send messages, manage instances, and receive notifications via WhatsApp using the Model Context Protocol.MIT- FlicenseNot gradedqualityNot gradedmaintenanceA self-hosted MCP server that connects AI clients to WhatsApp via the WAHA HTTP API. It enables users to manage sessions, search contacts, and send or receive messages and media directly through natural language interfaces.12 npm-
TDQS
Scored across 7 tools
Each tool targets a distinct action: session management (list, start, status, QR, logout) versus messaging (text, media). No two tools have overlapping purposes, and the descriptors clearly differentiate them.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., list_sessions, start_session, send_whatsapp_text). The pattern is uniform and predictable across the set.
Seven tools is well-scoped for a WhatsApp MCP server covering session lifecycle and message sending. Each tool serves a necessary function without redundancy or bloat.
The tool set covers the full session lifecycle (initiate, check status, retrieve QR, log out, list) and both primary message types (text and media). No obvious gaps for the stated domain.