Skip to main content
Glama
jppeiro90

MCP-WHATSAPP-EVO

by jppeiro90
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to MCP-WHATSAPP-EVO

No user-submitted related servers found.

    Related Servers

    • mcp-evolution

      billyfranklim1
      A
      license
      B
      quality
      C
      maintenance
      MCP server that integrates Evolution API to enable WhatsApp messaging, chat management, group operations, and instance control through natural language tools.
      54
      1
      MIT

    • Evolution API MCP Server

      serversmx
      A
      license
      B
      quality
      C
      maintenance
      Exposes the Evolution API v2 (WhatsApp) as 121 tools for MCP clients, enabling management of instances, messages, chats, groups, profiles, labels, webhooks, and integrations.
      64
      9 npm
      MIT

    • mcp-evolution-api

      pauloFroes
      F
      license
      A
      quality
      D
      maintenance
      MCP server that wraps the Evolution API (WhatsApp) as semantic tools for LLM agents, enabling messaging, chat management, group operations, and instance control via natural language.
      32
      -

    • WhatsApp MCP Stream

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

    C2.9/5.0

    Scored across 70 tools

    Disambiguation4/5

    Each tool targets a distinct action, but there is some overlap between send_media (which can send audio) and send_whatsapp_audio (voice note), and between send_media and send_ptv (round video). Agents may occasionally misselect between these. Overall, most tools have clear boundaries.

    Naming Consistency3/5

    Naming follows snake_case but uses a mix of verbs: get, fetch, find for retrieval; send, update, set for actions. Inconsistencies like get_connection_state vs fetch_profile, and send_chat_presence vs set_evolution_presence reduce predictability.

    Tool Count2/5

    70 tools is excessive for a typical MCP server. While each tool serves a specific purpose, the high number makes the surface unwieldy and increases selection difficulty. A consolidated API with fewer but more flexible tools would improve coherence.

    Completeness5/5

    The tool set covers nearly all WhatsApp operations: instance lifecycle, messaging (text, media, reactions, polls, templates, status), group management (create, update, invite, participants), profile, privacy, and webhooks. Only minor gaps like deleting a chat or forwarding messages exist, making it very complete for its domain.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources