Green API WhatsApp

MCP gateway for WhatsApp via Green API: messaging, contacts, groups and instance management.

Should I use this

Quality & Safety

A
Description quality
94%
Schema completeness
100%
Naming quality
78%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Findings (6)

  • LOWTool 'whatsapp_forward_messages' description lacks action verbin whatsapp_forward_messages
  • LOWTool 'whatsapp_reboot' description lacks action verbin whatsapp_reboot
  • LOWTool 'whatsapp_get_authorization_code' name length outside 3-30 rangein whatsapp_get_authorization_code
  • LOWTool 'whatsapp_last_incoming_messages' name length outside 3-30 rangein whatsapp_last_incoming_messages
  • LOWTool 'whatsapp_last_outgoing_messages' name length outside 3-30 rangein whatsapp_last_outgoing_messages
  • LOWTool 'whatsapp_remove_group_participant' name length outside 3-30 rangein whatsapp_remove_group_participant

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~4,881Tokens (tool definitions)
~823 BTypical response size
Significant attention impact (3.81% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "whatsapp": {
      "url": "https://mcp.green-api.com/mcp"
    }
  }
}

Remote endpoints

https://mcp.green-api.com/mcpstreamable-http
https://mcp.green-api.com/ssesse

What it can do

Tool inventory

No publishable tool enumeration has been recorded.

Community

Rate this Server

Evidence

Recent observations

auth requiredversion not recorded—
verifiedversion not recorded41 tools
auth requiredversion not recorded—
verifiedversion not recorded41 tools