Skip to main content
Glama
Vinix-Code-Dev

Wasapi MCP Server

by Vinix-Code-Dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Wasapi MCP Server

No user-submitted related servers found.

    Related Servers

    • Uazapi WhatsApp MCP Server

      pabloweyne
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables interaction with WhatsApp through the Uazapi API, allowing users to send text and media messages, manage contacts, and list conversations through natural language.
      -

    • WSAPI WhatsApp MCP Server

      wsapi-chat
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to interact with WhatsApp through the WSAPI service, supporting comprehensive messaging, contact management, group operations, and account management functionality. Allows sending various media types, managing chats, and controlling WhatsApp sessions through natural language.
      101
      403 npm
      3
      MIT

    • WhatsApp MCP

      brunotrolo
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables an assistant to send WhatsApp messages, images, documents, and voice alerts with delivery confirmations, read incoming messages for two-way interaction, and check connection status.
      13 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

    B3.4/5.0

    Scored across 62 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, with detailed descriptions. Metrics tools like get_agent_time_in_conversation and get_agent_time_response are specific. However, the sheer number of tools (62) could still cause some confusion, and tools like list_conversations vs get_conversation serve different functions but may be misunderstood.

    Naming Consistency4/5

    The naming follows a consistent verb_noun pattern with snake_case (e.g., get_contact, list_contacts, create_label). Minor deviations like change_conversation_status instead of update_conversation_status exist, but overall it's predictable and readable.

    Tool Count3/5

    With 62 tools, the count is high but arguably appropriate for a comprehensive WhatsApp API server covering contacts, conversations, campaigns, flows, templates, metrics, and more. However, it feels heavy for typical use, and some tools could be consolidated (e.g., multiple agent metrics).

    Completeness4/5

    The tool set covers CRUD operations for most entities (contacts, labels, custom fields, templates), sending various message types (text, attachment, flow, template), metrics, and workflow management. Missing: conversation deletion, campaign updates, and direct conversation ID lookup (get_conversation only by wa_id). Still, it's quite thorough.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources