Skip to main content
Glama
Sealjay

mcp-whatsapp

by Sealjay

Related Servers

Alternatives to mcp-whatsapp

  • A
    license
    A
    quality
    B
    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
    41 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
    131 npm
    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
    11 npm
    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
    14 npm
    3
    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
    2
    MIT
  • A
    license
    Not graded
    quality
    C
    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.
    26
    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
    B
    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.2/5.0

Scored across 42 tools

Disambiguation4/5

Most tools target clearly distinct resources or actions, and descriptions explicitly cross-reference alternatives such as send_presence vs send_typing and send_file vs send_audio_message. Minor overlap remains between get_status and pairing_status, and between mark_read and mark_chat_read, but careful reading resolves the ambiguity.

Naming Consistency4/5

The set is predominantly snake_case with a verb_noun pattern (send_message, get_chat, set_group_name, list_messages). A few outliers break the pattern, notably pairing_status as a noun phrase and is_on_whatsapp as a predicate, but the convention is still mostly predictable.

Tool Count2/5

42 tools is well above the typical 3–15 range for an MCP server and exceeds the 25+ threshold. While WhatsApp is a broad domain, several tools could be consolidated (e.g., status/pairing, read-marking, group setting updates), making selection unnecessarily heavy.

Completeness5/5

The surface covers a very full WhatsApp lifecycle: sending, editing, deleting, replying, reacting, media download, message search/context, group creation/join/leave/settings/participants, blocking, privacy, presence, polls, contacts, sync, and pairing/status. Core workflows have no obvious dead ends.

Maintenance

ActivityMaintained
ResponsivenessSlow