Skip to main content
Glama
gfb-47

WhatsApp MCP Server

by gfb-47
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to WhatsApp MCP Server

No user-submitted related servers found.

    Related Servers

    • WhatsApp Web MCP

      pnizer
      A
      license
      Not graded
      quality
      D
      maintenance
      A Node.js application that connects WhatsApp Web with AI models through the Model Context Protocol, enabling automated messaging, contact management, and group chat functionality through AI-driven workflows.
      27 npm
      44
      MIT

    • imessage-send-mcp

      andyjianzhou
      A
      license
      A
      quality
      D
      maintenance
      Enables sending iMessages or SMS messages via the macOS Messages app using osascript. No Full Disk Access required, and never reads your message history.
      1
      MIT

    • whatsapp-mcp

      rubickthemagus
      A
      license
      A
      quality
      C
      maintenance
      Lets you read WhatsApp history from the macOS app's own SQLite database without QR pairing or ban risk, with optional token-gated replying.
      7
      MIT

    • whatsapp-mcp

      Pl3ntz
      A
      license
      A
      quality
      C
      maintenance
      MCP server that gives AI agents read and write access to WhatsApp on macOS, reading local chat history offline and sending messages via pre-filled drafts with explicit user confirmation.
      8
      MIT

    • claude-whatsapp-mcp

      ferazfhansurie
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude Code to interact with WhatsApp for reading messages, sending replies, and searching contacts through the Model Context Protocol. It uses whatsapp-web.js to facilitate local connection management with QR code authentication and session persistence.
      4
      MIT

    • ChatRail MCP

      pedroantonnio
      A
      license
      Not graded
      quality
      B
      maintenance
      Lets AI runtimes and tools drive a local WhatsApp session through an HTTP-backed stdio interface, supporting message sending, chat listing, unread counters, replies, and read-state management. It keeps the WhatsApp provider in a single process so integrations can automate messaging without starting a competing session.
      0
      1
      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.1/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: checking WhatsApp status, listing recent contacts, and sending messages. There is no overlap in functionality, making it easy for an agent to select the correct tool without confusion.

    Naming Consistency4/5

    The tools follow a consistent verb-noun pattern with hyphens (e.g., check-whatsapp-status, list-recent-contacts, send-whatsapp-message). However, the use of hyphens instead of underscores is a minor deviation from common snake_case conventions, but it remains readable and predictable.

    Tool Count3/5

    With only 3 tools, the server feels thin for managing WhatsApp interactions, as it lacks operations like reading messages, managing groups, or handling media. While the tools cover basic actions, the scope is limited, making it borderline appropriate for a comprehensive WhatsApp integration.

    Completeness2/5

    The toolset is significantly incomplete for a WhatsApp server, missing essential CRUD operations such as reading incoming messages, replying to messages, managing contacts or groups, and handling attachments. This will likely cause agent failures when trying to perform common WhatsApp tasks beyond the basic ones provided.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources