Skip to main content
Glama
YCloud-Developers

YCloud WhatsApp API MCP Server

by YCloud-Developers
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to YCloud WhatsApp API MCP Server

No user-submitted related servers found.

    Related Servers

    • WhatsApp MCP Server

      msaelices
      A
      license
      B
      quality
      D
      maintenance
      A Python server that enables language models like Claude to interact with WhatsApp Business API through GreenAPI, supporting features like sending messages and managing groups.
      5
      13 PyPI
      27
      MIT

    • mcp-whatsapp-claude

      PedroSodrr10
      A
      license
      Not graded
      quality
      C
      maintenance
      A local MCP server that connects WhatsApp to Claude via QR code, enabling chat listing, message retrieval, and sending with automatic rate limiting for anti-ban protection.
      36 npm
      MIT

    • WhatsApp Desktop MCP

      srijonbasak
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that connects WhatsApp Web to AI tools like Gemini and Claude, providing chat reading, messaging, and a local CRM with draft-and-approve workflows.
      MIT

    • WhatsApp MCP Server

      jlucaso1
      A
      license
      C
      quality
      F
      maintenance
      A Model Context Protocol server that connects your personal WhatsApp account to AI agents like Claude, enabling them to search messages, view contacts, retrieve chat history, and send messages via WhatsApp.
      7
      3 npm
      74
      ISC
    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

    C2.8/5.0

    Scored across 19 tools

    Disambiguation4/5

    Most tools have distinct purposes targeting specific WhatsApp API resources (WABAs, messages, phones, templates) with clear action verbs. However, wa_msg_send and wa_msg_send_directly could cause confusion as they both send messages with only a delivery timing distinction that might not be immediately clear from the names alone.

    Naming Consistency5/5

    All tool names follow a consistent snake_case pattern with a clear wa_resource_action structure (e.g., wa_business_list, wa_msg_send, wa_template_create). The naming convention is predictable and uniform across all 19 tools, making them easily parsable.

    Tool Count4/5

    With 19 tools, the count is slightly high but reasonable for a comprehensive WhatsApp API server covering multiple resource types (businesses, messages, phones, templates). It provides detailed operations without being overwhelmingly large, though it borders on the heavy side.

    Completeness5/5

    The tool set offers complete CRUD/lifecycle coverage for all key WhatsApp API domains: WABAs (list/retrieve), messages (send/retrieve/mark read), phone numbers (list/register/retrieve/update settings and profile), and templates (create/edit/get/list/delete). No obvious gaps exist for typical agent workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources