Skip to main content
Glama
edouard-claude

whatsapp-mcp

by edouard-claude
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

Related Servers

Alternatives to whatsapp-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-whatsapp

      Sealjay
      A
      license
      A
      quality
      B
      maintenance
      Single-binary Go MCP server that wraps whatsmeow to expose a personal WhatsApp account as 41 MCP tools (messaging, groups, polls, media, privacy).
      42
      13
      MIT

    • whatsapp-mcp-plus

      eeshsaxena
      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

    • waxum-mcp

      imtaqin
      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

    • WhatMCP

      pedroschott
      A
      license
      Not graded
      quality
      D
      maintenance
      A local MCP server that provides a durable, searchable archive of your WhatsApp history using hybrid retrieval to navigate conversations.
      4
      MIT

    • parley

      Sachitt-AV-08
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients to read WhatsApp chats and send, reply, react to, and schedule messages on the WhatsApp Desktop already logged in locally. All traffic stays on 127.0.0.1, with human-like pacing and verified delivery rather than cloud APIs or QR logins.
      2
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 39 tools

    Disambiguation4/5

    Most tools target a distinct resource+action (send_message vs edit_message vs delete_message vs react; list_messages vs list_recent vs get_message_context). A few could be mildly confused, such as get_contact vs get_profile vs get_chat, and list_join_requests vs handle_join_requests, but the descriptions clearly differentiate them.

    Naming Consistency4/5

    The set is consistently snake_case and predominantly verb_noun (send_message, create_group, update_group, delete_message). A handful deviate with noun-only or ambiguous names (blocklist, react, group_invite_link, privacy_settings), but the pattern remains largely readable.

    Tool Count3/5

    39 tools is heavy and pushes into the crowded range, even though the WhatsApp domain (messaging, groups, communities, sessions, privacy, media, presence) is genuinely broad. Most tools earn their place, but the surface is large enough to burden selection.

    Completeness5/5

    Coverage is extensive: full messaging CRUD, groups and communities, participants, sessions (pair/logout/status), privacy settings, presence, media, polls, contacts, search, and history backfill. Little of the domain appears to be missing.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources