Skip to main content
Glama
pauloFroes

mcp-evolution-api

by pauloFroes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to mcp-evolution-api

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

    • WA MCP

      delltrak
      F
      license
      Not graded
      quality
      C
      maintenance
      WhatsApp MCP server that exposes messaging, groups, contacts, and profile management as tools and resources for AI agents, supporting Baileys and Meta Cloud API.
      22
      -

    • vistoazul-mcp

      vistoazul
      A
      license
      B
      quality
      B
      maintenance
      MCP server that enables AI agents to operate WhatsApp via Visto Azul API: send text, media, PIX charges, manage campaigns and contacts, and configure webhooks using natural language.
      11
      9 npm
      MIT

    • 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.
      -
    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.5/5.0

    Scored across 32 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (send_text, send_audio, send_media, etc.), but some ambiguity exists between generic send_media and specific types like send_audio/send_sticker, and find_chats vs list_groups could be confusing. Descriptions mostly resolve these, but not perfectly.

    Naming Consistency4/5

    Tools predominantly follow a verb_noun snake_case pattern (send_*, fetch_*, find_*, update_*), but 'group_participants' is a noun phrase without a verb, breaking the otherwise consistent pattern.

    Tool Count2/5

    With 32 tools, the surface is large and exceeds the typical well-scoped range. Several sending tools could be consolidated (e.g., send_media could cover audio/sticker), and the count feels heavy for the domain.

    Completeness4/5

    The set covers sending all message types, chat retrieval, group management, profile access, and connection status. Minor gaps like chat deletion or contact creation exist, but core workflows are well covered and missing features are easily worked around.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources