Skip to main content
Glama
HardikCoder45

WhatsApp MCP Server

by HardikCoder45
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to WhatsApp MCP Server

No user-submitted related servers found.

    Related Servers

    • WhatsApp MCP

      ionutsss1
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to read, search, and send personal WhatsApp messages and files through a locally linked device.
      20 npm
      MIT

    • WhatsApp MCP

      mcp-dir
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables connecting a personal or business WhatsApp account via QR pairing and then sending/reading messages, managing chats, contacts, groups, and searching message history through MCP tools.
      MIT

    • whatsapp-mcp

      vimal-v-2006
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents and MCP clients to read and send WhatsApp messages and media, search chats, and manage contacts and groups after a one-time QR pairing.
      20 npm
      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

    • WA MCP

      cecon
      A
      license
      Not graded
      quality
      A
      maintenance
      Exposes each authenticated WhatsApp Web session on a Windows PC as a stateless Streamable HTTP MCP endpoint, letting MCP clients list chats, read and search messages, fetch profiles, and send text messages under per-session read-only or read-and-send permissions.
      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

    A3.5/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools target distinct operations, but list_chats vs fetch_all_chats and read_messages vs fetch_message_history have overlapping purposes. Their descriptions clarify the differences (default-capped vs all chats, recent vs older history), so misselection is possible but manageable.

    Naming Consistency4/5

    Nearly all tools follow a consistent snake_case verb_noun pattern: list_chats, search_messages, read_messages, send_message, etc. Minor deviations are fetch_all_chats vs list_chats for similar listing actions and connection_status lacking a clear verb.

    Tool Count5/5

    Nine tools is well-scoped for a local WhatsApp MCP server. Each tool covers a distinct capability such as connection status, chat listing, message reading/searching, media handling, and sending.

    Completeness4/5

    The server covers core messaging workflows: connection state, chat discovery, message reading/searching/history, media download, and guarded sending. Some gaps remain, such as contact/group metadata, message reactions, or chat creation, but the essential read/send surface is present.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources