Skip to main content
Glama
aiteks-ltda

MCP Evolution API

by aiteks-ltda
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to MCP Evolution API

No user-submitted related servers found.

    Related Servers

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

      jlucaso1
      A
      license
      C
      quality
      F
      maintenance
      A Model Context Protocol server that connects your personal WhatsApp account to AI agents like Claude, enabling them to search messages, view contacts, retrieve chat history, and send messages via WhatsApp.
      7
      12 npm
      73
      ISC

    • WhatsApp MCP

      PONMANIAN-SA
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables interaction with WhatsApp through local stdio or remote HTTP/SSE connections. It allows users to send messages, manage groups, and access chat history using natural language.
      13 npm
      3
      MIT

    • claude-whatsapp-mcp

      ju-li
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude to manage WhatsApp instances through the Evolution API, including listing instances and sending text messages.
      MIT

    • WhatsApp MCP

      wsti-studio
      F
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that gives Claude read and write access to WhatsApp through a self-hosted Evolution API gateway. It is dependency-free, using Node's built-in fetch and stdio transport.
      -
    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.2/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools, as there are no other tools to compare it against. The single tool's purpose is inherently distinct by default.

    Naming Consistency5/5

    A single tool cannot demonstrate inconsistency, as there are no other tool names to compare it to. The naming pattern for 'hello_tool' (snake_case) is consistent within the set, albeit trivially so.

    Tool Count2/5

    A single tool is generally too few for most server purposes, as it limits functionality and suggests an incomplete or trivial implementation. While it might be appropriate for a minimal 'hello world' server, it is inadequate for any substantive domain coverage.

    Completeness1/5

    With only one tool named 'hello_tool', it is impossible to infer a meaningful domain or assess coverage. There are obvious gaps, as no CRUD operations, lifecycle management, or typical API interactions are present, making the surface severely incomplete for any practical purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources