Vexa
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Description from the maker (original English)
MCP gateway for WhatsApp via Green API: messaging, contacts, groups and instance management.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
X-Instance-Id, X-Api-TokenValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Run this in your terminal
claude mcp add --transport http whatsapp https://mcp.green-api.com/mcp --header 'X-Instance-Id: your-value' --header 'X-Api-Token: your-value'Fill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"whatsapp": {
"url": "https://mcp.green-api.com/mcp",
"headers": {
"X-Instance-Id": "your-value",
"X-Api-Token": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"whatsapp": {
"type": "http",
"url": "https://mcp.green-api.com/mcp",
"headers": {
"X-Instance-Id": "your-value",
"X-Api-Token": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Your choice stays on this device in a cookie; no account needed.
X-Instance-Id secret required HTTP headerX-Api-Token secret required HTTP headerThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified against the domain green-api.com (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: X-Instance-Id, X-Api-Token
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (0.1.2) reached the registry 4 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Vexa, emailmd, MCP WhatsApp Cloud
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
MCP server for WhatsApp Cloud API (Meta) — messages, media, and templates via Graph API
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
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
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
go build -o green-api-mcp-gateway ./cmd/server
Requires Go 1.25+.
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 iconWhen 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 exchangeserver:
transport: stdio # stdio | sse | http | hybrid port: 8090
auth: mode: config # config | proxy cache_ttl: 300 # seconds (proxy mode only)
green_api: instances:
webhook: mode: polling polling_timeout: 20
rate_limit: requests_per_second: 10 burst: 20
logging: level: info format: text
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 to https://api.green-api.com)GREEN_API_TRANSPORT — transport: stdio, sse, http, or hybridGREEN_API_PORT — HTTP port (defaults to 8090)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 to GREEN_API_BASE_URL, then https://mcp.green-api.com)GREEN_API_AUTH_MODE — config or proxyGREEN_API_AUTH_CACHE_TTL — proxy-auth credential cache TTL (seconds)GREEN_API_WEBHOOK_MODE — polling or receiverLOG_LEVEL — log levelLOG_FORMAT — text or json# With environment variables
export GREEN_API_INSTANCE_ID=1101000001 export GREEN_API_TOKEN=your_token ./green-api-mcp-gateway
./green-api-mcp-gateway --config config.yaml
Add to claude_desktop_config.json:
{
"mcpServers": { "whatsapp": { "command": "/path/to/green-api-mcp-gateway", "args": ["--config", "/path/to/config.yaml"] } } }
mcp:
servers:
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
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 — deletewhatsapp_get_state — authorization statewhatsapp_get_settings — current settingswhatsapp_set_settings — update settingswhatsapp_get_qr — authorization QR codewhatsapp_connect — connect instancewhatsapp_disconnect — disconnect instancewhatsapp_get_contacts — contact listwhatsapp_get_contact_info — contact informationwhatsapp_check_whatsapp — phone number checkwhatsapp_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 groupwhatsapp_receive_notification — receive an incoming notification (long-poll)whatsapp_create_instance — create an instancewhatsapp_delete_instance — delete an instancewhatsapp_get_instances — list instanceswhatsapp://instance/{id}/state — instance statewhatsapp://instance/{id}/settings — instance settingswhatsapp_customer_support — template for customer supportwhatsapp_broadcast — template for broadcast messaginggo test ./...
gofmt -w . GOOS=linux GOARCH=amd64 go build -o green-api-mcp-gateway-linux ./cmd/server
MIT — see LICENSE.