Skip to main content
Glama
Sign In
wuapi MCP server

wuapi MCP server

Official
by wuapidev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to wuapi MCP server

No user-submitted related servers found.

    Related Servers

    • WhatsApp MCP Gateway

      NabuxAi
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables authenticated MCP clients to manage multiple WhatsApp Business numbers through Meta's official Cloud API, including webhook-backed contact and conversation search, message history, and sending text, templates, or media within policy limits.
      MIT

    • WhatsApp MCP Stream

      BusinessNone
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables programmatic WhatsApp automation through MCP, including sending messages, managing chats and contacts, searching conversation history, and exchanging media files.
      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.
      45 npm
      MIT

    • whatsapp_MCP

      CyberPixelMarketing
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables linking a WhatsApp number via QR code and then sending, reading, listing chats, and checking status through MCP tools, with per-account API key authentication.
      -

    • 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.
      45 npm
      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.6/5.0

    Scored across 87 tools

    Disambiguation4/5

    The tools mostly target clearly distinct resources and actions, and the rich descriptions clarify overlaps like list_messages vs manage_channel.list_messages or get_contact vs lookup_contacts. A few umbrella tools (manage_labels, manage_channel, manage_stories) and similarly named contact/chat tools could still require careful reading, but genuine misselection is limited.

    Naming Consistency5/5

    Names consistently use snake_case and mostly follow a verb_noun pattern (send_text, get_chat, create_group, manage_channel). The repeated manage_* convention for multi-action resources is predictable, and there are no style collisions such as camelCase or vague single-word tools.

    Tool Count2/5

    Eighty-seven tools is very large even for a broad WhatsApp API surface, and many tools bundle multiple actions internally, making the external surface unusually heavy. The domain is extensive, but the set would benefit from consolidation or clearer grouping.

    Completeness5/5

    Coverage is exceptionally broad: accounts, messaging, media, chats, contacts, groups, communities, channels, stories, labels, privacy, webhooks, projects, invitations, billing, and more. The tool surface handles lifecycle operations and edge cases with few obvious dead ends.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues

    Resources