green-api-mcp-gateway
MCP serverCommunicationConnects your AI to WhatsApp through Green API so it can send and receive messages, manage contacts, and handle group chats. Once added, your AI can hold conversations on WhatsApp on your behalf and keep your chats organized.
Use green-api-mcp-gateway in Claude, ChatGPT or Ahel Desktop
Free. Sign in, add green-api-mcp-gateway and connect your AI. About a minute.
Also: Claude Code · Cursor · Codex
Then ask your AI: use the whatsapp add group participant tool from green-api-mcp-gateway
Needs your own Instance ID account. Keys stay in your vault.
Details
Available today. Use it from your connected AI after setup.
Add the integration and connect your WhatsApp account through Green API. Then ask your AI to send a message or check your chats to confirm it is working.
What your AI can do with it
- Send and receive WhatsApp messages
- Look up and manage contacts
- Create and manage group chats
- Manage your WhatsApp instance settings
Install green-api-mcp-gateway
The server’s own address, for the clients that take one directly. Or connect Ahel once and every client you use reads it from one address, with the account kept on Ahel rather than in each client’s config.
Claude Code
claude mcp add --transport http --scope user green-api-mcp-gateway 'https://mcp.green-api.com/mcp'Run it once in your project, then open /mcp to approve any sign-in the server asks for.
Claude Desktop
https://mcp.green-api.com/mcpAdd a custom connector in Settings, paste this address, and approve the sign-in.
Cursor
cursor://anysphere.cursor-deeplink/mcp/install?name=green-api-mcp-gateway&config=eyJ1cmwiOiJodHRwczovL21jcC5ncmVlbi1hcGkuY29tL21jcCJ9Open the link and Cursor adds the server at that address.
ChatGPT
https://mcp.green-api.com/mcpIn Settings, enable Developer mode, create an MCP app, and paste this address. Your plan and workspace must allow custom apps.
Codex
codex mcp add green-api-mcp-gateway --url 'https://mcp.green-api.com/mcp'Run it once, then sign in with codex mcp login green-api-mcp-gateway if the server asks for an account.
From the project's README
As published by green-api/green-api-mcp-gateway in README.md.
Support Links
Guides & News
MCP gateway for GREEN-API WhatsApp. Lets AI agents (Claude Desktop, OpenClaw, Cursor, and others) send messages, manage instances, and receive notifications via WhatsApp using the Model Context Protocol.
What it does
Send text messages, files by URL, locations, contacts, polls. Forward and edit messages. Manage groups (create, fetch data, add/remove participants). Check phone numbers for WhatsApp, fetch contacts and their info. Get instance state and settings, QR code for authorization. Receive incoming notifications via polling or an HTTP receiver. Partner API for creating/deleting instances. Multi-instance support in a single gateway. Prompt templates for common scenarios (customer support, broadcasts). Prometheus metrics and OpenTelemetry.
Instructions for connecting the MCP server can be found on our website
Architecture
Clean Architecture (Ports & Adapters):
cmd/server/main.go — entry point, DI wiring
internal/
domain/ — business entities, errors, constants (zero dependencies)
application/ — ports (interfaces)
infrastructure/
auth.go — CredentialManager (in-memory credential store)
config/config.go — YAML + env configuration
greenapi/client.go — WhatsApp client via Go SDK
mcp/
server.go — MCP server (stdio/sse)
tools.go — MCP tools registration
resources.go — MCP resources
prompts.go — MCP prompts
webhook/
bridge.go — polling bridge
receiver.go — HTTP receiver
Build
go build -o green-api-mcp-gateway ./cmd/server
Requires Go 1.25+.
Transports & endpoints
The server supports four transports, selected via server.transport (or the GREEN_API_TRANSPORT env var):
| Transport | Endpoints (relative to host:port) | Use case |
|---|---|---|
stdio | stdin/stdout | Local CLIs (Claude Desktop, Cursor) launching the binary. |
sse | GET / (stream) + POST /message | Legacy MCP clients (SSE only). |
http | POST/GET /mcp | Streamable HTTP (MCP 2025-03-26+) — preferred for new clients. |
hybrid | /sse + /message and /mcp on one port | Public server: serves both legacy SSE and Streamable HTTP. |
All HTTP-based transports also expose:
GET /health,GET /healthz— health probes (no auth)GET /favicon.ico,GET /favicon.png— GREEN-API icon
When auth.mode: proxy is enabled, the OAuth 2.0 PKCE endpoints are added too:
GET /.well-known/oauth-authorization-server— RFC 8414 metadataGET /.well-known/oauth-protected-resource— RFC 9728 metadataGET /authorize— browser-facing authorization formPOST /token— token exchange
Configuration
Via YAML
server:
transport: stdio # stdio | sse | http | hybrid
port: 8090
auth:
mode: config # config | proxy
cache_ttl: 300 # seconds (proxy mode only)
green_api:
instances:
- id: 1101000001
api_token: "YOUR_TOKEN"
api_url: "https://api.green-api.com"
webhook:
mode: polling
polling_timeout: 20
rate_limit:
requests_per_second: 10
burst: 20
logging:
level: info
format: text
Via environment variables
Environment variables take precedence over the YAML config:
The variables below cover both deployment modes. Credentials variables (GREEN_API_INSTANCE_ID, GREEN_API_TOKEN, GREEN_API_URL) apply only to local stdio runs with auth.mode: config. For HTTP transports (sse on /sse + /message, http on /mcp, or hybrid) use auth.mode: proxy instead — credentials arrive in HTTP headers or via the built-in OAuth flow and the env credentials are ignored.
GREEN_API_INSTANCE_ID— instance IDGREEN_API_TOKEN— API tokenGREEN_API_URL— API base URL (defaults tohttps://api.green-api.com)GREEN_API_TRANSPORT— transport:stdio,sse,http, orhybridGREEN_API_PORT— HTTP port (defaults to8090)GREEN_API_BASE_URL— public base URL (used for OAuth issuer/redirects, e.g.https://mcp.example.com)GREEN_API_WIDGET_DOMAIN— unique widget origin for ChatGPT Apps submission metadata (defaults toGREEN_API_BASE_URL, thenhttps://mcp.green-api.com)GREEN_API_AUTH_MODE—configorproxyGREEN_API_AUTH_CACHE_TTL— proxy-auth credential cache TTL (seconds)GREEN_API_WEBHOOK_MODE—pollingorreceiverLOG_LEVEL— log levelLOG_FORMAT—textorjson
Run
# With environment variables
export GREEN_API_INSTANCE_ID=1101000001
export GREEN_API_TOKEN=your_token
./green-api-mcp-gateway
# With a config file
./green-api-mcp-gateway --config config.yaml
Integration
Claude Desktop (local stdio)
Add to claude_desktop_config.json:
{
"mcpServers": {
"whatsapp": {
"command": "/path/to/green-api-mcp-gateway",
"args": ["--config", "/path/to/config.yaml"]
}
}
}
OpenClaw
mcp:
servers:
- name: whatsapp
command: /path/to/green-api-mcp-gateway
args: ["--config", "/path/to/config.yaml"]
Docker
docker build -t green-api-mcp-gateway .
docker run --rm -i \
-e GREEN_API_INSTANCE_ID=1101000001 \
-e GREEN_API_TOKEN=your_token \
green-api-mcp-gateway
MCP Tools
Messaging
whatsapp_send_message— text messagewhatsapp_send_file— file by URLwhatsapp_send_location— locationwhatsapp_send_contact— contact (vCard)whatsapp_send_poll— pollwhatsapp_forward_messages— forwardwhatsapp_edit_message— editwhatsapp_delete_message— delete
Instance
whatsapp_get_state— authorization statewhatsapp_get_settings— current settingswhatsapp_set_settings— update settingswhatsapp_get_qr— authorization QR codewhatsapp_connect— connect instancewhatsapp_disconnect— disconnect instance
Contacts
whatsapp_get_contacts— contact listwhatsapp_get_contact_info— contact informationwhatsapp_check_whatsapp— phone number check
Groups
whatsapp_create_group— create a groupwhatsapp_get_group_data— group datawhatsapp_add_group_participant— add a participantwhatsapp_remove_group_participant— remove a participantwhatsapp_leave_group— leave a group
Notifications
whatsapp_receive_notification— receive an incoming notification (long-poll)
Partner API
whatsapp_create_instance— create an instancewhatsapp_delete_instance— delete an instancewhatsapp_get_instances— list instances
MCP Resources
whatsapp://instance/{id}/state— instance statewhatsapp://instance/{id}/settings— instance settings
MCP Prompts
whatsapp_customer_support— template for customer supportwhatsapp_broadcast— template for broadcast messaging
Dependencies
- mcp-go — MCP SDK
- whatsapp-api-client-golang — GREEN-API Go SDK
Development
go test ./...
gofmt -w .
GOOS=linux GOARCH=amd64 go build -o green-api-mcp-gateway-linux ./cmd/server
License
MIT — see LICENSE.
Tools it offers (41)
What this server listed when Ahel dialed its public endpoint in Oct 2026, with no key and no account of yours. The names are the server’s own.
whatsapp_add_group_participantwhatsapp_check_whatsappwhatsapp_connectwhatsapp_create_groupwhatsapp_create_instancewhatsapp_delete_instancewhatsapp_delete_messagewhatsapp_delete_notificationwhatsapp_disconnectwhatsapp_edit_messagewhatsapp_forward_messageswhatsapp_get_authorization_codewhatsapp_get_chat_historywhatsapp_get_contact_avatarwhatsapp_get_contact_infowhatsapp_get_contactswhatsapp_get_group_datawhatsapp_get_instanceswhatsapp_get_messagewhatsapp_get_qrwhatsapp_get_settingswhatsapp_get_statewhatsapp_get_wa_settingswhatsapp_last_incoming_messageswhatsapp_last_outgoing_messageswhatsapp_leave_groupwhatsapp_logoutwhatsapp_read_chatwhatsapp_rebootwhatsapp_receive_notification
Signals
- Last commit
- Jul 2026
Ahel review
S4info
community integration, published by green-api, not whatsapp
Automated review, not a security audit. Ruleset v1.
Advanced
- Delivery
- whatsapp MCP server → your Ahel connector (mcp.ahel.ai) → your AI.
- Item type
- mcp-server
- Key
com-green-api-whatsapp- Source
- github.com/green-api/green-api-mcp-gateway
- Hosted endpoint
https://mcp.green-api.com/mcp
github.com/green-api/green-api-mcp-gateway
More in Communication
MCP server · builderio
More in Communicationpalisade
MCP server · palisadeemail
More in Communicationagent-native-brain
MCP server · builderio
More in Communicationqr-generator
MCP server · modelcontextprotocol
More in Communicationshipmail-mcp
MCP server · shipmail-to
More in Communicationagentphone
MCP server · agentphone-ai
More in Communication