Skip to main content
Glama
mcp-whatsapp

mcp-whatsapp

Related Servers

Alternatives to mcp-whatsapp

  • A
    license
    A
    quality
    C
    maintenance
    Enables Claude to interact with WhatsApp on macOS through the Model Context Protocol. It allows reading messages, searching contacts, listing chats, and sending replies via natural conversation.
    8
    58 PyPI
    2
    MIT
  • A
    license
    B
    quality
    D
    maintenance
    A comprehensive MCP server providing Claude with full access to Brevo's marketing automation platform through the official SDK, featuring tools for email operations, contact management, campaigns, SMS, conversations, webhooks, e-commerce, and account management.
    16
    3
    MIT
  • A
    license
    B
    quality
    D
    maintenance
    An MCP server that enables AI to control WhatsApp Web via Puppeteer Stealth for reading and sending messages. It features human-like interaction patterns and anti-ban protections to securely manage chats and communications through natural language.
    3
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    Enables AI assistants to interact with WhatsApp through the WSAPI service, supporting comprehensive messaging, contact management, group operations, and account management functionality. Allows sending various media types, managing chats, and controlling WhatsApp sessions through natural language.
    101
    20 npm
    4
    MIT

Related Servers

  • A
    license
    B
    quality
    B
    maintenance
    Full-featured personal WhatsApp MCP server: read and full-text search all chats, send, reply, react, edit and delete, media as raw files, groups and communities, multi-account and live notifications. Rust server with a Go whatsmeow bridge, local SQLite.
    39
    4
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    WhatsApp MCP server that exposes messaging, groups, contacts, and profile management as tools and resources for AI agents, supporting Baileys and Meta Cloud API.
    79 npm
    29
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    MCP server for WhatsApp that exposes send, read, and media management tools through the waxum REST API gateway, enabling any MCP client to interact with WhatsApp chats and media over stdio.
    2
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    A least-privilege, send-only MCP server for WhatsApp, backed by Meta's official WhatsApp Cloud API. It exposes tools to send text messages and pre-approved templates.
    8 npm
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    A secure, zero-setup WhatsApp MCP server that lets AI assistants read, search, summarize, and (with user confirmation) act on personal WhatsApp chats via a safety-focused toolset, built as a maintained successor to the abandoned whatsapp-mcp.
    5
    MIT

TDQS

A4.1/5.0

Scored across 43 tools

Disambiguation4/5

Most tools have clearly distinct resource+action targets (e.g. send_message vs send_reply vs send_reaction, mark_read vs mark_chat_read, list_chats vs list_groups). A few pairs overlap conceptually—get_status vs pairing_status both report connection/pairing state, and set_presence vs send_typing are adjacent presence concepts—but the descriptions explicitly cross-reference each other to steer selection.

Naming Consistency4/5

The surface is overwhelmingly consistent snake_case verb_noun (list_groups, send_file, set_group_locked, update_group_participants). Minor deviations like is_on_whatsapp (question form) and pairing_status (noun phrase rather than verb_noun) are readable but break the pattern slightly.

Tool Count2/5

43 tools is heavy even for a broad messaging domain; several send_* and set_group_* variants could plausibly be consolidated (e.g. one send_media with a type parameter, one set_group_setting). The count makes the surface harder to scan and increases selection risk.

Completeness4/5

Coverage is strong: sending (text, reply, media, audio, contact card, poll), editing/deleting, group lifecycle and admin settings, privacy, blocklist, presence, media download, sync, and transcription. Gaps are modest—no location/sticker sending, no chat mute/archive, no profile-picture retrieval—but core workflows are complete.

Maintenance

ActivityActive
ResponsivenessUsually handled