Skip to main content
Glama
wazap-mcp

wazap-mcp

by razvangirgiz

Related Servers

Alternatives to wazap-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that connects AI agents to WhatsApp using the multi-device API, enabling messaging, group management, and more as a regular user.
      6 npm
      1
      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.
      29
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that turns WhatsApp into agent-callable tools, enabling search contacts, send/receive messages, read chats, handle media, and monitor calls via the WhatsApp Web multi-device protocol.
      11 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A native MCP server for SocialMate that gives your AI a WhatsApp, enabling it to send and read messages, manage contacts and groups, and more through 44 tools.
      46 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A self-hosted WhatsApp bridge that exposes a stdio MCP server with ~20 tools for reading conversations, sending messages, managing groups, contacts, and aliases, enabling AI agents to operate WhatsApp directly.
      4
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      OpenWA MCP server that bridges AI agents to the OpenWA WhatsApp API, exposing 40 tools for sessions, messages, contacts, groups, and webhooks so agents can read and send WhatsApp messages through a self-hosted OpenWA gateway.
      -

    TDQS

    A3.6/5.0

    Scored across 23 tools

    Disambiguation4/5

    Each tool targets a recognizable slice of the WhatsApp domain (sending drafts, confirming sends, reading chats vs. full messages, groups vs. chats, search vs. catch_up vs. wait_for_messages), and descriptions draw boundaries explicitly. A few pairs like catch_up/wait_for_messages and scheduled_messages/reminder require reading the description to separate, and the multi-action tools (manage_chat, manage_group, reminder, scheduled_messages) bundle several behaviors internally, but overall selection is unambiguous.

    Naming Consistency4/5

    Nearly all names are snake_case with a verb_noun shape (get_status, list_chats, send_message, confirm_send, manage_group, read_messages). Minor deviations are noun-only names for multi-op tools (reminder, scheduled_messages) and bare verbs (search, learn, remember, catch_up), which slightly breaks the pattern but stays readable and predictable.

    Tool Count4/5

    23 tools is on the heavy side of the typical 3-15 band, but the surface is genuinely rich (drafts, media, groups, scheduling, reminders, search, streaming wait) and each tool maps to a real capability. The count is justified by scope rather than redundant, though it sits near the upper edge of comfortable.

    Completeness4/5

    Coverage is broad: link/auth, read/search, draft-then-confirm sending, edit/delete/react, media, contacts, scheduled messages, local reminders, group administration, and status probing. Gaps are minor (posting stories/statuses, own-profile management), which agents can work around without hitting dead ends.

    Maintenance

    ActivityActive
    ResponsivenessLimited data