Skip to main content
Glama
rukman7

whatsapp-mcp-server

by rukman7
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to whatsapp-mcp-server

No user-submitted related servers found.

    Related Servers

    • mcp-whatsapp-giulia-ai

      wganalytics
      A
      license
      A
      quality
      C
      maintenance
      Enables LLM agents to operate WhatsApp through the Evolution API, providing tools to list groups, fetch message history, and send text messages to groups or individual phone numbers.
      4
      MIT

    • WAHA WhatsApp MCP Server

      Maheidem
      A
      license
      A
      quality
      C
      maintenance
      Enables Claude to interact with WhatsApp through a unified backend API, providing 20 tools for messaging, media, groups, contacts, and chat management.
      22
      29 npm
      MIT

    • OpenWA MCP Server

      ExoCubeYT
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to manage WhatsApp sessions, send multi-format messages, control group participants, and configure webhooks by wrapping the OpenWA REST API with 44 tools.
      44
      2
      MIT

    • WAHA MCP Server

      dudu1111685
      A
      license
      B
      quality
      B
      maintenance
      Bridges the WhatsApp HTTP API with AI assistants to enable full control over messaging, chat management, and interactive workflows through 63 specialized tools. It allows users to automate WhatsApp tasks and receive real-time AI feedback directly on their mobile devices.
      63
      12 npm
      5
      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

    A4.1/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool targets a distinct action: one per message media type (text, image, document, location, contact, reaction, buttons, list), plus mark-as-read and profile/template management. No two tools overlap in purpose, even the interactive buttons and list messages are clearly differentiated by their payload structures.

    Naming Consistency5/5

    All tools follow a uniform 'whatsapp_verb_noun' pattern: send_text, send_image, get_business_profile, list_templates, etc. The snake_case convention is consistently applied, and verbs are descriptive and non-repetitive across the set.

    Tool Count5/5

    13 tools is well within the ideal range for a domain-focused server. The count reflects a comprehensive but not bloated surface: nine send methods, one acknowledgment, two profile operations, and one template listing. Each tool earns its place.

    Completeness4/5

    The core send capabilities are thorough (text, template, media, interactive), and profile management is covered with both get and update. Minor gaps exist: no video/audio send tools and no create/delete template operations, but these are peripheral to the primary send and profile workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources