Skip to main content
Glama
Sign In
Blueticks WhatsApp MCP

Blueticks WhatsApp MCP

by serenix-com
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Blueticks WhatsApp MCP

No user-submitted related servers found.

    Related Servers

    • 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.
      42 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

      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.
      -

    • 9bot

      9-bot
      A
      license
      Not graded
      quality
      A
      maintenance
      Automate and manage WhatsApp groups, communities, and channels with scheduling, moderation, analytics, and more.
      1
      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.9/5.0

    Scored across 9 tools

    Disambiguation4/5

    Each top-level tool maps to a distinct resource (messages, chats, contacts, groups, audiences, campaigns, webhooks, engine, utils), so an agent can pick the right one by domain. The main gray area is sending: scheduled_messages.send can also send 'now', overlapping with chats.send_message_text/media/poll, and chats.list vs groups.list both return group-ish entities — but the descriptions explicitly clarify the intended split.

    Naming Consistency4/5

    Consistent plural-resource noun naming with a uniform 'action' sub-parameter pattern (send/get/list/update/cancel) throughout all nine tools. Minor deviations: singular tools (engine, utils) and a few noun-style action names (common_groups, get_media) break the pure verb pattern, but the scheme is predictable.

    Tool Count5/5

    Nine top-level tools is well-scoped for a WhatsApp automation server, and each maps to a coherent domain object rather than exposing every operation as its own tool. Heavy sub-action surfaces (e.g. chats) are grouped logically rather than sprawling the tool list.

    Completeness4/5

    Broad coverage: send/receive, scheduled queue, contacts, groups, audiences, campaigns, webhooks, and engine status — a full lifecycle for messaging automation. Gaps remain around destructive/engagement operations: no message delete/revoke or reaction, and group membership management lacks add/remove/promote participant actions despite group creation.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources