Skip to main content
Glama
billyfranklim1

mcp-evolution

by billyfranklim1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-evolution

No user-submitted related servers found.

    Related Servers

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

    • mcp-zap

      Joaquim-Salles
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for sending and receiving WhatsApp messages through Evolution API, enabling management of instances, messages, and chats directly from Claude Code.
      -

    • whatsapp-mcp-evolution

      tzolkin-collab
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server that integrates WhatsApp via the Evolution API v2, enabling AI assistants to manage WhatsApp instances, send text/media messages, configure Typebot flows, and set up webhooks. It uses SSE transport and is designed for single-tenant deployments.
      -

    • MCP-WHATSAPP-EVO

      jppeiro90
      A
      license
      C
      quality
      D
      maintenance
      Exposes the full WhatsApp API via Evolution API, enabling message sending, chat history, group management, and more through MCP tools.
      70
      MIT

    • whats-mcp

      SaptodeepSarkar
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that turns WhatsApp into agent-callable tools, enabling search contacts, send/receive messages, read chats, handle media, and monitor calls via the WhatsApp Web multi-device protocol.
      2 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 54 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose. Even similar actions (e.g., send_media vs send_audio) are precisely differentiated by description. No two tools overlap in function.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern (e.g., send_text, update_group_subject, fetch_privacy). No mixing of camelCase or other conventions, making the set predictable.

    Tool Count2/5

    54 tools is well above the 25+ threshold, making the server feel heavy and potentially overwhelming for agents. While the domain is broad, the count could be reduced by combining or omitting rarely used tools.

    Completeness4/5

    The tool set comprehensively covers WhatsApp messaging, groups, instance management, and profile operations. Minor gaps exist (e.g., no forward message or fetch status updates) but do not critically impair core workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources