Name: MCP Evolution API
Author: aiteks-ltda

LABSCO SUMMARY

The sending side of WhatsApp automation, wired to a deployment you control.

Sending is where this is complete: text, media, audio, stickers, locations, contact cards, reactions, polls, lists and buttons all go out, and the instance lifecycle is covered end to end. Reading is narrower — contacts, chats and group membership are there, message history and profile editing are not — so treat it as an outbound channel with enough read access to address messages correctly.

What it is

A server in front of Evolution API, the self-hosted WhatsApp automation layer. It manages the connection instances, sends the full range of WhatsApp message types, and reads contacts, chats and groups.

What you get

Instances created, connected, restarted, logged out and deleted, with the connection state readable at any point
Plain text, media, WhatsApp audio, stickers, locations, contact cards and status posts sent
Interactive messages — polls, lists and buttons — plus reactions to an existing message
Presence set on an instance
Contacts and chats listed
Groups fetched by identifier or in bulk, with their member lists
Webhooks and instance settings written and read back

Requirements

A running Evolution API deployment — its base URL and an API key, supplied as environment settings. You build it from source with npm and run it under Node.

Setup effort

Build from source — git clone https://github.com/aiteks-ltda/mcp-evolution-whatsapp-api.git

See installation options

USE CASES

01

Sending a notification to a customer on WhatsApp

Send the text, a media file, a location or a contact card through your own Evolution deployment rather than a third-party gateway.

02

Asking a question that fits in a tap

Send a poll, a list or a button message so the recipient can answer with a tap. The answers do not come back through this server: no tool reads message history.

03

Getting a number connected

Create the instance, connect it, and check the connection state before you send anything; restart or log out from the same place.

04

Working out who to message

Pull the contact and chat lists, or fetch a group and its members, to resolve the recipient before sending.

05

Routing inbound events somewhere

Point the instance's webhook at your own endpoint and read the settings back to confirm they took.

30 tools

Listed in project code.

`create_evolution_instance`

Create a new WhatsApp instance using Evolution API

BEFORE YOU INSTALL

What to know first

Tools you get

30 tools registered in the project's code. some_function is left over from the starter template the project was built on: an example tool that only returns a hello greeting. The other 29 are the Evolution API tools.

Requires

Node.js and npm (to build and run dist/main.js)
A running Evolution API instance
EVOLUTION_API_URL in your environment
EVOLUTION_API_KEY in your environment

Where it runs

The documented client runs the server on your machine.

INSTALLATION

Connect your client

You clone and build this one yourself.

Server setup

TERMINAL

git clone https://github.com/aiteks-ltda/mcp-evolution-whatsapp-api.git
cd mcp-evolution-whatsapp-api
npm install
npm run build

MCP Clients

Claude Desktop

CLAUDE DESKTOP · JSON

{
  "mcpServers": {
    "evo-api": {
      "command": "node",
      "args": [
        "<YOUR_PATH_TO_MCP_EVOLUTION_WHATSAPP_API>/dist/main.js"
      ],
      "env": {
        "EVOLUTION_API_URL": "<YOUR_EVOLUTION_API_URL>",
        "EVOLUTION_API_KEY": "<YOUR_EVOLUTION_API_KEY>"
      }
    }
  }
}

MCP Evolution API

The sending side of WhatsApp automation, wired to a deployment you control.

What it is

What you get

Requirements

Setup effort

Sending a notification to a customer on WhatsApp

Asking a question that fits in a tap

Getting a number connected

Working out who to message

Routing inbound events somewhere

30 tools

create_evolution_instance

get_evolution_info

fetch_evolution_instances

connect_evolution_instance

get_connection_state

logout_evolution_instance

delete_evolution_instance

restart_evolution_instance

set_evolution_presence

set_evolution_webhook

get_evolution_webhook

set_evolution_settings

get_evolution_settings

send_plain_text

send_status

send_media

send_whatsapp_audio

send_sticker

send_location

send_contact

send_reaction

send_poll

send_list

send_buttons

fetch_all_groups

find_group_by_jid

find_group_members

find_chats

find_contacts

some_function

What to know first

Tools you get

Requires

Where it runs

Connect your client

Server setup

MCP Clients

Claude Desktop

Same category

Local MCP (LMCP)

WhatsApp MCP Server by Charlesagui

Whasapo

TimelinesAI WhatsApp

`create_evolution_instance`

`get_evolution_info`

`fetch_evolution_instances`

`connect_evolution_instance`

`get_connection_state`

`logout_evolution_instance`

`delete_evolution_instance`

`restart_evolution_instance`

`set_evolution_presence`

`set_evolution_webhook`

`get_evolution_webhook`

`set_evolution_settings`

`get_evolution_settings`

`send_plain_text`

`send_status`

`send_media`

`send_whatsapp_audio`

`send_sticker`

`send_location`

`send_contact`

`send_reaction`

`send_poll`

`send_list`

`send_buttons`

`fetch_all_groups`

`find_group_by_jid`

`find_group_members`

`find_chats`

`find_contacts`

`some_function`